Editorial back offices for France Télévisions

The context

France Télévisions, France’s national public broadcaster, runs a dense digital ecosystem: many editorial platforms, newsrooms publishing around the clock, and internal tools that have to keep up — without ever stopping.

Since January 2024 I have been working as a Drupal/Symfony consultant on back offices within the group, as part of integrated teams, on agile cycles.

The problem

An editorial back office is not a brochure site: it is a working tool used all day long by teams who cannot afford to wait. The typical stakes of this kind of platform:

• a Drupal 10 back office for content management, integrated with a Symfony front end that consumes its data through an API;
• rich content models (programmes, articles, contributions, media) that evolve with editorial needs;
• publishing workflows and fine-grained permissions per role and scope;
• compliance with W3C accessibility standards — a hard requirement for a public broadcaster;
• changes shipped regularly to production, with no regressions and no downtime.

What I do

Senior development on the Drupal 10 side: content modelling, custom business modules, API endpoints for the Symfony front end, roles and permissions, accessibility, code reviews. All of it within an industrialised organisation — GitLab for version control, Jenkins for CI/CD, multiple environments, acceptance testing with editorial teams.

The result

Editorial tools that do their job, day after day: regular production releases, a maintainable and accessible technical foundation, and editorial teams that are autonomous with their content.

Out of respect for client confidentiality, this case study is deliberately kept general. Details can be discussed directly, within the limits of my engagements.