Content / CMS
A governed content management system for pages, posts, reusable components, themes, menus, SEO, redirects, comments, reactions, and public publishing.
Purpose and What Problem This Solves
The Content module lets non-developers create and maintain public-facing pages while keeping layouts, components, SEO metadata, comments, and theme behavior controlled. It prevents arbitrary code edits while still giving editors a safe publishing workflow.
Who normally uses this module
What You Can Do Here
- Create public pages and blog posts with reusable approved sections.
- Manage site navigation, footer menus, redirects, metadata, and sitemaps.
- Review comments and reactions with moderation controls.
- Run page-quality diagnostics and improve public content performance.
- Assign CMS pages to system routes while preserving safe fallback behavior.
Core Concepts and Terms
Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.
Page
A public content entry built from approved components and metadata.
Post
A dated content item such as news, article, announcement, or educational update.
Component
A reusable approved section type that editors can configure without writing arbitrary HTML or JavaScript.
Theme
The visual package controlling public page layout, topbar, footer, and tokens.
Revision
A saved content snapshot that supports review and rollback.
Redirect
A rule that sends old URLs to new URLs so visitors and search engines do not hit dead links.
Beginner Quick Start
Use this first-run path in a training database or with a supervised account before handling live records.
- Confirm the module is enabled and the active theme is available.
- Create categories and tags for the content plan.
- Draft a page using approved components and add SEO title, description, and canonical URL when needed.
- Preview the page on desktop and mobile before publishing.
- After publishing, check navigation, sitemap, redirects, comments, and analytics signals.
Standard Operating Procedures
These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.
Publish a public page
- Create the page with a clear title, slug, and purpose.
- Add approved components in a logical reading order: hero, proof, details, call to action, support content.
- Fill SEO metadata and preview the page on multiple screen sizes.
- Publish, then open the public URL and check links, images, and navigation.
Update an existing article
- Read the current article and identify what changed.
- Update only the stale sections and keep the original URL if the topic is the same.
- Save a revision, preview, and include a short editorial note when policy requires it.
- Publish and monitor comments or search performance after the update.
Handle comments
- Review new comments for spam, abuse, privacy issues, and topic relevance.
- Approve useful comments, hide unsafe ones, and escalate sensitive cases.
- Reply with official guidance when the answer should be public.
- Turn recurring comment questions into page improvements.
Industry Notes and Good Practice
- Good CMS governance separates content intent from visual implementation. Editors choose approved components instead of pasting unsafe code.
- SEO basics matter: one clear topic per page, descriptive titles, useful headings, fast media, and redirects for moved pages.
- Revision history is part of content control. Use it to explain what changed and to recover from mistakes.
- Public pages should remain useful if optional modules are disabled. Check fallback routes and menus before launch.
Controls, Data Quality, and Review Checklist
Use this checklist during onboarding, monthly review, and process audits.
- Every public page has an owner, purpose, status, slug, title, meta description, and reviewed links.
- Images are compressed, relevant, and have descriptive alt text when the component supports it.
- Navigation entries point to live pages and are removed or redirected when pages retire.
- Comments and reactions are moderated on a predictable schedule.
Related ERPat areas
FAQ and Troubleshooting
Why is my page not visible publicly?Check status, publish date, route assignment, theme availability, and whether the public URL is overridden by another route.
Can I paste custom JavaScript?No. Use approved components. This keeps the public site safer and easier to support.
When should I use a redirect?Use redirects whenever a public URL changes or old content is consolidated into a new page.
What should beginners do first?Draft a simple page, preview it, check headings and links, then publish only after another person reviews it.