Features / Multisite & multilingual
All your sites, all your languages, one admin.
A single Plumixia instance hosts as many sites as you need. Each has its own identity — domains, languages, theme, media library, publishing settings — and you manage them all from one place.
One site = one complete workspace.
Pages, layouts, shared components, object types, media and theme are scoped per site. An editor can have rights on one site and not on another.
- Several domains per site — with and without www, staging domain, final domain
- Languages and default language set site by site
- Auto-publish can be enabled per site (handy for staging)
- Notification e-mails specific to each site
- Roles per site: media, content, developer, administrator
Language variants that are linked, not copied.
Page groups
The French and English versions of a page belong to the same group. The CMS knows they match and generates the hreflang tags.
Translatable fields
In a layout or shared component, a single block holds one value per language: one header, one footer, for the whole site.
Assisted translation
Creating a variant automatically translates the title, description and metadata (DeepL by default). The rest is translated block by block, then reviewed as a draft.
Multisite and languages in practice
Can two sites share a layout?
Each site has its own layouts, so a change on one site never breaks another. To start a new site from an existing one, you clone the pages and reuse the theme; an AI agent can do this setup over MCP.
Can URLs differ by language?
Yes. Each variant has its own URL (/tarifs and /en/pricing, for example) and its own title and description.
What if a page isn't translated yet?
It simply doesn't exist in the other language: no empty page, no broken hreflang link. You publish each variant when it is ready.