content-architect

What problem does it solve?

Provide a disciplined process and an implementation-ready blueprint to decide what screens/pages to build, how content should be organized, and which journeys and navigation will deliver user and business value. It reduces guesswork in early product decisions, prevents redundant content, and gives developers and designers a concrete spec instead of vague wireframes.

Core Features & Use Cases

• Top Tasks Analysis: Identify the 5-10 tasks that drive product value and use them to seed journeys and screens.
• Journeys → Screens → Navigation: Map critical user journeys, derive a minimal screen inventory, and design navigation that passes the 4S test.
• Prioritization & Gates: Classify screens as MVP / v2 / nice-to-have and require validation gates before progressing between phases.
• Developer-Ready Blueprint: Produce content-first screen specs, real microcopy, and a Mermaid sitemap suitable for direct implementation or handoff.
• Use Cases: Showcase sites, SaaS dashboards, CLI-to-frontend migrations, and redesign audits where the first decision is "what to build".

Quick Start

Create an MVP content architecture blueprint for a small service website by describing the product, audience, business goal, current state, and any constraints.