From 69d5a24fa846296b55c2c9609a7063802a20a26b Mon Sep 17 00:00:00 2001 From: Jakub Zych Date: Wed, 28 Oct 2026 12:35:11 +0100 Subject: [PATCH] docs(33): record per-site options for post title, new-tab links and journal breadcrumbs --- .../phases/33-seo-output-audit-and-content/33-CONTEXT.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.planning/phases/33-seo-output-audit-and-content/33-CONTEXT.md b/.planning/phases/33-seo-output-audit-and-content/33-CONTEXT.md index 13d2f0da..3edb8db9 100644 --- a/.planning/phases/33-seo-output-audit-and-content/33-CONTEXT.md +++ b/.planning/phases/33-seo-output-audit-and-content/33-CONTEXT.md @@ -40,6 +40,10 @@ The split of responsibility from 32-CONTEXT still holds: the backend plugins own - **Off:** content H1 is stored and rendered as written; the editor offers H1; `journal:fix-headings` refuses to run and says why; the layer does not demote h1 (it reads the setting from the Journal API, not from a layer option). - The live heading outline (D-51) works in both modes. The crawler keeps checking the rendered page (one H1 per page); the CMS-side "H1 in content" check runs only when the setting is on. - Where the setting lives (Journal, not the SEO plugin) follows D-96: the content plugin owns its own fixes. +- **Layer options instead of fixed layout assumptions (Jakub, 2026-10-28, from the UI-SPEC check).** + - **Post title heading:** the journal layer's post page renders the title as the H1 when Journal's H1 setting is on, and as a styled non-heading element when it is off, so a post never gets two H1s. A layer option (e.g. `postTitleTag`) overrides either way. + - **Outbound links in a new tab (D-83):** a switch on the SEO settings Links tab, manageable through MCP, default on. When off, outbound links keep their `rel` rules but open in the same tab. + - **Journal breadcrumbs (D-86):** a journal-layer option turns off the journal pages' built-in ``, for sites whose layout places breadcrumbs itself. - **The framework still carries no SEO code (D-90).** If Phase 33 needs a new framework seam, it must be generic and additive (D-106 rules: patch tag, no breaking change); D-103 rules out a fourth seam for redirects and verification files. ### Decisions implemented entirely in Phase 33