Clement Yuen
Back to case study

Architecture explorer

Next.js Blog

Interactive system map for this project. Select a node to inspect technology, role, integration, and responsibilities.

Sibling writing app: the Angular host links out; Next.js owns content routing and markdown posts.

Node types

  • Frontend
  • External service
  • Infrastructure

Architecture decisions

Decision · reason · alternative · trade-off for each major fork in the road.

Decision

Sibling Next.js app instead of an Angular blog feature

Reason
Content authoring and rendering fit the Next.js ecosystem; the host stays focused on resume + demos.
Alternative
Markdown rendering inside the Angular portfolio
Trade-off
Two front-end runtimes to maintain; cross-app navigation is a full page load.

Decision

File-based posts over a headless CMS

Reason
Zero infra for a small corpus; diffs are the editorial workflow.
Alternative
CMS-backed content API
Trade-off
Non-technical editing is harder; scaling editorial roles later would need a different model.