CSS Library

📐 Load order matters: Tokens first, then Reset, then Components/Utilities — Components and Utilities reference the CSS variables Tokens defines.

📦 Library Files

Four small, composable stylesheets instead of every engine page repeating its own copy of the same design system.

Design Tokens

1,535 bytes

Color, spacing, radius, and typography variables shared across every Xcojo engine.

View Raw

Reset

914 bytes

A minimal modern reset — sane box-sizing, no default margins, media elements sized correctly.

View Raw

Components

3,981 bytes

The card, dropdown, sub-nav, code-block, and badge classes shared by every engine page.

View Raw

Utilities

1,388 bytes

A small set of layout and spacing utility classes for one-off adjustments.

View Raw

🔌 Load the Full Library

Simplest option — one link tag, correct load order guaranteed:

<link rel="stylesheet" href="https://dev.xcojo.com/CSS/?file=all">

Or load only what a page needs, in order:

<link rel="stylesheet" href="https://dev.xcojo.com/CSS/?file=tokens">
<link rel="stylesheet" href="https://dev.xcojo.com/CSS/?file=reset">
<link rel="stylesheet" href="https://dev.xcojo.com/CSS/?file=components">
<link rel="stylesheet" href="https://dev.xcojo.com/CSS/?file=utilities">

Example Usage

<div class="xcojo-card xcojo-flex xcojo-flex-col xcojo-gap-3">
    <h2>Example</h2>
    <p class="xcojo-text-muted">Styled entirely from the shared library.</p>
</div>

README & Developer Guide

Welcome to the Xcojo CSS Library Engine. It centralizes the design tokens and component classes used across every engine page, so updating a color or spacing value happens in one place instead of seven.

API Parameter

Class Naming

All component and utility classes are prefixed xcojo- to avoid colliding with anything already on a page.

Cross-Origin Integration (CORS)

All endpoints include automatic CORS headers (Access-Control-Allow-Origin: *) and long-lived caching, since design tokens change rarely.

Migrating an Existing Engine Page

  1. Replace the page's own :root block with a single <link> to ?file=tokens.
  2. Swap hardcoded classes like .card, .dropdown-content, .sub-nav-btn for their xcojo- equivalents where convenient — this is optional and can be done gradually, since the old class names still work if left in place.
  3. Drop the page-specific copies of that CSS once confirmed working, shrinking the page significantly.