Skip to main content

CMS pages

CMS is a level-0, write-capable static-page surface. The primary Settings entry is /all-settings?category=pages; source also retains the direct /settings/pages route. Mounting the manager reads page records, so neither path is a safe documentation probe.

Static Pages Manager header, search, and column headings without page records

Pages list​

Current client source defines:

  • a Static page name column;
  • Search and pagination controls;
  • Add page / Add new static page;
  • a per-page Enable control; and
  • Edit and Delete actions in the row menu.

The list-level Enable switch is wired to an immediate page update. API source applies role/public visibility filters to reads. These source contracts do not prove deployed publication, indexing, URL availability, or successful visibility changes, and no page record was read.

Create or edit a page​

The source-defined Add/Edit form can contain:

  • Name;
  • Slug;
  • SEO Title (up to 255 characters);
  • SEO Description (up to 1,000 characters);
  • SEO Image on existing pages; and
  • the page body editor, with formatting, tables, link, image, video, and code-view tools.

Client source strips spaces from the slug. Current API source requires a nonempty name, slug, and body on creation; restricts type to 1, 2, or 3; limits SEO title to 255 characters and SEO description to 1,000; and accepts an SEO image only as JPG or PNG, at most 1,024 KB, with width and height each from 1,200 through 1,500 pixels. These are fixed-source rules, not a runtime test, universal deployed guarantee, or invitation to enter content or media.

For creation, client source can submit an enabled page and substitutes a blank paragraph when its editor body is empty. Server validation remains authoritative in source; neither behavior was executed.

Save, publish, and delete semantics​

For an existing page, Accept maps to a page update; Cancel closes the current form without that form submission. No save response, rollback, final content, or public effect is claimed.

Current client source has no separate Publish control. Enablement is included in update paths, and Delete maps directly to deletion without a source-visible confirmation or restore flow. Runtime, recovery, and public URL behavior remain unverified.

Content and search impact

Page content, slugs, SEO metadata, media, enabled state, and deletion are public-content/search/customer effect classes. Every page/media mutation and downstream consumer remains blocked.

Images and embedded content​

The editor source can insert links, images, and videos. Its image picker reads project files and exposes separate file upload/delete actions. No file list, name, thumbnail, URL, upload, deletion, embedded content, or external destination was accessed.

Safe evidence​

The approved capture is limited to the manager heading, search, and column headings; it excludes page records and content. Any future capture must avoid page names, body text, SEO metadata, image thumbnails, URLs, file names, and user/customer information. Do not open an existing page or use any Add, Edit, Enable, Accept, Delete, upload, or media-insert action for a capture.

The retained /settings/pages path is a terminal audit-only duplicate-route exclusion, not a second CMS article or an entitlement shortcut. This page remains the sole documentation owner. Re-entry requires route/ownership drift or an approved synthetic page/media fixture isolating create, update, upload, enable, and delete effects.

Related guides: Settings overview · Settings logs