Handbook
Forge design system (Kitchen Sink)
This handbook uses the **Forge design system** from the shared [forgesdlc-kitchensink](https://github.com/autowww/forgesdlc-kitchensink) repository: Bootstrap 5 dark theme, design tokens, Python
Forge design system (Kitchen Sink)
This handbook uses the Forge design system from the shared forgesdlc-kitchensink repository: Bootstrap 5 dark theme, design tokens, Python components and layouts, HTML transforms, and reusable SVG diagram templates.
Where it lives
| Piece | Role |
|---|---|
forge-theme.css |
Blueprints handbook look (nav, ToC, prose, callouts) |
docs-theme.css |
Optional chapter-style pages |
forge-theme.js |
Theme behavior |
components/ (Python) |
handbook_page(), callouts, nav fragments, table transforms |
assets/svg/ |
Diagram archetypes (flows, charts, boards) |
Build copies CSS/JS and SVGs into website/assets/ when you run generator/build-handbook.py.
Design tokens (summary)
- Background: deep space (
#0A0E17family) - Accents: cyan (
#06B6D4), amber (#F59E0B) - Fonts: Inter (body), JetBrains Mono (code), Space Mono (labels)
Use semantic HTML and existing component classes from the generator rather than ad-hoc styles.
Page layouts
Kitchen Sink defines full-page layouts (showcase, handbook, product, landing, …). The blueprints site uses handbook_page: sidebar + article + optional right ToC. See the Kitchen Sink Page Layouts documentation for schematics and live previews.
Diagram templates (examples)
Below are a few SVG templates shipped with Kitchen Sink. They illustrate the visual language for methodology docs; replace placeholders with your own labels.
Reference: the Kitchen Sink repo includes a built diagram gallery under showcase/ (run python3 generator/build-showcase.py locally, or see forgesdlc-kitchensink for sources).
Authoring guidance
- Prefer Mermaid in Markdown for diagrams that change often; use SVG templates for stable figures.
- Put shared figures in blueprint
docs/assets/or rely on copied Kitchen Sinkassets/template-*.svgafter build. - Keep tables and headings so
transforms(e.g. table wrappers) can run consistently.
Related links
- Documentation structure — how SDLC docs are organized
- Maintenance (generator / CI) — see
sdlc/docs/MAINTENANCE.mdin the blueprints repository
Canonical source
Edit https://github.com/autowww/blueprints/blob/main/sdlc/DESIGN-SYSTEM-KITCHENSINK.md first; regenerate with docs/build-handbook.py.