barerepo

The UI mockups. Open index.html to browse all 24 views.

What is here

index.html          contact sheet linking every view
build.py            regenerates every page from one shared chrome
tokens.css          the entire stylesheet
docs/BUILD.md       implementation order, stack, performance budget, traps

Everything else is a generated page. Edit build.py and re-run it rather than editing HTML by hand. The five original pages were hand-written and drifted, which is why the generator exists.

python3 build.py

Reading order

1. The book, parts I and II. The argument, and how git works.
2. index.html. What it looks like.
3. The book, parts III to VI. The mechanics, and every page.
4. The book, part VII. How to use the site. Every task, with commands.
5. The book, part VIII. How to deploy it, and how to know it is correct.
6. docs/BUILD.md. What to build first.

The book has its own repository, barerepo/book. It is not here.

Read chapter 42 before you render any user content. It is a security chapter.

The book is the only source of truth. Part VII is written in Simplified Technical English. Parts I to VI are normal prose, because they contain argument and not procedure.

The short version

The server owns almost nothing. Identity is an ssh key you hold. Discussion is git notes in your clone. Settings are a file in your tree. Builds run on your hardware. Pull requests are refs you push without asking permission, and merging happens on your machine with git merge while the server watches.

Every view shows the command that performs the action, because the goal is to put the user closer to the machine rather than further from it.

Status

Spec complete. Implementation in progress at the repository root, stage 1 of docs/BUILD.md.