Ticking a section off crosses out the section
All checks were successful
CI / naming (push) Successful in 4s
CI / frontend (push) Successful in 12s
CI / migrations-mysql (push) Successful in 40s
CI / backend (push) Successful in 3m48s

It struck the heading and left everything underneath looking untouched, which
is the opposite of what somebody ticking "this section is done" means. The
strike now covers every block under that heading, down to the next heading of
the same or higher rank - so a top-level section takes its sub-sections with
it.

That needed the rank, and the HTML importer was throwing it away: h2, h3 and h4
all arrived as a flat 'heading', so a parent heading had no children to cross
out. It was the visible half of a real loss - a converted article kept its
words and lost its shape. Headings now carry their level and render at it, and
a guide written before this reads as flat, exactly as it did.

Code blocks, tables and images inside a finished section fade but are not
struck. A line through a command makes it unreadable, and re-reading the
command is usually the reason to look back at a step already done.

The five imported guides were re-imported so they carry their structure.
This commit is contained in:
cproudlock
2026-08-27 15:42:46 -04:00
parent 03a1151a5a
commit 8953ce8210
5 changed files with 98 additions and 13 deletions

View File

@@ -115,6 +115,17 @@ ADR-007 and ADR-002.
### Fixed
- **Ticking a section off crossed out its title and nothing else.** The strike
now covers everything under that heading, including its sub-sections, which
is what "this section is done" means to somebody who ticked the thing that
contained them. It needed the heading RANK, which the HTML importer was
discarding: every heading arrived as a sibling, so a parent had no children
to cross out. Headings now carry their level, render at their rank, and a
guide written before this reads as flat, exactly as it did. Code blocks,
tables and images inside a finished section are faded but not struck - a line
through a command makes it unreadable, and re-reading the command is usually
why somebody looks back at a step they have already done.
- **Tech Tools was invisible to anyone without an account**, even though every
tool on the page is deliberately usable without one and Secure Send is the
single write this product offers a guest. The nav item named no permission,