Website pages

Every page of the public website in one register: what it is, which course or service it shows, where it sits in the menu, who owns it, and whether the version visitors see is the latest one.

Review & publishingLanding pagesOpen the ML510 course page

Coverage check: what content administration already existed

Verified against the prototype files on 3 Oct 2026

Already demonstrated

  • Course editor: the public course description, and a “SEO & publishing” tab with URL slug, status, search title and description, pre-publish checks and version history. Its Publish button shows a message only.
  • Knowledge hub content: articles and Playbook episodes from idea to review to published, with author, technical reviewer, publish date and an AI brief.
  • Website booking widgets: catalogue, dates, “Book now” and checkout blocks with their placements on public pages, and the WordPress plugin or new-site install options.
  • Registration forms: form builder with a live preview and publish per batch.
  • AI content drafting: catalog description, excerpt and search title drafted for review and approval.
  • Public website: page files in public/, with the header menu built from one array in shell.js.

Was missing

  • No register of website pages. Standard pages such as About, Contact and Accreditation had no editor at all.
  • No landing pages tied to campaigns.
  • No screen to change the header or footer menu.
  • Search metadata only per course; no site-wide view, no issue list.
  • No preview of a draft against the public page, no shared review queue, no revision history or approver across pages and menus.
  • The WordPress question was stated only for booking widgets, not for page authoring and ownership.

Added in this revision

  • This register, with state, version, reviewer, publish date and a catalog-consistency flag.
  • Page editor and preview with review, simulated publish and revision history.
  • Landing pages, Menus, SEO metadata and Review & publishing.
  • Both answers to the WordPress decision on every screen, without choosing one.
  • Course content itself stays in the Course editor. The page editor reads price, hours, level and dates from the catalog and cannot change them.
Demonstrated in the prototype with sample records. No page, menu or metadata is published anywhere: every publish action is simulated.
Course pages are generated from the catalog, one per published course. Landing page rows are also on Landing pages.