From 97d63216b627ff7ccee0c79adbde7f88269717a9 Mon Sep 17 00:00:00 2001
From: istos <ronald@istos.it>
Date: Fri, 31 Jul 2026 17:20:49 +0200
Subject: [PATCH] site: take the six doors off the landing page
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The page is now three things: what bench is, what installing costs, and
why to bother. The header nav is the way into the docs.

Removing them takes their CSS with them (.doors/.door* in the base sheet
and in all three breakpoints) and two tests that existed only for them —
the six-are-distinct check here and TheDoorsOpenOntoArticles in
test_site_pages. The hero-buttons test survives its class, renamed to say
what it now guards: the landing page's only links into the docs.

One test needed retargeting rather than deleting.
test_it_fails_before_anything_is_written removed /concepts/team-mode/
from the manifest to prove a dead internal link stops the build before
anything is written — but the link it relied on was a door. It now aims
at /guides/install/, which the hero button still hard-links.

Side effect worth having: the two reasons in "Why bench?" that nearly
repeated doors 03 and 04 no longer sit above them.
---
 site/static/site.css       | 32 ++-------------------
 site/templates/home.html   | 57 ++++++--------------------------------
 tests/test_site_landing.py | 31 ++++++---------------
 tests/test_site_pages.py   | 14 ----------
 4 files changed, 20 insertions(+), 114 deletions(-)

diff --git a/site/static/site.css b/site/static/site.css
index 500b4de..7ce619a 100644
--- a/site/static/site.css
+++ b/site/static/site.css
@@ -406,10 +406,9 @@ img{max-width:100%;height:auto}
 .install-copy p{margin:0;max-width:52ch;color:var(--muted);text-wrap:pretty}
 .install .terminal{min-width:0}
 
-/* Why bench, above the doors. Deliberately unboxed: the doors below are
-   the page's one grid of cards, and repeating that shape here would make
-   the eye read the same object twice. Two columns rather than three, so
-   the first reason — the one that needs a sentence, not a phrase — has
+/* Why bench: the landing page's one content section, between the
+   install band and the footer. Two columns rather than three, so the
+   first reason — the one that needs a sentence, not a phrase — has
    somewhere to put it. */
 .why{padding:8px 44px 30px}
 .why-title{
@@ -430,28 +429,6 @@ img{max-width:100%;height:auto}
   text-wrap:pretty;
 }
 
