Skip to the content.

Application architecture

As-built architecture for @tgmc/web (Nuxt 4 + Nitro) in the TGMC Nx monorepo. Diagrams document what exists today — not a target-state redesign.

Live SVG on /product (AppArchitectureDiagram) shares the content-API topology without a Mermaid runtime. Full Mermaid sources live in the pages below and render in-app under /docs.

Diagram set

Diagram Type Page
System context & containers C4 L1–L2 System C4
Four-environment deployment Deployment System C4 § Deployment
API inventory & store UML Component / class API & store UML
Site map & page wireframes Wireframes Site wireframes
Complex process sequences UML sequence Process sequences

Admin process architecture and UML — current session, CRUD, CDN, media and deployment diagrams.

Context (short)

Public chrome: AppPrimaryNav is About / Work / Gallery / Code / Writing. Docs, AI Lab, and Process are Work sub-nav (AppWorkSubNav on /work and /work/[slug]). Full IA: portfolio-august-launch.md.

Page copy, gallery, and case studies load through Nitro (GET /api/content/:collection) so client WASM SQLite is not used during SPA navigations. Durable contact messages and blog posts use MessageStore / BlogPostStore adapters selected by DATA_BACKEND or the effective environment (local SQLite; development/test/production DynamoDB; PostgreSQL opt-in). Test/prod HTML and API run on Lambda behind HTTP API; hashed assets go to S3/CloudFront.

Media Library architecture and UML — current components, class model, upload/processing/retrieval/deletion sequences, lifecycle and deployment.

Runtime details

Runtime boundaries and flows covers import boundaries, docs delivery, preferences, media processing, backend selection and promotion.