FR/ENRequest a quote
Culture & Media Sector

Custom cultural sites and editorial CMS:ecosystems built to last.

Multi-site, multilingual, autonomous editorial teams: what cultural institutions expect from a website that publishes extensively, over time, and with a strong identity: foundations, museums, publishers, and media.

Discuss your project View our cultural work
Art Explora
Les Nouveaux Éditeurs
01 — Sector challenges

A single site is never enough for long.

Every exhibition, label, or program eventually demands its own space. The real question isn’t whether the ecosystem will grow, but whether it will grow coherently—and who will maintain it daily.

A proliferating ecosystem

Exhibitions, programs, labels, events: each initiative eventually calls for its own site, and the whole must remain coherent without overshadowing individual identities.

Editorial teams that need to publish fast

Programming, catalogues, authors, press releases: content arrives at the pace of the cultural season—your system must keep up.

An artistic direction to uphold

In the cultural sector, artistic direction is paramount and must be respected, regardless of content type or site evolution.

Demanding budgets over time

Grants, patronage, annual cycles: a cultural website must live and evolve for years. A solid, scalable technical foundation is therefore essential.

02 — What we build

Four focus areas, depending on what’s holding you back.

A site ecosystem to structure, a brand identity to faithfully integrate, editorial workflows to automate. Rarely all at once—framing helps prioritise.

Multi-site ecosystems & editorial CMS

A shared foundation, sites per entity, program, or label, and explicit content governance: who publishes what, where, in which language. The CMS is shaped around your real-world objects: exhibitions, works, authors, publications, events.

PayloadMulti-siteMultilingual
Websites & CMS

Editorial brand websites

Faithful integration of designs: your art direction remains the reference, and we ensure it’s accurately delivered in production.

Pixel-perfect integrationAD preservedCo-contracting
UX/UI Design

Editorial automation & CRM

Content flows between sites, CRM sync, newsletters, catalogue updates: everything your teams currently copy manually from one tool to another, especially during peak programming seasons.

n8nCRMNewsletters
Automation

Sovereign AI on your archives and catalogues

Natural language search across archives, catalogues, and document collections, with systematic source citation.

RAGCited sourcesSovereign
AI assistants on your data
03 — Proof

Two cultural ecosystems, sustained over time.

An art foundation and a publishing group. In both cases: multiple sites, multiple identities, and a relationship that endured.

Art ExploraCultural foundation · Multi-site ecosystem
Multi-siteMultilingualCRM

Four years of support, an ecosystem that grew with the foundation.

Main foundation website, dedicated space for the Artexplorer museum boat, multilingual content, and CRM automations: a site ecosystem built and expanded with each new program. Over one million page views per year, with ongoing support since 2022.

Read the Art Explora case study
Les Nouveaux ÉditeursPublishing group · House websites

Multiple houses, multiple worlds, a group-wide coherence.

Showcase sites for the group’s imprints: Éditions La Tribu, Maison Pop, and other labels. Each reflecting its own editorial identity, all bound by an overarching coherence. Branding and user journeys designed by We Think Elastic, development by Scroll. A long-term partnership with multiple projects delivered.

Multi-siteCatalogues & AuthorsWe Think Elastic
Read the case study
04 — Our approach

Three commitments that stand the test of time.

What we establish during scoping—and why the institutions we support evolve their site for years rather than rebuilding it.

Execution in service of creation

We collaborate with your design agency or in-house art director. The mockups are the reference: our role is to implement them faithfully, including costly design choices we flag, without making decisions on your behalf.

Editorial autonomy as a design criterion

A CMS designed for editors, not developers: clear templates, fields named in your business language, publishing without tickets. It’s a design criterion, not an add-on training at the end of the project.

Longevity as the standard

Up-to-date documentation, real handover, ongoing support. A cultural ecosystem is maintained and evolves with the programming; it isn’t discarded every two years.

05 — Stack & Method

A lean stack, built to last.

Proven, recruit-friendly technologies, a CMS your teams can truly manage, and data hosted in France.

Front

Next.js
React
TypeScript

CMS

Payload
Webflow
Editorial templates

Back / Data

PostgreSQL
Multilingual
API

Automation

n8n
CRM
Webhooks

AI

Mistral
RAG
Cited sources

Hosting

OVH
Scaleway
GDPR

Webflow when it’s the right tool: for a showcase editorial site with a strong art direction, without high volumes or business needs. As soon as there’s a site ecosystem, structured multilingual content, high content volumes, or integration with your tools, custom development is required.

06 — FAQ

Frequently asked questions

The questions that come up during scoping with a foundation, museum, publishing house, or communications department.

It’s a design requirement, not a post-project option. The CMS is shaped around your real-world objects—exhibitions, works, authors, publications, events—with clear templates and fields labeled in your terminology, not the developer’s.

Natively. Multilingual is built into the content model: each piece of content exists per language, with its own URLs, tags, and SEO. An institution serving international audiences cannot rely on a translation widget layered over a monolingual site, as foreign versions must be indexable and editable just like the French one.

For public institutions or those publicly funded, yes: RGAA applies, and an accessibility statement is mandatory. We address accessibility from the start—semantic structure, contrast, keyboard navigation, and text alternatives for artwork visuals—rather than as a post-audit fix. Sector-specific obligations are detailed on our Public Sector page.

You do. The code is delivered to your repository, content is exportable, hosting is transferable, and documentation is yours to keep. For an institution accountable to a board, patrons, or public funders, reversibility isn’t a sales pitch—it’s a necessity.

Yes, and it’s a collaboration model we’ve refined. Your agency or in-house design team provides the identities and mockups—they’re the reference. Our role is to faithfully implement them in production: typography, grids, animations, interface states, and to flag design choices that may incur maintenance costs, without making those decisions for you.
Let’s talk

Building a multi-site ecosystem, revamping an editorial CMS, or leading a redesign without losing your content? Let’s discuss identities, volumes, and timelines.

Contact details
20 Rue des Taillandiers
75011 Paris
Response within 24 business hours.