Architecture

Workspace boundaries for web, docs, Storybook, packages, CLI, and MCP.

View Markdown

The workspace separates public surfaces by responsibility:

  • apps/web serves the portfolio and profile/resume LLM surface at mun.digital.
  • apps/docs serves public reference docs at docs.mun.digital.
  • apps/storybook serves the static app-component workbench at storybook.mun.digital.
  • packages/cli publishes the mundigital CLI and local stdio MCP server.
  • packages/tokens distributes generated token CSS.

Portfolio components live in apps/web; they are not a workspace package. Turborepo coordinates build tasks so shared token and public interface changes are visible to affected apps.

Static Documentation Routes

Docs pages are generated from local Markdown-compatible content and expose matching .md routes for source-oriented readers. Markdown and LLM route handlers are static-safe and do not use request-time APIs.

Canonical metadata is page-specific:

  • https://docs.mun.digital for the docs homepage.
  • https://docs.mun.digital/mcp and https://docs.mun.digital/cli for the primary agentic reference surfaces.
  • Matching page URLs for architecture, agent workflow, tokens, components, and Storybook supporting docs.

Public Data Boundary

The docs and Storybook apps document public interfaces and design-system workflow only. They must not import packages/profile/data/resume.json, generated resume artifacts, or private profile fields.

CLI and MCP docs can describe sanitized public outputs, but examples must use placeholders or sanitized public artifacts only.