PagibleAI CMS Documentation

Install PagibleAI in a Laravel application

PagibleAI installs into an existing Laravel 11, 12, or 13 application. The installer adds the CMS packages and configuration; migrations create the page, element, file, version, and search tables.

Start with a clean branch and a database backup when adding the CMS to an established application. The package uses your Laravel database, filesystem, queue, cache, authentication, and deployment process.

composer require aimeos/pagible
php artisan cms:install
php artisan migrate
php artisan cms:user -e editor@example.com

Package responsibilities

Package
Responsibility
Use it when
Core
Models, versions, permissions, tenancy
Every installation
Admin
Vue editing interface
People edit content in a browser
Theme
Blade rendering and page cache
Laravel serves the website
GraphQL
Administrative API
An application manages CMS records
JSON:API
Published content delivery
A frontend reads content remotely
AI
Writing, translation, media operations
Editors need configured assistance
Search
Database-native full-text index
Readers search the website
MCP
Permission-checked content tools
Agents assist with CMS work

Working examples

Editorial workspace prepared for structured content planning

Build a content element

Define one reusable content shape, render it with Blade, and make it available to editors.

Open the content element example

Team discussing an editorial workflow around a shared table

Configure editorial AI

Assign a provider and model to each editorial task without coupling the CMS to one service.

Open the AI configuration example

Publish with explicit roles

Documents and notes prepared for an editorial publishing review

PagibleAI separates viewing, editing, publishing, and administration permissions. Named role definitions expand into permission sets, so a small site can use simple roles while a larger installation can assign narrower capabilities.

Every save creates a version. Publishing selects the snapshot that public routes and delivery APIs may read. Schedule the cms:publish command when your team uses timed releases.