Layout replaces one section per page

The admin was a section each for Home, About Us, Collections, Gallery, Collabs, Drops and Services,
because the site's pages were a constant in site-map.ts and a developer was the only one who could add
one. A page builder is going to replace that, so the nav stops enumerating pages.

What is left is the two things a page is NOT: Layout — the shell every page renders inside — and Pages,
listed but not built. Layout is first because it is first in the work: building pages before the frame
they sit in means building them twice.

The panel is a sketch of the page with the controls under it. Menu across the top, a body, the footer
at the bottom, in the chosen colours and typefaces — the same principle the header editor already
follows, where the admin renders the structure as the page will show it. It is honest about being a
sketch: drawing the logo and the rules would be a second implementation of the layout, and the two
would drift the first time either changed.

Fonts are a mapping, not free text. styles.css already declares four ROLES — body, sub, title,
display — and every template asks for a role rather than a typeface, so choosing a font is choosing
which of the four faces the build subsets plays each part. The list travels with the payload rather
than being copied here, because a picker offering a face the build never subsets renders as a fallback
nobody chose.

The per-page panels are NOT deleted. AboutPanel, HomePanel and RecordsPanel are still in the tree and
still work; they are unreachable, which is a line in sections.ts rather than a rewrite. The page
builder is not finished, and removing the only way to edit the live site's content before its
replacement exists would leave a gap with nothing in it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

web/DetailPanel.tsx

@@ -4,13 +4,10 @@ import { Button } from '@/components/ui/button';
 import { DEFAULT_SECTION, isSectionKey, sectionFor, sectionOpen, type SectionKey } from './sections';
 import { AdministrationPanel } from './AdministrationPanel';
 import { MediaPanel } from './MediaPanel';
-import { HomePanel } from './sections/HomePanel';
 import { GalleriesPanel } from './sections/GalleriesPanel';
+import { LayoutPanel } from './sections/LayoutPanel';
 import { PublishButton } from './PublishButton';
 import { SaveTargetProvider, useSaveButton } from './SaveTarget';
-import { AboutPanel } from './sections/AboutPanel';
-import { RecordsPanel } from './sections/RecordsPanel';
-import { COLLABS_CONFIG, DROPS_CONFIG, GALLERY_CONFIG } from './sections/records';
 import { MessagesPanel } from './MessagesPanel';
 import { PlannedSection } from './PlannedSection';
 import { useReady } from './useReady';
@@ -47,15 +44,7 @@ import { useReady } from './useReady';
  * silently showing somebody else's.
  */
 const PANELS: Partial<Record<SectionKey, () => React.JSX.Element>> = {
-  home: HomePanel,
-  about: AboutPanel,
-  /*
-    Three sections, one panel, configured — the same split the site's API already makes between
-    `records.ts` and `sections.ts`. See web/sections/records.ts for what each one carries.
-  */
-  gallery: () => <RecordsPanel config={GALLERY_CONFIG} />,
-  drops: () => <RecordsPanel config={DROPS_CONFIG} />,
-  collabs: () => <RecordsPanel config={COLLABS_CONFIG} />,
+  layout: LayoutPanel,
   galleries: GalleriesPanel,
   messages: MessagesPanel,
   administration: AdministrationPanel,