Data and Screen Reference
A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Contents module package.
Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 10 of 395 synchronized guides.
A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Contents module package.
ERPat CMS (Content) — Administrator Guide This guide explains how a content/marketing administrator uses the ERPat CMS to publish public pages and blog posts, build pages from…
ERPat CMS (Content) — Security Posture This document describes the security model of the CMS module: how output is escaped, how user-generated content is constrained, the RBAC…
Answers to the most common setup, access, workflow, and support questions for the Contents module, with troubleshooting and support guidance.
How administrators keep Contents secure and reliable: permissions, menus, settings, public pages, API surfaces, migrations, and change management.
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.
The routine operating manual for staff who run Contents day to day — the core screens, records, and workflows to use once setup is complete.
ERPat CMS (Content) — Developer Guide This guide covers the architecture and extension points of the CMS module: primary-DB pinning, the component package convention, the…
A practical first-run checklist for enabling Contents, granting the right permissions, preparing your starter data, and training the first users.
Evidence gathered from the current Contents module files — controllers, models, configs, and migrations — before writing these user guide pages.