Version 0.11 brought real-time collaboration. Version 0.12 focuses on controlled delivery at scale: manage access without leaving the page workflow, update large page trees in fewer steps, and start from five distinct PagibleAI themes.
PagibleAI CMS 0.12: Private Content, CDN-Ready Delivery
PagibleAI CMS 0.12 gives you precise control over private content and prepares public pages for CDN delivery. Set pages to public, signed-in only or a named audience; move protected media to private storage; connect paid access to Stripe, Paddle or Mollie.
Editors gain batch updates, a smoother media workflow, richer content blocks and five new themes. Developers get gzipped page caching, version-safe MCP writes, Pulse monitoring and tighter security defaults.
PagibleAI 0.12 requires PHP 8.2; follow the PagibleAI upgrade guide before updating production.
For Editors: Control Access, Move Faster
What's New for Editors
Private Pages & Audiences
Set a page to public, signed-in only or a named audience. In 0.12.1, authorized editors can also grant access directly to individual users. See Frontend Page Access Control for configuration details.
Protected Media
Move files used by restricted pages to private storage. PagibleAI authorizes each request and can issue short-lived storage URLs when the configured disk supports them.
Faster Bulk Editing
Update pages, shared elements and files in batches. Apply page changes to descendants when needed, cutting repetitive work across large sites and documentation trees.
A Better Media Workflow
Drop files directly into fields, preview SVGs correctly, use clearer audio and video controls, and spot protected assets in lists and reference panels.
Five New Themes
Start with Bold, Estate, Journal, Luxury or Style. Compare the PagibleAI theme collection and choose the visual direction that fits your site.
Richer Content Blocks
Build with testimonials, page lists, multi-image heroes and configurable card columns—more expressive layouts without custom templates.
From Private Page to Paid Customer Area
Suppose you publish a paid research report. Restrict its page to customers, move the report and supporting media to private storage, then connect the same named access rule to Stripe, Paddle or Mollie. Editors stay in the normal page workflow; signed-in customers receive only the material their account unlocks.
The same model supports signed-in-only or application-defined access without payments. Private files are authorized through the pages that use them and served locally or through a short-lived storage URL. Paid Frontend Page Access explains the provider-neutral setup.
For Developers: CDN Delivery, Safer Automation
Under the hood, 0.12 makes public delivery, automation and extensions more predictable. Page caches can be served through CDNs, MCP writes detect stale versions, Laravel Pulse exposes CMS activity, and admin plugins use a supported extension point. PagibleAI now uses the MIT license, hardens file and theme path handling, and disables GraphQL schema introspection outside debug mode.
Under the Hood
CDN-Ready Page Cache
Store anonymous public responses as gzipped complete-page cache entries that CDNs can serve without unnecessary cookie barriers. Invalidation follows content changes, and 0.12.1 adds bulk clearing for selected pages.
Version-Safe MCP Writes
MCP save tools require the current latest_id. When content changed after it was read, PagibleAI detects the stale version instead of silently overwriting work. See the PagibleAI MCP Tools Reference.
Payment-Backed Access
Use paid page access with Stripe, Paddle or Mollie while provider-specific billing remains outside the core access model.
Pulse & Action Events
CMS actions emit structured events, and the optional Laravel Pulse package turns them into tenant-aware metrics for page requests and other CMS interfaces.
Extensible Admin Plugins
Register Vue admin plugins through a supported extension point without coupling them to the core. Build PagibleAI CMS Admin Extensions shows the integration path.
Safer AI & WebMCP
AI refinement validates structured output, synthesis streams through Prisma and long-running operations use configurable timeouts. WebMCP exposes browser-facing search and contact actions through application validation.
0.12 Highlights
Area
What Changed
Who Benefits
Access & media
Page rules, direct user grants and private files
Editors
Editing workflow
Bulk updates, page-tree fixes and media improvements
Editors
Themes & content
Five themes plus richer heroes, cards and page lists
Editors
Delivery
Gzipped CDN-ready cache with bulk clearing
Developers
Automation
Version-safe MCP writes and admin plugins
Developers
Payments
Stripe, Paddle and Mollie access adapters
Developers
Observability & AI
Pulse events, schema validation and streaming synthesis
Developers
Foundation
PHP 8.2, MIT license and safer defaults
Developers
Frequently Asked Questions
What can I protect in PagibleAI 0.12?
Leave a page public, require a signed-in tenant user or assign named access values. In 0.12.1, authorized editors can also grant supported values directly to individual users. Move files to private storage when they must follow the same page authorization.
How does paid content access work?
Optional Cashier packages for Stripe, Paddle and Mollie turn a purchase or subscription into named frontend access. Your page keeps a provider-neutral rule while the selected adapter handles the payment lifecycle.
Can restricted pages use the public page cache?
No. Complete-page caching applies only to anonymous public responses. Restricted pages and private files stay on their authorization path, while public pages benefit from compressed, CDN-ready cache entries.
What should I check before upgrading from 0.11?
PagibleAI 0.12 requires PHP 8.2. Back up your database and media, follow the PagibleAI upgrade guide, confirm your access and private-disk configuration, then test themes, APIs and queue workers before updating production.
Upgrade to PagibleAI 0.12
Add private content, CDN-ready delivery and safer automation to your Laravel CMS with PagibleAI 0.12.