nexxo 8c105c17d6 Move each plan's marketing copy from the controller into the console ... Audience line and note were LandingController::COPY, a hardcoded array keyed on exactly the four plan keys the seed migration created — a plan made under any other key rendered with no copy at all. They move onto the family for the same reason the recommendation mark does: they are a stance about the product line, not a capability that changes with a price, so they must not be frozen per version. Backfilled in the migration from the controller's own strings, so the public page prints exactly what it printed a moment ago. A family with no copy yet renders without the audience line rather than an empty gap. Feature labels (managed_updates, daily_backups, ...) stay in the controller: they name catalogue features, not individual plans, so there is no per-plan or per-version place to hang an editable customer-facing label without re-introducing a shared feature table. That table existed once and was deliberately removed when the plan catalogue closed its pricing split-brain; bringing it back for wording alone is a bigger, separate decision.		2026-07-29 14:31:44 +02:00
..
css	Redesign the public website instead of recolouring it	2026-07-29 11:43:25 +02:00
js	Answer a check at once, start an update at once, and count down to neither	2026-07-28 22:25:07 +02:00
views	Move each plan's marketing copy from the controller into the console	2026-07-29 14:31:44 +02:00