` wrapping `{props.children}` then `{props.nav}`. After this change, the no-nav, no-animation code path no longer exists in this file. ## Step 2 — new `PublicationFullHeader.tsx` Drop-in component for the no-nav case. Server component is fine — no scroll listeners, no `ref`, no `useEffect`. ```tsx import React from "react"; export function PublicationFullHeader(props: { children: React.ReactNode }) { return (

{props.children}

); } ``` - No `sticky` class, no `z-10`, no `bg-bg-page`. - No `--header-shrink` paddingTop math — just static `pt-5` (matches the current `calc(20px - 20px * 0)` resting value). - Callers pass a `` (default stacked variant) as children, with `description`, `author`, `subscribeButton` populated. ## Step 3 — `PublicationContent.tsx` Replace the single `PublicationStickyHeader` block (lines ~93–132) with a branch: ```tsx stickyHeader={ navPages.length > 0 ? ( } > ) : ( ) : undefined } subscribeButton={

} /> ) } ``` Key behavior change to flag: the with-nav branch drops `description`, `author`, `subscribeButton` — per the design intent of "simplified header + nav that shrinks on scroll". If that's wrong, the fix is to thread those props back in on the with-nav side (still using `variant="inline"`). Add the `PublicationFullHeader` import; keep the rest of the imports as-is. ## Step 4 — `PublicationPageRenderer.tsx` Same branching shape as Step 3, but custom pages don't carry author or subscribe button today: ```tsx stickyHeader={ navPages.length > 0 ? ( } > ) : ( ) } ``` (A user landing on a custom-page URL when `navPages.length === 0` is an edge case — direct link, no nav available — but it's still a valid render path, so the no-nav branch needs to handle it.) ## Step 5 — `edit/[[...route]]/layout.tsx` Move `PublicationPagesNav` from a sibling into the `nav` prop so it gets the scroll-shrink wrapper. Keep `sticky={false}` (the page editor visually sticks because of its flex layout — `position: sticky` is not used here). Before (lines ~99–112): ```tsx

{props.children}

``` After: ```tsx

} >

{props.children}

``` (Keep the existing `variant="inline"` and the description prop the editor already passes.) ## Open question / risk The scroll-shrink listener in `PublicationStickyHeader` attaches to `el.parentElement` and filters scroll events by `.publicationScrollContainer`. In the published view, that container is `PublicationHomeLayout`'s root — fine. In the editor, `parentElement` is `pubWrapper` (no scroll container class), and the real scroll container lives several levels deeper inside `{props.children}` (each `Page` declares its own `publicationScrollContainer`). Capture-phase scroll listeners on `pubWrapper` *should* fire as the event passes down toward the inner Page, so the filter-by-class approach should still catch it — but worth a manual smoke test in the editor after wiring, because scroll events famously do not bubble. If shrink doesn't fire in the editor, the fix is to walk up from `el` looking for the nearest scroll container inside the DOM subtree, or to broaden the parent search. ## Verification checklist - Published publication home, **0 nav pages**: full header (icon, title, description, author, subscribe), no animation, scrolls with the page, nothing stuck at the top. - Published publication home, **≥1 nav pages**: compact icon + title + nav, sticks to top of scroll container, shrinks on scroll, nav stays visible. - Published custom page (`/[rkey]`), **≥1 nav pages**: same as above with active path highlighting. - Published custom page (`/[rkey]`), **0 nav pages**: full header renders above the page content, no animation. - Page editor (`/edit/...`): compact icon + title + PublicationPagesNav, scroll-shrink behavior fires as you scroll the page body, header does not use `position: sticky`. - `npx tsc` clean.