Structured content
Articles, forms, galleries, banners, video, files, and custom content share a coherent authoring model.
RED-CMS / Custom content platform / 2012—2026
A content system that learned to change.
RED-CMS began as a practical publishing tool. Across five major releases, it became a reusable product: one structural foundation that can support distinct industries, websites, and editorial needs without becoming a different CMS every time.
RoleFounder and Product Architect
Active installations03
Major releases05
Product evolution14 years
Public sourceGitHub 01
The product thesis
Different industries. One adaptable structural core.
The challenge was not simply learning how a CMS stores pages. It was understanding which parts should remain stable—content relationships, editorial controls, layouts, permissions—and which parts should adapt to each organization.
That distinction shaped RED-CMS into a platform rather than a succession of one-off websites. Client presentation and data stay separate; the product architecture remains reusable.
02
Five releases / one continuous product
Built in layers, not replaced in cycles.
Each release reflects a larger understanding of the product: authoring first, then flexibility, then modernization, portability, and safer long-term operation.
- Version1.0
The first working content system
- Version2.0
A broader administration model
- Version3.0
A more adaptable publishing structure
- Version4.0
Modernization without abandoning history
- Version5.0
A portable, compatibility-first release
03
Architecture as an editorial tool
The interface exposes the model without exposing the machinery.
Editors work with recognizable content and layout decisions. Underneath, the product preserves relationships between structure, content, presentation, and public output.
Reusable layouts
Page structures and named positions let editors arrange different experiences without rewriting templates.
Independent themes
Presentation can change by site while the administration, content model, and operating rules remain stable.
Protected continuity
Compatibility, migrations, rollback paths, and isolated client data make modernization deliberate instead of destructive.
AuthorCreates and organizes content
→Core modelPreserves structure and relationships
→Layout + themeAdapts presentation by installation
→Public sitePublishes the appropriate experience
04
Structured flexibility
Form Builder
Reusable does not mean rigid.
Purpose, fields, validation, delivery settings, and page placement belong to one understandable workflow. The same principle extends across articles, galleries, layouts, themes, navigation, and site-wide settings.
- Content tools organized by editorial purpose
- Visual layout structures with responsive maps
- Theme presentation separated from core administration
- Versioning, migrations, validation, and rollback
05
The architecture in use
Three active installations. Three different content realities.
The value of the product is visible in its range: the structural core supports creative education, culinary publishing, nonprofit storytelling, and distinct editorial workflows.
- 01
adrianagranobles.com
Music education and creative practice
- 02
chefmama.com
Food and culinary publishing
- 03
janelleswishingwell.org
Community and nonprofit storytelling
What this work demonstrates
Product architecture is the discipline of deciding what should change—and what should not.
RED-CMS 5.0 is a clean, reusable distribution with client themes, media, content, and databases intentionally kept separate. That boundary protects both product evolution and client continuity.
Explore the public repositoryProduct captures and installation names are shown with permission. Private configuration, credentials, databases, and operational material are intentionally excluded.