Handbook
Cross-site documentation map
Forge splits documentation by concern, not by hiding Lenses:
Updated
| If you need… | Start here |
|---|---|
| Lenses product — install, Studio, Wizard, security, APIs | This site (lenses.forgesdlc.com) and forge-lenses on GitHub |
| Forge SDLC methodology — adoption narrative, knowledge base | forgesdlc.com |
| Blueprints framework — ceremonies, templates, process handbook | blueprints.forgesdlc.com (Lenses quickstart hub: Blueprints → Lenses) |
| Kitchen Sink — layouts, components, diagram templates | Kitchen Sink handbook · forgesdlc-kitchensink (GitHub) — diagram keys for this handbook live in Diagram catalog. |
| Maintainer-only — ADRs, raw HTTP tables, release mechanics | Maintainer handbook (GitHub) — not on the lean public static build |
Rules of thumb
- Evaluators stay on Lenses + Blueprints Lenses hub until they need process depth.
- Operators pair Security and local-first with Configuration reference.
- Automation authors pair Schemas and API (builders) with JSON examples.
This page satisfies the prompt-pack docs/public/cross-site-map.md intent using the docs/handbook-public/ layout (same static handbook build).
Use Forge SDLC methodology for executive framing, Blueprints for ceremonies/templates, then return here for executable Studio/Wizard/API guidance—avoid duplicate canon across sites; prefer links over verbatim copies.