What changed

• registers TanStack Markdown and TanStack Highlight as public UI & UX libraries
• adds library metadata, navigation, stats, sitemap, OG colors, maintainer ownership, versioned routes, and redirect coverage
• replaces the shared content-tools template with two independent marketing pages
• gives Markdown an editorial publishing story around its public AST, deliberate syntax profile, safety contract, renderer parity, extensions, and bundle size
• gives Highlight a code-lab story around selective language registration, synchronous output, semantic CSS themes, embedded-language scanners, annotations, corpus benchmarks, and explicit tradeoffs
• sharpens both library taglines and descriptions across discovery surfaces

Why

Markdown and Highlight solve adjacent problems, but the shared landing-page structure flattened the product differences. Their marketing now follows the architecture and constraints that make each library distinctive.

Impact

Both libraries appear across library discovery and navigation with launch pages that explain when to choose them, what they deliberately leave out, and how they compose without implying that one depends on the other.

Validation

• pnpm test
• type-aware lint and TypeScript checks
• light and dark mode visual checks at desktop and 390px mobile widths for both landing pages
• docs source validation: Markdown 24/24 paths, Highlight 30/30 paths