•4 min read
Five diagrams explain this blog's content Treemap: article counts, Payload relationships, data flow, in-place exploration, and the border-layer fix.
Writing
Five diagrams explain this blog's content Treemap: article counts, Payload relationships, data flow, in-place exploration, and the border-layer fix.
Why I chose Giscus and GitHub Discussions for blog comments, how immutable post IDs keep bilingual threads together, and how the production cache fallback works.
How I replaced a fixed handwritten SVG with CMS-editable text, server-side generation, content-addressed Blob artifacts, and lightweight SVG playback—and debugged two animation failures.
A practical account of an embedded Payload CMS MCP server: components, request flow, Vercel deployment, permissions, health checks, and rollback.
Why Open Graph images matter for social sharing, how traditional approaches generate them, and how this site uses headless browser screenshots with an async queue to produce pixel-perfect OG images automatically.
This post explains how the platform stays maintainable by separating schema ownership, public delivery, and reusable presentation across apps/admin, apps/www, and @repo/ui. It also shows how generated Payload types, Markdown-first posts, and TurboRepo workflows keep content, frontend code, and local development aligned.