Workspace

Publishing operations
Sync healthy
3 approvals pending
2
Approval waitingSummer homepage launch is still open.
Media queue7 assets are waiting on crops or alt text.
EC

Platform architecture

Structured for many sites, languages, and publishing needs.

The platform story here is deliberately practical: a shared CMS, clear content primitives, and a frontend that can evolve without making editors pay for technical complexity.

Core modelMulti-site + multilingual
Delivery patternSSR public web + future APIs

Layer

Presentation layer

A Vercel-hosted frontend that stays fast, indexable, and easy to extend with new public pages or section layouts.

Layer

Editorial layer

Reusable page templates, structured blog posts, events, and block-based sections that keep publishing flexible but consistent.

Layer

Operational layer

Site administration, language setup, user access, and global configuration designed for a distributed editorial network.

Reusable blocks

Common CMS blocks plus a few network-specific modules.

Rich text and rich media

Image + text combinations

Calls to action and button groups

Gallery and carousel sections

Video embeds and social links

Document downloads and simple lists

Testimonials and impact metrics

People directories and map-based views

Newsletter, alerts, and event modules

Architecture notes

Built to stay flexible without becoming fragile.

Keep content and presentation separated so the same data can be used in future APIs.

Support multilingual content at the site level rather than forcing translation into one global bucket.

Use SSR for public pages so search engines and social previews stay reliable.

Allow super admins to add sites and languages without custom deployment work.