Skip to main content

CMS Module Analysis: Content Management

[!IMPORTANT] DECOMMISSIONING STATUS: The WepNG internal CMS is being replaced by DatoCMS. This module currently serves legacy content or specific internal pages not yet migrated.

1. Overview​

CMS (Content Management System) formerly handled dynamic content. It is now in a sunset phase.

Key Metrics​

  • Scope: PageNG, BlocksNG.
  • Status: Legacy / Read-Only.
  • New Master: DatoCMS + Vercel.

2. Architectural Archeology​

2.1 The "Block System" Pattern (Legacy)​

The CMS uses a Block System (BlocksNGBiz) where content snippets are stored in the DB.

  • Risk: Security risks defined previously.
  • Maintenance: Content updates should now happen in DatoCMS, not here.

2.2 The "PageNG" Router (Legacy)​

PageNGBiz handled dynamic routing.

  • Current State: The Vercel Frontend now handles routing. PageNG might only be serving redirect rules or fallback pages.

3. Evolution Strategy​

Step 1: Headless CMS Migration (Long Term)​

The ultimate goal should be Contentful or Strapi.

  • Why: Managing CMS in custom .NET code is non-core business.
  • How: Start syncing PageNG content to a Headless CMS and have the Frontend query the Headless API.

Step 2: Decouple Routing​

Move routing logic out of the DB (PageNG) and into the Frontend Application (React/Next.js Router).