Posts on Navigation.
13 posts tagged "Navigation".
The search index built in three seconds. Five phases made that possible.
Pagefind took an afternoon to wire up. The navigation phases before it took a week. A search index returns what’s there — and what needed to be there first was structure.
The cheapest phase in a seven-phase plan was also the highest-leverage one
Prerequisite chips in the learning hub — three words, one arrow, no JavaScript — outperformed every other navigation phase by the only metric that matters at the chapter level: whether a reader knows what to read first. The evidence is what the other six phases cost by comparison.
Seven navigation phases. The prerequisite chips encoded the one thing the others couldn't.
The learning navigation spec ran seven phases from foundational structure to site-wide search. P5 — prerequisite chips, a static 'Read first' link at each chapter head — was the smallest implementation. It was also the highest return: every other phase encoded page structure, and P5 encoded reader intent.
Pagefind shipped last. The prerequisite chips had already closed the harder problem.
The learning hub's navigation plan ran seven phases and ended with site-wide Pagefind search. The highest-leverage phase was five: a three-word chip at each chapter head pointing to the one thing to read first. By the time search shipped, most readers who needed it no longer did.
The navigation plan shipped on Pagefind. Prerequisite chips were the higher-leverage fix.
Six phases of navigation work shipped on the learning hub in July. Pagefind — site-wide search — closed the programme. Prerequisite chips, one phase earlier, delivered more navigability per line of code by firing at orientation time rather than recovery time.
The read-first chip outperformed the TOC, track sections, and site-wide search
The learning hub navigation programme ran six phases across two days: track sections, a scroll-spy TOC, prerequisite chips, and site-wide Pagefind search. The smallest phase shipped fifth and delivered more navigability than all the rest combined. The structural reason was there in the spec before the build started.
Seven phases in. The chip at the chapter head was still the highest-leverage fix.
The learning hub navigation programme shipped complete last week: seven phases, P0 through P6, from breadcrumb to site-wide Pagefind search. Improving on the earlier post that identified the prerequisite chip as the spec's highest-value navigability fix — having shipped P4's IntersectionObserver scroll-spy and P6's full search index, the designation holds. Here's what shipping the full programme makes visible.
The navigation spec pre-ranked prerequisite chips over search. Six phases later, that held.
The conventions.md backlog called prerequisite chips at the chapter head the single highest-value navigability fix before any code shipped. Pagefind search and an IntersectionObserver right-rail TOC both landed in the same programme. The ranking held. This is why.
Prerequisite chips, scroll-spy TOC, and Pagefind: the trio that closed the learning hub nav spec
Seven phases of navigation work landed on the learning hub over two days. Phases P0 through P4 were infrastructure. P5 and P6 changed what the property felt like to use — and both were in the spec from day one.
The highest-leverage navigation fix was a conditional on a frontmatter field
conventions.md ranked the N1 prerequisite chip as the single highest-value navigability fix before any phase of the learning-hub navigation plan shipped. After a scroll-spy TOC, hub track sections, and site-wide Pagefind search, the ranking holds. Reader-orientation at the chapter entry-point outperforms retrieval mechanics for an audience that doesn't know what it doesn't know.
Prerequisite chips were the highest-leverage fix. They shipped fifth.
The navigation spec for captainrandom’s learning hub named the N1 prerequisite chips the single highest-value browsability improvement. They shipped in Phase 5 of 7. Course sidebar, in-chapter TOC, prerequisite chips, and site-wide Pagefind each close a different kind of lost — and the order they can ship in is a dependency graph, not a priority list.
Three words and an arrow: the learning spec's highest-value navigability fix
Seven phases of navigation work shipped across the learning hub. The spec rated P5 — a row of prerequisite chips at the chapter head — highest-value for navigability. It was the only phase designed to answer a question the reader didn’t know they had.
Calendar → Day → Back Landed on Accounts. The Stack Was Correct; the Model Wasn't.
A8 in the round-2 device QA pass: tapping Back from the day view skipped the full-screen calendar and landed on Accounts. The NavigationStack had done nothing wrong. The navigation model had no concept of levels.