Launch

Changelog

Release 1.2.0

Every section on every page type now has its own `Show the …` box, and unticking it removes the section from the markup rather than hiding it. The colour scheme stops fighting the colour pickers, and section headings disappear when you leave them blank.

3 min read

Until this release, removing a section from a Launch page meant emptying it. Delete the quotes, and the quotes section went away. That works, but it is a destructive way to answer a layout question — you lose the content in order to find out whether the page reads better without it, and getting it back means typing it again.

Every section on every page type now carries its own boolean, sitting at the top of that section’s settings group and defaulting to on. There are fifty-seven of them across the eight page types. Untick one and the section leaves the document: not display: none, not an empty padded band with a hairline at the top of it, gone. Tick it again and your content is where you left it.

The toggle is an AND with the content rather than an override of it. Ticking Show the quotes on a page that has no quotes renders nothing, which means the two ways of removing a section still both work and you can pick the one that suits what you are doing. Clear the content when it is wrong; untick the box when it is right but not now.

Two things stayed where they were, and both are deliberate. The navigation bar has always had its own toggle in Appearance rather than in a section group, because it is chrome rather than content. The footer call to action is a theme token, not page metadata, because it is site-wide — clear its heading to remove it everywhere.

Section headings follow the same rule. A comparison table with no title prints the table. A features block with no pitch prints the features. Previously an empty heading left an empty rule above the section, which is the kind of detail that only shows up on the one page where you didn’t want a heading.

Colour scheme is now an opt-in switch. dark and light ship complete palettes and ignore the seven individual colour tokens; custom is what makes those tokens live. The problem this solves is that a colour picker has no unset state — it always holds a value, so a scheme had no way to tell “the user chose this” from “this is what was in the box”. An explicit third option is the only way a scheme can stay in charge of its own palette. Accent is the exception and applies in all three, because it is a brand colour rather than a light or dark one.

Smaller things in this release: the changelog timeline prints a post’s last tag as a version chip, so ["Changelog", "3.0.0"] gives you both the filter and the number; tag matching normalises the way Masthead does, so The Economy, the economy and the-economy are the same tag; and the navigation rail accepts a one-line note per child link.