Features / Layouts & components
A brand defined once, respected everywhere.
Theme, layouts, shared components: Plumixia separates what is common from what belongs to each page. Your design stays free — HTML and CSS classes of your choice — and consistent from page to page.
From the most general to the most specific.
Theme
Stylesheet, JavaScript, <head> tags (fonts, favicon), body classes. Compiled Tailwind or hand-written CSS, served from the media library or inline.
Layout
The common structure: header, navigation, page content area, footer. Each page picks its layout; a dedicated layout serves the 404 page.
Shared components
A banner, a callout, a menu reused by reference across pages or layouts. Change it in one place, it changes everywhere.
Fragments
Snippets injected automatically into every page or every form: a tracking tag, a GDPR notice, a common field.
The components that ship with the CMS.
| Family | Components | What for |
|---|---|---|
| Blocks | HTML block, widget, script, style, head, body start and end | Free content and code injection exactly where needed |
| Containers | Container, page container, object container, modal | Structure the page, display a data object, open a dialog |
| Repeaters | Generic repeater, article repeater, category repeater | News lists, catalogues, sections generated from data |
| Interactive islands | Tabs, accordion | Collapsed or tabbed content, no JavaScript to write |
| Forms | Form, step, field, captcha, submit, confirmation… | See Forms |
| Tracking | A/B test, GTM, pixel, analytics, tracker, consent | See Marketing |
| SEO & navigation | Structured data, redirect, search | See SEO |
Any component can be limited to a device type (desktop, tablet, mobile) and carries its own CSS classes.
Your HTML, your classes.
Plumixia doesn't impose a UI framework. Blocks accept HTML and any classes: Tailwind, Bootstrap, an in-house design system. This very site, for example, uses a hand-written stylesheet.
- Typed schemas: each component declares its properties, tabs, required and translatable fields
- Controlled nesting: a component knows where it may be placed (no form inside a form)
- Page cloning to start from an existing page
- Readable by an AI agent, which reads the schemas before building a page