projectious.work — Brand & Design System

projectious-work.github.io/brand

Colour, typography, logo, and interface patterns — with the usage terms that go with them.

---

This repository holds the complete brand system for projectious.work: the design documentation, the logo in every delivered format, machine-readable design tokens, and document templates. The published site at projectious-work.github.io/brand is generated from this repository and is built with the system it documents — the colour scales rendering those pages are the scales the pages describe.

Status: Active — maintained · Release: v3.0.0

What's inside

Three scales, defined step roles

The palette is three 12-step Radix-convention ramps — midnight, orange, slate — across light, navy-default dark, and opt-in deep-dark appearances. Every step carries a role, so a border step never gets pressed into service as text.

A named entry point for each colour

Seven aliases sit on top of the scales for the values most projects reach for first.

Each appearance is token-driven. Navy is the default dark experience; deep dark is an explicit focused-workspace option:

Three typefaces, three jobs

Plus Jakarta Sans for headings, Source Sans 3 for body, IBM Plex Mono for code — all SIL OFL 1.1, on a fixed ramp. Each row below is set in the values it documents.

Code is dark by default, with a real light companion

The default code panel stays dark in every page appearance. A separately measured light syntax palette supports deliberate light-panel specimens; it is never produced by inversion or an automatic page-mode switch.

Components with normative measurements

Where a component appears in the docs, its numbers are binding — a 40px input is 40px.

Documentation

Full-text search is at /search/ — live filtering, term highlighting, shareable ?q= links, and no external search service. The release dropdown in the top bar switches between versions.

Section	Covers
Foundations	Colour, typography, spacing, shape, motion
Logo	Lockups, clear space, minimum sizes, file formats
Interface	Components, code, appearances, icons, forms
Media	Motion, audio, video, photography, presentations
Collateral	Business card, email signature, social and OG
Governance	Licensing, trademark, legal assessment, provenance
Tokens	CSS, JSON, and Tailwind exports

Repository layout

src/                Normative brand contract and Hugo site
├── hugo.yaml       Site and release configuration
├── content/        Authoritative human-readable documentation
├── assets/scss/    Site-owned, data-driven design-system specimens
├── layouts/        Layouts and the specimen shortcodes
├── data/brand.yaml Authoritative structured values
├── static/         Public assets and generated token downloads
└── go.mod          Pinned projectious.work Hugo theme release

input/              Designer-supplied upstream reference material
scripts/            Local generation, verification, release, and deploy tools

src/data/brand.yaml and src/content/docs/ are the local sources of truth. Public downloads are generated from them. input/ is reference material for reconciliation and is not a second runtime authority.

Build output goes to public/ at the repository root, not inside src/.

Building the site locally

Requires Hugo extended ≥ 0.157. The site uses the theme's Hugo-only CSS path and does not require Node or npm.

git clone https://github.com/projectious-work/brand.git
cd brand

./scripts/serve-docs.sh     # live preview at http://localhost:1313/
./scripts/build-docs.sh     # production build into public/
./scripts/verify.sh         # the full check suite
./scripts/deploy-docs.sh    # build and push to the gh-pages branch

When working in the development container, start the watcher with ./scripts/serve-docs.sh --bind 0.0.0.0. The Compose override publishes its port only at http://localhost:1313/ on the host.

There is no CI. No GitHub Actions, no workflows. Builds, checks, and deployments all run locally and are pushed to the gh-pages branch, which GitHub Pages serves from its root. scripts/verify.sh is what "the checks passed" means here:

Check	What it covers
build-docs.sh	Hugo build, including relref resolution
audit_contrast.py	Every page in both colour modes against WCAG AA
check-links.mjs	Every internal link and asset resolves

Releasing

./scripts/release.sh v1.2.0 --dry-run   # show what would happen
./scripts/release.sh v1.2.0             # verify, stamp, tag, push, publish

Prepare version metadata and the changelog on release/vX.Y.Z, review and squash-merge it, then run release.sh from clean main. It verifies the merged release, creates the tag and GitHub Release, and publishes the archived snapshot plus the latest root in one Pages push. See CHANGELOG.md.

To regenerate the screenshots in this README:

uv run --with playwright playwright install chromium
./scripts/capture-readme-images.sh

Licence

This repository is split-licensed:

• Brand assets — logos, brand imagery, and normative design documentation under src/ — are proprietary and source-available. You may view and reference them; you may not modify, redistribute, or use them commercially without written consent.
• Code, scripts, and design tokens are MIT. The token values are free to use.

Full terms in LICENSE.md and TRADEMARK.md. Third-party asset provenance is documented in the governance section.

Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md. Run ./scripts/verify.sh before opening a pull request. Security or unlicensed-material reports go to info@projectious.work — see SECURITY.md, not a public issue.

---

_{© 2026 projectious.work · Redesigning work — Cloud · Agile · Agentic AI}