WordPress, Drupal, Pimcore and Strapi, deployed, configured and extended for your business
Four open platforms to publish, structure and deliver your content and your data. We deploy them, configure them around your business and bring them in line with the law that applies to you.
What these platforms cover as standard
Compliance, where you operate
The platform is the same whatever the country. What changes is the configuration: chart of accounts, tax rates, exchange formats, transmission obligations. We set out France and Switzerland below because they are the two our clients meet most often. For another country the principle does not change: we start from what local law requires, and configure accordingly.
France
A public website collects data and sets trackers. The GDPR requires consent gathered before anything is stored and as easy to withdraw as it was to give, and accessibility applies to public bodies and those acting for them. The platform serves the pages; it carries neither the consent capture nor its log. We set up the banner, the record of choices, the retention periods and the accessibility checks.
Switzerland
The revised Federal Act on Data Protection asks for the same prior information and the same retention periods. The mechanisms are the same, the configuration differs — and hosting can stay in Switzerland where the nature of your content calls for it.
Each country you operate in is handled on its own terms, with its own rules and formats. You still deal with one person, however many of them there are.
How we work
Integration in practice
These four platforms do not do the same job, and that is where the choice is made. An editorial site is not run like a data repository, and an administration interface is not a public front. We start from what you publish, who writes it and who reviews it, before naming a platform — then we carry the existing material across, content and media included, rather than starting from a blank page.
The differences between them are deliberate and configurable. Multilingual content, for instance, ships in the core of Drupal while WordPress does not support it natively — its own documentation says so — and is then handled by extension. Where the standard stops, we build: when the audience multiplies at a stroke, we separate editorial production from delivery, which is the subject of our decoupled architectures; when content becomes a path rather than a page, we build learning platforms; when publishing becomes a procedure, a one-stop service centre.
How we build is set out on Custom Development, and how we look after what we deliver on Support & maintenance.
The modules we have built around the core
The standard covers a great deal. It stops at a few specific points: those are the ones we build.
Product master records
These platforms carry custom fields, not a product repository: no attributes by family, no completeness by channel, no approval cycle. With Pimcore the platform itself ships seven bundles — the commerce framework and the Data Hub are distributed separately.
PIM & Product RepositoriesSubscriptions and access to content
None of the four bills a subscription or decides, article by article, what stays open and what is paid for. Drupal ships no commerce module among its seventy-six.
Subscription Management & PaywallsMember space and community
A user account is not a profile: no activity feed, no relationships between members, no moderation queue with its reports. With Strapi, review workflows belong to the Enterprise plan.
Community Platform & Member ProfilesPublishing open datasets
Publishing data is not publishing an article: standard formats, versions, licences and map-based visualisation have no equivalent as standard.
Observatories & Open DataVideo delivery
The media library files a video away; it does not encode it at several qualities and does not stream it live.
Streaming Platforms (VOD/Live)Your sites after launch
A public site is exposed at all times. WordPress, Drupal, Pimcore and Strapi patch at a steady pace, and an abandoned extension becomes an open door. Accessibility and consent are verified over time, not once at handover.
We apply the patches, we replace abandoned extensions before they become a risk, and we recheck accessibility as you publish. BUILD puts the site online; RUN keeps it there.
Support & maintenance