Architecture Insight

The Sugartown 2.0 System Contract

Sugartown 2.0 establishes a non-negotiable architecture: Python is the single source of truth; WordPress is a stateless rendering layer.

This eliminates CMS drift, enables reproducibility, and prepares the platform for a headless future.

Core Principles

• Python as Canonical: All content, metadata, and tokens exist in sugartown-cms. If it is not in Python, it does not exist.
• WordPress as Renderer: WP holds no unique content; it displays structured data via custom templates.
• Structured Gem Model: Gems are topological knowledge nodes, not posts in a feed.
• Two-Repo Boundary: sugartown-cms (content, logic, tokens) vs. 2025-sugartown-pink (presentation).
• Mini Design System: Tokens define a portable visual identity shared across WP, Figma, and future React front ends.
• Reproducible Publishing: Hashing, backups, and visualization scripts ensure deterministic builds.

Repository Structure

The codebase enforces a strict separation of concerns between the Content Engine (Data) and the Rendering Layer (Theme).

Reference Artifacts

The following strategic documents govern the execution of this architecture:

Why This Matters

By treating content as code, Sugartown CMS transforms static pages into a programmable dataset. This elevates the platform from a simple management tool into a knowledge engine—structured, portable, and platform-agnostic.