Project: Sugartown CMS Architecture

This project began with a simple request: “Write a blog post about Gemini 3.” It escalated into a full-stack systems exercise because, as a Product Manager, I fundamentally reject unstructured data.

The Challenge: Breaking the Blob

Traditional CMS platforms treat knowledge as a blob—title, body, timestamp—buried in a chronological feed. That model works for publishing, but it fails for thinking.

I wanted a Knowledge Graph: a system where insights are treated as atomic nodes that can be queried, filtered, and recombined across contexts.

The Architectural Approach

The solution was a deliberately hybrid system:

Python as Source of Truth for structure, taxonomy, and publishing logic WordPress as Rendering Layer, not authoring environment Gems as a custom post type optimized for topology over chronology

The Outcome

The system now behaves like a living product. I can refactor the entire portfolio by changing a single Python file. The green checkmark in the terminal has become my favorite UI.

Equally important: the architecture now supports narrative. The Knowledge Graph is no longer a curiosity—it is the organizing principle of the site.

Next: for how this system continues to evolve.

1. Platform Roadmap (strategic context)
2. Knowledge Graph Roadmap (subsystem evolution)