Theme Customization
Customize layout, presentation, and design language without inventing features that do not exist.
Theme customization in Curator starts with presentation and layout choices, not with pretending there is a separate theme engine when there is not.
What is safe to customize
In the current stack, the most practical theme work happens in:
- public templates and route output
- shared layout wrappers
- stylesheet variables and component classes
- marketing and marketplace page sections
If you are working on Curator Marketplace itself, most of the visible customization lives in the rendered HTML and the shared CSS file.
Start with the design system
Curator already uses a shared visual language for spacing, buttons, cards, and page shells. Reuse those existing classes before introducing new one-off patterns.
That keeps the marketplace, docs, support pages, and engine marketing pages feeling like one product instead of separate demos stitched together.
Recommended customization workflow
- Change copy and structure first.
- Adjust layout containers and spacing second.
- Introduce new card or section variants only when the existing system is not enough.
Keep customization truthful
Do not add labels, badges, or navigation items for features that are not really available yet. A cleaner interface with fewer promises is better than a polished mock that overstates the product.
Where to go next
If your change needs behavior rather than presentation, plugin development is the better next page.