Case Study · Internal System
SpicaCMS
A custom CMS direction for content-heavy digital products.
Internal Systems
Concept
CMS · Internal Platform · Publishing System
Overview
Project overview
SpicaCMS is a planned CMS system for projects that need structured content, custom editorial workflows, SEO pages, directories, and product logic that is hard to fit into a generic CMS.
Role
Role and responsibilities
The work covered product thinking, engineering decisions, and practical delivery.
- CMS planning
- Data model planning
- Editorial workflow planning
- Django backend structure
- Next.js frontend structure
Challenge
The challenge
Many publishing products start with WordPress and later need custom models, APIs, and frontends. SpicaCMS is a direction for projects where custom structure matters from the start.
Approach
The approach
- 01Planned reusable modules for posts, pages, taxonomies, authors, directories, media, and SEO metadata.
- 02Prepared a Django backend direction with a clean API for public frontends and admin tools.
- 03Designed a Next.js frontend path for fast public pages and reusable layouts.
- 04Kept the system suitable for travel portals, music portals, directories, and niche media products.
Outcome
What it delivered
- A reusable CMS blueprint for future content products.
- A clearer alternative when WordPress is too limiting for a project.
- A structure that can power media sites, directories, and product pages.
- A base for future automation, AI-assisted drafts, and SEO workflows.
Preview
Product preview
SpicaCMS · publishing system
Custom CMS structure for content products and directories.
Architecture
System overview
A simple view of the main product layers.
Architecture
Editors
Admin panel and editorial workflowsAPI
Django content APIData
PostgreSQL content modelsFrontend
Next.js public pagesAutomation
Future AI and SEO workflowsDjangoNext.jsPostgreSQLCMSPublishing
