Repository

GitHub Structure & Consolidation

How this design system is organized for GitHub, and the one rule that keeps it from sprawling: one project = one repo = one deploy. Everything that links together lives together.

Doc 32 / 32Repo Digital-Allies/design-system

01The rule

Work split across separate projects can't link to each other once deployed — that's how portals end up pointing at nothing. So:

This project is the single source of truth. Tokens, fonts, components, templates, slides, the UI kit, and the CMS all live here.
New work that links into the system is built inside this project.
New work that merely uses the brand (a separate product, e.g. Atomic Finds) copies in the assets it needs — it doesn't cross-link to this repo's files.

Field note. If you ever find a link reaching into another project's files, that's the bug. Bring the files home or copy what's needed.

02Folder structure

design-system/
  index.html                  # landing — portals + downloads
  00-master-index.html        # every doc, linked
  colors_and_type.css         # all tokens + @font-face
  README.md  SKILL.md         # brand book + skill manifest
  GLOBAL_CONTEXT_FOR_CLAUDE.md
  assets/                     # logos, icons, art, photos
  fonts/                      # Lexend Deca + JetBrains Mono
  preview/                    # one spec card per concept
  ui_kits/website/            # digitalallies.net as components
  slides/                     # 7 slide templates
  social/                     # social carousels
  templates/                  # CMS-ready page templates
  docs/                       # extended documentation
  cms/                        # CMS / marketing hub
    index.html                # the hub
    dashboard.html            # standalone dashboard
    connected/                # Connected CMS + 30-Day Run (editable)
  _ds_bundle.js               # compiled components (generated)

03Updating the repo

The platform project is the live working copy. To publish:

# inside your local clone of the repo
git add .
git commit -m "Sync: CMS consolidation + docs"
git push origin HEAD:main

If git reports not a git repository, you're not inside the repo folder — cd into your clone (or git clone it first), drop the updated files in, then commit. Authentication uses a GitHub Personal Access Token as the password.

04Deploying

Once the repo is current, import Digital-Allies/design-system into Vercel (Add New → Project). Vercel serves every file, so all portals, previews, downloads, and the CMS apps work — the whole system live, from one deploy.