FullStack VC v0.1.1 — Docs Prose Typography
A patch on v0.1.0's how-to engine: the docs pages now articulate their own prose. Tailwind's preflight had been stripping every heading bare; a shared docs-prose.css gives guides, use-cases, and tool pages real typographic hierarchy from a single source — and the redundant body title is gone.
Why Care?
v0.1.0 shipped the two-perspective how-to engine — but its pages rendered raw markdown with no prose styling, so every section heading sat at body size. A how-to you can't scan isn't much of a how-to. This patch makes the content readable.
What's New Since v0.1.0
Shared
docs-prose.css— one global stylesheet articulating the LFM /AstroMarkdownoutput (h1–h4, lists, blockquotes, inline code, tables, rules, images), applied via a.docs-prosewrapper on the guide, use-case, and tool body. Mirrors the site'sMarkdownReadertreatment, so the docs read like the rest of the long-form content and inherit all three theme modes.Redundant body title removed — the markdown body's
# Titleis gone; the page header already renders it, and bodies now start at##(theMarkdownReaderconvention).
Why It Was Bare
The project's own house rule names it: Tailwind's preflight resets headings to base size, so markdown rendered without scoped prose styles inherits that. The site solves it twice already (the session page; MarkdownReader), but the brand-new docs routes had neither. We factored the treatment into one global stylesheet instead of copying a third scoped block.
Operational Hand-Off
Tag
v0.1.1— a patch on v0.1.0 (styling/readability only; no behavior or schema change).package.jsonbumped0.1.0→0.1.1to match.No new type debt;
astro checkheld at its pre-existing baseline.
What's Next
Unchanged from v0.1.0: the docs chrome (left-nav, right-hand TOC, prev/next pagination) is specced and waiting, and the engine wants more guides to pressure-test the two-perspective structure.