What changed
Pollora's public 13.x framework and project skeleton offer a Laravel-first WordPress architecture, described in an October 29, 2026 Laravel News technical walkthrough. Laravel boots first and handles front-end routes, controllers, middleware, Blade templates and Vite assets; WordPress is loaded inside it and continues to provide admin, database, plugins and Gutenberg editing. PHP 8 attributes register WordPress post types, taxonomies, hooks and REST routes. The MIT-licensed project ships a Composer starter and CLI with DDEV support.
Why it matters
PHP teams can keep WordPress content editing and plugin workflows while building the front end with Laravel's routing, ORM and tooling, without a separate headless CMS API. But every request loads both systems, WordPress core updates move to Composer, and conventional theme execution is replaced. That changes hosting requirements, performance assumptions and compatibility testing.
Laravel owns requests while WordPress remains the editor
Install with composer create-project pollora/pollora or the Pollora CLI. WordPress core lives under public/cms and loads during Laravel bootstrap. Laravel handles frontend responses through Route::wp() and Route::wpMatch() using WordPress conditional tags; unmatched routes use WordPress-style template hierarchy as Blade files. WordPress admin, database and plugins remain available, but this is not a conventional theme.
PHP attributes and Blade replace much of the traditional WordPress glue
Pollora discovers PHP attributes for post types, taxonomies, actions, filters and REST endpoints. Gutenberg blocks can use JSX editor files and Blade for server output and previews. WordPress media can use Laravel filesystem disks, including S3-compatible object storage, while Colt exposes WordPress records through Eloquent models.
The maintenance and hosting boundary is substantial
The current skeleton requires PHP 8.4+, Composer 2, MySQL 5.7+ or MariaDB 10.3+, plus Node/npm for Vite. SQLite and PostgreSQL are not supported for the WordPress bootstrap. Core updates go through Composer rather than the dashboard. Both frameworks load per request; benchmark real workloads rather than assuming a speed gain. Test plugins, admin, REST, cron, caching, media and themes before migrating a mature site.
Compared with Sage, Acorn and Corcel
Acorn brings Laravel components into WordPress; Sage is a WordPress theme workflow; Corcel reads WordPress data from a Laravel app. Pollora reverses the boot order, treating Laravel as the main application and WordPress as embedded CMS. Laravel News independently documents the implementation and describes the project as young relative to established Roots tools.
Evidence limitations
The source skeleton, documentation and Laravel News walkthrough establish design and installability, not independent production performance, broad plugin compatibility or long-term maintenance reliability. The installation page contains an inconsistent older version reference alongside a current 13.39.2 claim; pin and verify exact Composer versions.