V1 build order and coverage #25
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ordered build list and the map from every settled decision in PLAN.md to the
issue that implements it. A decision with no issue beside it is a hole in the
plan. Closes when #24 closes.
One branch and PR per milestone, one commit per issue.
Build order
M1 tracer bullet - one hardcoded template end to end, thin at every layer
M2 spec language
M3 layout engine
M4 renderers complete
M5 widgets
M6 editor shell
M7 authoring
M8 v1
Composing the page found five things and each was fixed before v1 closed:
Coverage
Out of scope
Decisions 24 to 26 are in no milestone. Two invariants keep 24 and 25 cheap and
are tracked as requirements rather than features:
pages -> documentfrom the start - #7, #15Decision 26, content reflowing across a break, is a layout rewrite. If it is ever
wanted, decisions 3, 5 and 16 reopen.
Closing with #24. Every milestone is built and every settled decision in PLAN.md
has an issue beside it.
The five findings the gate turned up are listed against M8 above. PLAN.md moved
with them: decision 6 gained count, decision 11 gained readouts and the page and
theme panels, and decision 16 now says all four margins rather than the bottom.