Docs
The writing that spans Sitez's files, in reading order. Each code file's own reasoning is in its @prose block.
- Design: the spec, with what Sitez promises, its rules, and what's not in v1.
- Usage: install it, start a site, and what to tell your agents.
- Sitez: how Sitez, the site layer, is built, and what was ruled out.
- Elementz: the element, one
@name.htmlfile with its markup, CSS and behavior. - Plan: the order of the work, with what's done and what's next.
- Lessons: what building it taught, for the next change.
- Development: build, test and release Sitez itself.
Docs
- design.md
Sitez is a static site generator, a Vite plugin with no options. Markz goes in
text/, HTML, CSS and JavaScript incode/, JSON indata/and files inpublic/. Runvp build, get complete HTML. - development.md
How Sitez is built and changed. What every repository shares, like the scripts, CI and releases, is in ship's standard, and isn't repeated here.
- elementz.md
elementz is the element layer: one
@name.htmlfile that holds an element's markup, written at build time, its CSS and its behavior. A host renders it into a page. Sitez is the first host, and Pagez (its design) would be the second. - lessons.md
What building Sitez taught, for whoever changes it next. Each lesson says what happened and what to do about it. The detail is in plan, sitez and
git log. - plan.md
Where Sitez is and what comes next, in order. Finished work gets a line or two, newest first. The detail lives in design.md, sitez.md, elementz.md, the code's
@prose, the tests andgit log. - sitez.md
How Sitez is built: the site layer, with its folders, the frame, links, redirects, bundling and the dev server. What it promises is in design.md, and everything here can change underneath without changing those promises. The element is elementz.md's.
- usage.md
Install