Thread all Vitality Blueprint chapters into one long-form page once the series completes
DARE.CO.UK · PARKED SKETCH · 2026-06-07
Mirrored from ~/.claude/.../memory/parked_sketch_happiness_thread_vitality_blueprint_2026-06-06.md. This is a design sketch parked for future build — read for context, not as a current deliverable.
Dan 2026-06-06 after Ch8 shipped — “It would be great to thread all the chapters into 1-long-page, once we complete it all.” Build trigger = all remaining chapters voiced (Ch9 Supplements through Ch12 Mobility + back chapters). Output is a single
/body/vitality-blueprint/page that reads as a continuous book, drops the per-chapter cross-link friction, preserves anchor IDs for direct deep-links, and stays regeneratable from the chapter sources. Probably a small build script rather than manual curation.
Sketch: when the Vitality Blueprint series is complete, build a single long-form page that stitches every chapter article into one continuous read. Serves two distinct reading modes: chapter-by-chapter (current, scannable) and full-book (longer-form, dive deep).
Why (Dan 2026-06-06):
“It would be great to thread all the chapters into 1-long-page, once we complete it all.”
The series so far (Ch1-8) reads well as individual articles — each chapter has its own page, its own URL, its own pull-quotes. Cross-links bridge the inter-chapter dependencies. That’s the right primary surface. But there’s a second reader mode that the chapter view doesn’t serve: the person who wants to read the whole Blueprint in one sitting without 12 navigation hops. The threaded long-form page is that.
Build sketch:
~/bin/happiness_thread_blueprint.py — small script that:
- Reads
body/vitality-blueprint-*-after-50/index.htmlfiles in chapter order (1-12 + back chapters) - Extracts just the
<article class="article-body">block from each - Generates a single page at
body/vitality-blueprint/index.htmlwith: - One unified<head>(title, meta, og) - One unified<style>block (the shared blueprint CSS, deduped) - A sticky/jumpable table of contents - Each chapter wrapped in<section id="chapter-N" class="chapter">with chapter-number kicker - Per-chapter “back to TOC” affordance - Source attribution + R2 PDF link at top AND bottom - Drops the inter-chapter cross-link friction — when everything is on one page,
<a href="/body/vitality-blueprint-circulation-after-50/">Ch2</a>becomes<a href="#chapter-2">Ch2</a>(in-page anchor). Script handles the rewrite. - Preserves stable anchor IDs (
#chapter-1,#chapter-2, etc.) so deep-links from outside survive future re-stitchings.
Reading-mode decision (which surface is canonical):
- Chapter-by-chapter articles stay as the primary content. They’re what the room index lists, what gets shared individually, what shows up in search.
/body/vitality-blueprint/is the secondary surface — listed prominently from the body room index and from the series’ first chapter, but not the default click-target.- Both surfaces share the same source-link path to media.gf.cx.
Editorial bridges (the part that might need hand-touch):
The threaded version benefits from short connective sentences between chapters — “Chapter 1 established the muscle-bone-T loop. Chapter 2 maps the vascular system that those mechanisms route through.” A pure concatenation reads slightly choppy. The script can leave a <div class="chapter-bridge"></div> placeholder that Opus polishes in one pass after the script runs. Cheap; doesn’t need to be automated.
Trigger to build:
When chapters 1 through the back chapter (Ch26 90-Day Roadmap, per the substrate ToC) are all voiced. Today: Ch1-8 done; remaining = Ch9 Supplements · Ch10 Hydration · Ch11 30-Day Meal Plan · Ch12 Mobility · Ch13-22 (greppable from substrate) · Ch23 FAQs · Ch24 Long-Term Vitality · Ch25 Conclusion · Ch26 90-Day Roadmap. Realistically ~10-15 more chapters.
Anti-pattern: building the threaded view at Ch5 or Ch8. Premature stitching means re-stitching every time a new chapter ships. Wait until the series is closed, then run the script once + Opus-bridge once.
Sister memories:
project_happiness_pdf_ingest_pipeline_2026-06-06— the ingest + cleanup that produced these chaptersfeedback_duality_model_proven_build_pattern_2026-06-06— the model-tier teaching loop that voiced the chapters; the long-form view is the proven build’s archival outputfeedback_head_check_audit_pattern_generalise_at_3rd_use_2026-06-06— sister to this: the threading script is the first use of the chapter-stitching pattern; don’t generalise to “any happiness.gf.cx series” until a second series triggers