BETC Fullsix
MUH logo
BETC Fullsix

MUH

The headless hub that normalises your CMS content into clean APIs any front end can consume.

WP + NestJSnative headless
1 / None middleware, N front ends
@muh/*versioned packages

MUH (Unified Headless Middleware) permanently decouples the front end from the CMS: an editorial back office (WordPress Bedrock or Directus, your choice), a NestJS middleware at the centre, one or more Next.js front ends as consumers. Each layer evolves independently - swapping the CMS does not require rewriting the front end, adding a new front end does not touch the CMS, and vice versa.

This is not a theoretical architectural bet: it is the foundation running betc.com and a dozen other client projects, from simple showcase sites to platforms with authenticated member areas, encrypted forms and multilingual search.

Vos équipeséditorialesun seul back-officeon écritune foisMUHle hub de contenusmet tout au même formatSite weble site publicApplicationmobile ou webOutil internemétier, back-officeCHAQUE EXTRÉMITÉ SE REMPLACE SANS TOUCHER À L’AUTRErefondre le site n’oblige pas à remigrer les contenus, et changer d’outil éditorial ne réécrit pas le site

Decoupling

The front end never talks to the CMS directly. MUH exposes stable, normalised REST/GraphQL APIs regardless of the WordPress/Directus version or the plugin and extension configuration. The CMS becomes a replaceable implementation detail.

Built-in quality

SEO and GEO (generative-AI optimisation), RGAA accessibility, Cloudflare edge cache with targeted URL invalidation on every publish, OAuth2/Keycloak auth for authenticated areas - quality is wired into the foundation, not bolted on project by project.

Reversibility

The @muh/* packages (adapters, forms, fixtures, CLI, DTOs) are semantically versioned and published to the private GitLab registry. Replacing WordPress with Directus (or the reverse) tomorrow will not break a single line of front-end code: only the adapter changes.