PagibleAI CMS Documentation

Use these guides to install PagibleAI, configure its services, build the frontend and connect external tools. If this is your first installation, start with the setup guides. Existing sites can go directly to access control, APIs or maintenance.

• Install PagibleAI CMS in Laravel: Install the package, create an administrator and check the CMS routes.
• Configure PagibleAI CMS: Add only the AI providers, metrics services and form protection you need.
• Upgrade PagibleAI CMS: Update the package, assets and database without skipping deployment checks.

• Frontend: Render CMS pages, navigation and files in your Laravel application.
• Customize PagibleAI Theme: Override Blade templates, CSS and JavaScript while keeping the theme structure maintainable.
• Create Content Elements: Define your own content element types with fields, templates and translations.
• Add Dynamic Content: Load data from your application or external services into content elements when a page is rendered.
• robots.txt, security.txt and Sitemaps: Manage crawler rules and the security contact in the CMS and submit the XML and news sitemaps.
• Real-Time Updates with Laravel Reverb Broadcasting: Notify other editors about page, element and file changes.

• Authorization and Permissions: Define CMS roles and decide who may view, edit, publish or administer content.
• Frontend Access Control: Restrict pages on the website to logged-in visitors with matching access values.
• Multi-Tenancy SaaS Setup with stancl/tenancy: Scope users and CMS records by tenant in one shared database. PagibleAI does not support a separate database connection for each tenant.

• PagibleAI JSON REST API: Read published pages and navigation through the read-only JSON:API. The /cms/schema route returns the available content element schemas.
• PagibleAI GraphQL API: Query and manage CMS records through the authenticated administration API.
• PagibleAI MCP API Overview: Connect an MCP client to the tools for pages, content elements, files and media.
• Webhooks: Send signed, queued notifications to external services when CMS content changes. Grant the config:webhook permission to users who manage webhooks.
• CDN Cache Purging: Purge changed pages and removed files from Cloudflare, Fastly or Varnish. Purge requests run as queued jobs; use a real queue worker in production, because the sync driver purges after the response without retries.

• Customize PagibleAI: Overview of the extension points for themes, the admin panel and distributions.
• Create a Theme Package: Ship templates, assets, content elements and demo content as a Composer package.
• Build Admin Extensions: Add your own panels, fields and actions to the admin interface with plugins.
• Build Custom PagibleAI Distributions: Combine the Pagible packages required by your application.

• Pagible Search package: Index draft and published records for SQLite, MySQL, PostgreSQL or SQL Server. Rebuild the index with php artisan cms:index.
• Pagible Import package: Import WordPress posts, Gutenberg blocks and media, or TYPO3 page trees and their content with php artisan cms:t3-import. The importers create the imported published version; they do not copy WordPress or TYPO3 revision history.
• Pagible Backup package: Back up tenant CMS records and public or protected media, verify archives and restore them. php artisan cms:restore --force also restores backups from another installation after verifying all checksums. Backup archives are not encrypted, so keep them on private storage.
• Pagible Pulse package: Show GraphQL, MCP, search, contact form, page and JSON:API request metrics in the Laravel Pulse dashboard. Install it with composer require aimeos/pagible-pulse.

The Pagible Cashier package connects one supported Laravel Cashier provider and grants frontend access from subscriptions or one-time payments. Use Stripe, Paddle or Mollie, and keep payment-derived access values under provider control. The Paid Page Access guide shows the setup step by step.