Case study · The proof of the protocol

A complete web ecosystem, built in ~3 weeks

La Cathédrale — a multi-service platform delivered by one person driving the W.O.L.F.© protocol

This is a technical demonstration, not a product pitch. A single, real, public project — an editorial platform, a 24/7 radio, video streaming, a members’ community, an online shop and a full-text indexed corpus of thousands of documents — designed, built and put online in about three weeks by one person.

Set against a conventional workload estimate, the same scope lands on the order of 550 to 650 person-days and roughly ten months for a team of about fifty. That gap — a productivity ratio of 1:15 to 1:50 — is the whole point of this page.

≈ 3 weeks 1 person 1:15–1:50 Productivity vs conventional methods

Visit the live site See the numbers

Live in production

See it for yourself

Everything described on this page runs in production today. The site, the radio, the streaming and the corpus are all publicly reachable.

abbejulio.fr

The idea & the scope

One brief, a whole ecosystem

The commission was not a single site but a coherent digital ecosystem: publish, broadcast, stream, gather a community, sell, and make a large documentary corpus searchable — under one identity, in many languages.

A multi-service platform, not a brochure site

“La Cathédrale” (abbejulio.fr) brings together, behind one brand and one design system, six services that usually each demand their own project and their own team: a multilingual editorial platform, a 24/7 online radio, a video-streaming channel, a members’ community, an online shop, and a full-text indexed corpus of thousands of documents.

The engineering interest is exactly this: every one of these bricks is a real production system — a broadcast chain, a streaming server, a search index, an e-commerce flow — wired together and operated as a whole.

Editorial platform

A PHP front controller, clean multilingual URLs, SEO and an architecture wired for 17 languages.

24/7 radio

An always-on online radio with automated programming and a live now-playing feed.

Video streaming

A self-hosted video channel (“Le Parvis”) for on-demand and streamed footage.

Indexed corpus

Thousands of documents, structured and searchable full-text, behind access control.

Community & commerce

Member accounts, a membership flow and an online shop, all under the same identity.

Back-office & operations

Editorial back-office, an audio-conversion pipeline and backups proven restorable.

Mockups & captures

What it looks like

Reserved slots for screenshots of the live platform. Drop real captures in without touching the layout.

Home Screenshot — reserved slot

The editorial home — gazette mosaic, EN/FR.
Radio Screenshot — reserved slot

The 24/7 radio console and now-playing.
Corpus Screenshot — reserved slot

Full-text search across the indexed corpus.
Streaming Screenshot — reserved slot

The self-hosted video channel.
Shop & members Screenshot — reserved slot

The online shop and the members’ area.
Back-office Screenshot — reserved slot

Editorial back-office and operations.

What was delivered

The features shipped

A non-exhaustive list of the systems actually built and put into production — the concrete surface behind the productivity claim.

Multi-service architecture

Six production services orchestrated behind one edge, one brand and one design system.

PHP front controller & clean routing

A single entry point, clean URLs, per-page SEO descriptors, no framework bloat.

Internationalisation (EN/FR + 17 languages)

A pointed-key translation engine with English fallback and an architecture ready for 17 languages.

Full-text indexed corpus

A structured SQLite corpus of thousands of documents with a read-only access library and full-text search.

Documentary ETL pipeline

Import, normalisation and structuring of heterogeneous sources into the corpus schema — rights status tracked per document.

24/7 radio chain

A self-hosted broadcast stack with automated programming and a live metadata feed.

Audio broadcast pipeline

A file-watcher that converts dropped m4a/wav files to broadcast MP3 and injects them into the radio automatically.

Self-hosted video streaming

A PeerTube channel for streamed and on-demand video, under the platform’s own domain.

E-commerce & membership

An online shop and a membership flow, with member accounts and a private area.

Community spaces

Member accounts, a live chat and community areas tied to the same identity.

Technical SEO

A multilingual sitemap, hreflang alternates, canonical URLs, Open Graph and JSON-LD structured data.

Accessibility (WCAG)

Semantic structure, keyboard and screen-reader support, contrast held to AA/AAA targets.

Under the hood

The services, wired together

How the pieces fit: an edge reverse proxy fronts the editorial site and three self-hosted services, all fed by an industrialised delivery chain.

Edge reverse proxy

An nginx edge terminates TLS and routes each sub-domain to its service — including access control in front of the corpus.

Editorial site (PHP)

The front-controller platform: routing, i18n, SEO and the design system that unifies every service.

Radio service

A self-hosted AzuraCast station handles the 24/7 stream, its library and its now-playing API.

Streaming service

A PeerTube instance hosts the video channel on its own sub-domain.

Corpus store

A SQLite corpus kept outside the web root, read through a dedicated PHP library, exposed behind access control.

Audio conversion watcher

A systemd watcher transcodes new audio to broadcast format and hands it to the radio — no manual step.

Delivery chain

Git worktrees, per-file locking (zero parallel-write conflicts) and a scripted deploy move code from dev to staging to production.

An industrialised chain — honestly scripted, not a heavyweight CI vendor.

The demonstration

Real time vs the conventional estimate

The same scope, measured two ways: what it actually took, and what conventional workload ratios would have predicted. The gap is the productivity of the protocol.

What it actually took

Real delivery

Elapsed time: ≈ 3 weeks
Team: 1 person
Scope: 6 production services

The result 1:15 — 1:50 Productivity vs conventional methods

Depending on how conservatively the equivalent is counted, the protocol compresses the work by a factor of fifteen to fifty. This is a demonstration of productivity, not a benchmark claim.

Conventional equivalent — an estimate

Estimated equivalent

What the same scope would represent under conventional workload ratios, at industry day-rates.

Effort: ≈ 550–650 person-days
Budget: ≈ €350,000 excl. tax
Duration: ≈ 10 months
Team: ≈ 50 people

A defensible methodological estimate — orders of magnitude, never figures set in stone.

The demonstration

How the estimate is built

The equivalent is derived from the delivered scope — six independent production services, multilingual, with a broadcast chain, a streaming server, a search index and an e-commerce flow — costed with conventional per-service workloads and mid-market day-rates. It is deliberately framed as a range.

Scope counted service by service, not as one site.
Mid-market day-rates, not the cheapest offshore floor.
A range, not a single number — orders of magnitude.
The recipe stays protected; the result is verifiable.

What this proves

Not a product for sale — the proof of the protocol

La Cathédrale is not on the shelf. It exists to show, on a real and public system, what the W.O.L.F.© protocol compresses: months of a large team into weeks of one person, at industrial quality.

The same protocol applies to other projects under the same conditions; let’s discuss yours.

Start a project Read the protocol

Figures on this page are defensible estimates, presented for demonstration.