Modules
Every module plugs into the DMS you already run: its pages join the sidebar, its permissions join the role editor and its data stays in your project's database. Install a module with the AntelopeJS CLI, then follow its guide.
ajs project modules add @antelopejs/dms-<module>
- AI assistant
Create and refine pages, layouts and configurations with an assistant that understands the DMS.
AntelopeJS/dms-ai - Builder
Edit a DMS project's pages and blocks programmatically, with every change checked to compile.
AntelopeJS/dms-builder - Database
Explore rows, inspect schemas and run queries without leaving your workspace.
AntelopeJS/dms-database - API
Bring endpoint configuration, implementation, documentation and request statistics into one view.
AntelopeJS/dms-api - Automation
Wire triggers, conditions and actions in a visual flow editor that other modules extend.
AntelopeJS/dms-automation - SaaS
Manage tenants, plans, subscriptions and invoicing alongside the product you deliver.
AntelopeJS/dms-saas - Translation
Manage locales and translation keys for your dashboard and the applications it serves.
AntelopeJS/dms-lang - Mailing
Design email templates with a block editor, then follow every send and its delivery.
AntelopeJS/dms-mailing - Marketing
First-party traffic dashboards, conversion funnels, A/B splits and click heatmaps.
AntelopeJS/dms-marketing - Media
Organize uploads, folders and image derivatives in the same permission model as your dashboard.
AntelopeJS/dms-media
How module guides are organized
Each guide follows the same path, so you know where to look whatever the module:
- Introduction: what the module adds and what it looks like.
- Installation and Configuration: the package to add and the options it reads.
- Usage: one page per screen or feature, with screenshots.
- Extending: the interfaces and APIs other modules call, when the module has any.
Interface references
A separately published interface owns its reference beside its source, in
packages/interface-dms-*/docs/. These references describe the contract consumed
by other modules; the guides above describe the runtime that implements it.
API, Database, Translation and AI document their supported integration points in their Extending guides; they do not publish a separate interface package.