Contents
ERPat CMS - a lightweight, WordPress-inspired content management layer. Server-rendered public pages and blog posts built from whitelisted, per-component-versioned reusable section packages (Tools-Hub style); a safe section/block editor (no arbitrary HTML/JS); content timeline with forward-only rollback; SEO metadata, sitemap, feeds and redirects; async.
What This Module Is For
ERPat CMS - a lightweight, WordPress-inspired content management layer. Server-rendered public pages and blog posts built from whitelisted, per-component-versioned reusable section packages (Tools-Hub style); a safe section/block editor (no arbitrary HTML/JS); content timeline with forward-only rollback; SEO metadata, sitemap, feeds and redirects; async.
Module at a Glance
Where users usually start
- Cms
- Cms Dashboard
- Cms Content Hub
- Cms Templates
- Cms Media
- Cms Taxonomy
- Cms Settings
Primary user groups
- Module administrators
- Staff users assigned to the workflow
- Managers who review records and reports
- API consumers and integration owners
- Operations staff monitoring scheduled processing
Documentation Map
Getting Started
Use this first when enabling the module, assigning access, and preparing starter data.
Daily Operations
Use this for routine work, record handling, review cycles, reporting, and handoff steps.
Administration and Controls
Use this for permissions, settings, automations, public pages, widgets, and APIs.
Data and Screen Reference
Use this to identify module screens, data records, routes, and supporting files.
Module Research Notes
Use this to see what module files were inspected and what capability evidence was found.
FAQ and Troubleshooting
Use this when the menu, data, permissions, jobs, public pages, or reports do not behave as expected.
Operator Outcomes
- Understand what the module owns and where it appears in the ERPat workspace.
- Know the first setup tasks required before staff use live data.
- Operate the main list, form, detail, report, and review screens consistently.
- Identify which permissions, settings, public pages, APIs, jobs, or widgets need administrator review.
- Recognize the core records managed by the module, including cms_contents, cms_content_meta, cms_revisions, cms_categories.