-/* Every door is a link to a page this site builds — the whole card is
-   the target, so the hover is the card's border rather than an
-   underline under three words of it. */
-.doors{
-  display:grid;grid-template-columns:repeat(3,1fr);gap:14px;
-  padding:0 44px 34px;
-}
-.door{
-  display:flex;flex-direction:column;gap:8px;padding:20px;
-  background:var(--surface);border:1px solid var(--border-soft);
-  border-radius:12px;color:var(--text);
-}
-.door:hover{border-color:var(--accent);color:var(--text);text-decoration:none}
-.door-dark{background:var(--text);border-color:var(--text);color:var(--canvas)}
-.door-dark:hover{border-color:var(--accent);color:var(--canvas)}
-.door-index{font-size:11px;color:var(--dim)}
-.door-dark .door-index{color:#7fa0a8}
-.door-title{font:600 19px/1.2 var(--display)}
-.door-text{font-size:var(--t-ui);line-height:1.6;color:var(--muted)}
-.door-dark .door-text{color:#a9c4c9}
-.door .mono{font-size:var(--t-code)}
-
 /* The strip at the foot of the landing page. It carries the version and
    nothing else measurable, because the version is the only thing about
    itself this site can measure. */
@@ -548,7 +525,6 @@ img{max-width:100%;height:auto}
   .menu-contents{display:block}
   .hero{grid-template-columns:minmax(0,1fr);gap:28px;padding:32px 24px}
   .install{grid-template-columns:minmax(0,1fr);gap:26px;padding:28px 24px}
-  .doors{grid-template-columns:repeat(2,minmax(0,1fr));padding:0 24px 28px}
   .why{padding:8px 24px 26px}
   .strip{padding:18px 24px}
 
@@ -594,7 +570,6 @@ img{max-width:100%;height:auto}
   .side{display:none}
   .menu{display:block}
   .page-article .prose,.page-reference .prose{padding:24px 20px 36px}
-  .doors{grid-template-columns:minmax(0,1fr)}
   .why-list{grid-template-columns:minmax(0,1fr);gap:18px}
   .masthead{padding:12px 18px;gap:12px;flex-wrap:wrap}
   .crumbs{flex-wrap:wrap}
@@ -635,7 +610,6 @@ img{max-width:100%;height:auto}
   .hero{padding:26px 16px}
   .hero-actions{gap:8px}
   .hero-actions .button{width:100%}
-  .doors{padding:0 16px 24px}
   .why{padding:8px 16px 22px}
   .strip{padding:16px}
   .install{padding:24px 16px}
diff --git a/site/templates/home.html b/site/templates/home.html
index a67161f..7edad5c 100644
--- a/site/templates/home.html
+++ b/site/templates/home.html
@@ -1,6 +1,8 @@
 <!doctype html>
-<!-- Layout "home" — 1b Dockside from the turn-2 docs design: a landing
-     that is mostly a terminal and a set of doors.
+<!-- Layout "home" — 1b Dockside from the turn-2 docs design, reduced to
+     three things: what bench is, what installing it costs, and why to
+     bother. The six doors it used to end on are gone; the header nav is
+     the way into the docs.
 
      The words here are authored rather than sliced (site/pages.json says
      so with "source": null), which is exactly why the two facts a
@@ -133,10 +135,10 @@ Task board for ~/your-repo/.task-manager/tasks
   </div>
 </section>
 
-<!-- Why bench, before the six doors say what it does. Four reasons, and
-     the first is the one no hosted tool can answer: it is in your
-     codebase, so it is yours to change. The three after it are the
-     coordination problems a reader has usually already hit. -->
+<!-- Why bench. Four reasons, and the first is the one no hosted tool can
+     answer: it is in your codebase, so it is yours to change. The three
+     after it are the coordination problems a reader has usually already
+     hit. -->
 <section class="why">
   <h2 class="why-title">Why bench?</h2>
   <div class="why-list">
@@ -169,49 +171,6 @@ Task board for ~/your-repo/.task-manager/tasks
   </div>
 </section>
 
-<section class="doors">
-  <a class="door" href="/guides/install/">
-    <span class="mono door-index">01</span>
-    <span class="door-title">Running in two minutes</span>
-    <span class="door-text">Drop it into any repo, run one script, open the
-      board. No account, no config sprawl — it untars into
-      <span class="mono">.task-manager/</span> and serves on port 26071.</span>
-  </a>
-  <a class="door" href="/concepts/stages/">
-    <span class="mono door-index">02</span>
-    <span class="door-title">Always know what every agent is doing</span>
-    <span class="door-text">Backlog to done at a glance. The board cannot
-      drift from reality, because tasks <i>are</i> files in your repo: the
-      directory a card sits in is its status.</span>
-  </a>
-  <a class="door" href="/concepts/agents-on-the-board/">
-    <span class="mono door-index">03</span>
-    <span class="door-title">Parallel agents, zero collisions</span>
-    <span class="door-text">Every agent gets its own git worktree and branch.
-      Run five at once without them overwriting each other.</span>
-  </a>
-  <a class="door" href="/concepts/pull-requests/">
-    <span class="mono door-index">04</span>
-    <span class="door-title">Nothing ships without you</span>
-    <span class="door-text">Finished work arrives as a PR with CI status on
-      the card. bench never merges — you stay the gate, without being the
-      bottleneck.</span>
-  </a>
-  <a class="door" href="/concepts/team-mode/">
-    <span class="mono door-index">05</span>
-    <span class="door-title">One board for the whole team</span>
-    <span class="door-text">Synced through git itself
-      (<span class="mono">BOARD_SYNC=1</span>) — no shared server, no
-      per-seat billing, no “who updated the ticket?”</span>
-  </a>
-  <a class="door door-dark" href="/concepts/three-layer-law/">
-    <span class="mono door-index">06</span>
-    <span class="door-title">Swap agents without rewiring</span>
-    <span class="door-text">Vendors are adapters. Change your coding agent,
-      or run several, without changing your workflow.</span>
-  </a>
-</section>
-
 <!-- The strip turn 1 of the design filled with a most-read ranking. The
      analytics here counts pageviews and nothing about a person, so it
      could not honestly rank anything for a reader anyway; the strip says
diff --git a/tests/test_site_landing.py b/tests/test_site_landing.py
index 7143fa5..cda5a8c 100644
--- a/tests/test_site_landing.py
+++ b/tests/test_site_landing.py
@@ -11,8 +11,8 @@ Three promises, each mechanised below:
   held against the source that prints it — install.py's setup questions,
   board.py's startup. A reworded prompt fails here rather than quietly
   turning the strongest thing on the page into fiction.
-- **Every door opens.** The six cards point at routes this build writes,
-  and a link that resolves to nothing fails the build instead of shipping.
+- **Its links go somewhere.** A link that resolves to nothing fails the
+  build instead of shipping.
 
     python3 -m unittest discover -s tests
 """
@@ -135,24 +135,9 @@ class TheTerminalIsATranscript(LandingCase):
         self.assertIn("abridged", self.home)
 
 
-class TheDoorsOpen(LandingCase):
-    """Six doors, each a page this site builds."""
-
-    def doors(self) -> list:
-        return re.findall(r'<a class="door[^"]*" href="([^"]+)"', self.home)
-
-    def test_there_are_six_and_they_are_distinct(self):
-        self.assertEqual(6, len(self.doors()))
-        self.assertEqual(6, len(set(self.doors())))
-
-    def test_each_one_is_a_route_the_build_writes(self):
-        routes = {page["path"] for page in self.manifest["pages"]}
-        for door in self.doors():
-            with self.subTest(door=door):
-                self.assertIn(door, routes)
-                self.assertTrue(
-                    BUILDER.target_for(self.out, door).is_file(),
-                    f"{door} is in the manifest but produced no page")
+class TheHeroLeadsSomewhere(LandingCase):
+    """The landing page's only links into the docs, now that the six
+    doors are gone: these two buttons and the header nav."""
 
     def test_both_hero_buttons_go_somewhere_real(self):
         """One to the install guide, one to the repository."""
@@ -286,10 +271,12 @@ class ADeadInternalLinkStopsTheBuild(ScratchCase):
         self.assertIn("does not write", result.stderr)
 
     def test_it_fails_before_anything_is_written(self):
-        """As drift does: the last good build stays up."""
+        """As drift does: the last good build stays up. Aimed at the
+        install guide because the hero button hard-links it — the
+        landing page's other internal links went with the doors."""
         manifest = self.repo.manifest()
         manifest["pages"] = [page for page in manifest["pages"]
-                             if page["path"] != "/concepts/team-mode/"]
+                             if page["path"] != "/guides/install/"]
         self.repo.write_manifest(manifest)
         self.repo.build()
         self.assertFalse(self.repo.out.exists(),
diff --git a/tests/test_site_pages.py b/tests/test_site_pages.py
index 1cde53f..7182cce 100644
--- a/tests/test_site_pages.py
+++ b/tests/test_site_pages.py
@@ -32,7 +32,6 @@ HEADING_ID = re.compile(r'<h2 id="([^"]+)"')
 TOC_LINK = re.compile(r'class="toc-link" href="#([^"]+)"')
 SIDE_HERE = re.compile(r'class="side-link side-here" href="([^"]+)"')
 GUTTER_LINK = re.compile(r'class="gutter-link" href="([^"]+)"')
-DOOR = re.compile(r'class="door[^"]*" href="([^"]+)"')
 LEDE = re.compile(r'<p class="prose-lede">(.*?)</p>', re.S)
 # Both rails are written twice — the column the design draws, and the
 # folded <details> strip that replaces it below the breakpoint. So these
@@ -269,19 +268,6 @@ class EditThisPageOpensTheSection(BuiltSite):
                 'class="gutter-link" href="')[-1].split('"')[0])
 
 
-class TheDoorsOpenOntoArticles(BuiltSite):
-    """Task 33 put six doors on the landing page. This is the other end of
-    them."""
-
-    def test_every_door_lands_on_a_page_in_the_flow(self):
-        routes = {entry["path"] for entry in self.flow}
-        doors = DOOR.findall(self.page("/"))
-        self.assertEqual(6, len(doors))
-        for door in doors:
-            self.assertIn(door, routes,
-                          f"the door to {door} opens onto nothing")
-
-
 @needs_renderer
 class MarkdownComesOutAsMarkup(BuiltSite):
     """The edge case: a table, a fenced code block and a nested list have