This blog explains the repository itself: why it is shaped around independent concepts, how the static-site generator works, and which parts of the design still need hardening.
src/concepts, src/syncs, src/engine, and example/pages.
A step-by-step guide to creating a static site — directory structure, frontmatter, layouts, collections, and the dev loop.
A source tour of the concept-design framework repo: concepts, syncs, engine, runtime, and the example site.
How runtime adapters keep concepts pure, testable, and independent by moving platform side effects to a separate boundary.
How the example static site generator is decomposed into independent concepts and recomposed with syncs.
A walkthrough of when/where/then syncs, the thirteen sync files, flow isolation, and where the current sync layer is brittle.
How one CLI action expands into scans, per-file cascades, index regeneration, cleanup, and command reporting.
A single content file moving through Filing, Frontmattering, Formatting, Routing, Collecting, Layouting, and back to Filing.
The recurring sync patterns in this repo — fan-out, join, barrier, context threading, aggregation, and error shapes — with real code.
Where the concept-design model is useful, where this implementation bends, and what the issue review says to fix.