Project case study

A clearer way to solve a complex challenge

A multi-tenant content platform I designed, built and run in production, including the website you are reading now.

role
Sole engineer, from design to production
type
Multi-tenant CMS and site builder
CORE STACK
.NET 10, Angular, PostgreSQL
STATUS
Live in production
The AfdCMS page editor
the AfdCMS page editor
The AfdCMS page editor

THE CHALLENGE

Most CMS platforms get harder to run as they grow

Updates become manual, deployments become risky, and critical features end up depending on third-party plugins that bring their own technical debt.

14

feature modules, from pages and media to store and campaigns

1,400+

automated tests run on every build

4

environments every release moves through

13

13 module data models, each checked for missing migrations before every release

WHAT I BUILT

One platform, everything a real site needs

Multi-tenant by design

Each site is resolved from its domain and isolated at the database level, so one platform safely runs many sites.

Visual page builder

Over thirty section types, live preview, undo and redo, saved sections and drafts, all without touching code.

Media on Cloudflare R2

Uploads live outside the application, with a local fallback and background sync, so deployments never touch content.

Secure sign-in everywhere

Google sign-in and role-based permissions that behave the same in every environment, not just on a laptop.

Commerce and campaigns

A store with Stripe and PayPal checkout, plus a campaign studio for planning and publishing social posts.

Built-in operations

Health checks, media sync monitoring and a release footer that shows exactly which version is running.

  1. Build

    Compile, run every test and migrate fresh databases, then package the result once.

  2. Test

    Deployed to a test server and checked end-to-end in a real browser.

  3. Staging

    Rehearsed on a copy of production infrastructure before anyone sees it.

  4. Production

    Released on approval, with health checks and a rollback path.

HARD PROBLEMS SOLVED

The parts that usually go wrong

Sign-in across environments

Google’s callback rules differ per domain. The whole sign-in flow was built and checked for each environment, so access works everywhere.

heading Media that survives deploys

Moving uploads to Cloudflare R2, with a verified local fallback, separated content from code, so releases can never lose an image.

Releases you can trust

Build-once packages, automatic version tags and a guard that refuses to label an untested commit as released.

The result
TECHNOLOGY
  • Angular
  • ASP.NET Core
  • C#
  • CI/CD
  • Cloudflare R2
  • Entity Framework Core
  • Google Authentication
  • .NET
  • PostgreSQL
  • React
  • Release Management
  • SQL Server
  • TypeScript