For the people who will build it
S.I.T.E.S is a specification, not a library. Nothing to install, nothing to compile, and no dependency to keep current. These pages are the contracts: what a compliant site is, how the grid works, how a site is authored, and how to assemble one by hand.
What you are actually getting
A specification, not a dependency
The rules a compliant site follows — ten of them, and this site obeys every one. Nothing to upgrade, because there is nothing to install.
A grid with two modes
An automatic auto-fit grid for ordinary pages, and a configured twelve-column grid when a layout has to be exact. A container query per tile handles every screen without a breakpoint.
One content file
Copy, theme, navigation and images live in one JSON document. The markup owns structure; the file owns the words, and the admin edits it.
Tiles that compose
Every part declares the fields it accepts, so the admin, the builder and the linter all read one declaration instead of three lists that drift.
Where to go next
Quickstart — build one by hand
Copy a starter page, paste tiles into it, put your words in the content file. A text editor and a browser are the whole toolchain.
The grid
How the two layout modes work, why there are no breakpoints, and how a tile reflows by its own width rather than the window width.
The standard
The full rule set with conformance levels, and the reasoning behind each rule rather than just the rule.
The blueprint format
Author an entire site as one Markdown document, then compile it to the content file. This is how an agent writes a site.
The repository is the documentation
Every rule in the standard is implemented in the code you are reading, and this site is built with it. Clone it and point your editor — or your agent — at it.