Press kit
Pollora press kit: key facts, descriptions in English and French, logos, mascots, screenshots, code samples and the one-minute video.
Everything you need to write about Pollora: key facts, ready-to-use descriptions, brand assets, screenshots and code samples. Use them freely in articles about the project. Download every image (ZIP, 3.3 MB).
Key facts
| Name | Pollora, the Laravel framework for WordPress |
|---|---|
| What it is | An open-source PHP framework: WordPress runs inside a Laravel application |
| Current release | v13.35.5, 9 October 2026, on Laravel 13.35 |
| First stable release | v13.34.0, 30 September 2026 (the version number follows Laravel: 13.34 = Laravel 13.34) |
| License | MIT (framework, skeleton, CLI, Nectar and the other packages) |
| Publisher | AmphiBee, a French web agency |
| Requirements | PHP 8.4+, WordPress 7.1+, MySQL 5.7+ or MariaDB 10.3+ |
| Links | GitHub · v13.35.2 release notes · Installation · How Pollora compares |
Descriptions
Copy whichever length fits. Each description uses only the facts above.
English
Short · 51 words
Pollora is an open-source framework that runs WordPress inside a Laravel application. Laravel routing, controllers and Blade render the front end, while the WordPress admin and plugins keep working. Hooks, post types and REST routes are declared with PHP 8 attributes. The first stable release, v13.34.0, shipped on 30 September 2026.
Medium · 141 words
Pollora is an open-source PHP framework that runs WordPress inside a Laravel application. It takes the inverse route of Acorn, where Laravel runs inside WordPress: in Pollora, Laravel boots first and loads WordPress as part of its own boot. The front end is rendered with Laravel routing, controllers and Blade; the WordPress admin, database, plugins and REST API keep working. Hooks, post types, taxonomies and REST routes are declared with PHP 8 attributes and registered by auto-discovery, and Route::wp() matches Laravel routes on WordPress conditional tags. Nectar gives AI coding agents accurate context about a Pollora project. The first stable release, v13.34.0, shipped on 30 September 2026; its version number follows Laravel's. Pollora builds on the work of Roots (@roots/vite-plugin, the Bedrock layout, Sage Directives) and its models fork Corcel. It is MIT-licensed and published by AmphiBee, a French web agency.
Long · 281 words
Pollora is an open-source PHP framework that runs WordPress inside a Laravel application. Many Laravel developers also have to ship WordPress sites, and there they find functions.php, scattered hooks and global functions again. Pollora lets them keep the Laravel way of working without giving up what WordPress does well.
The arrangement is the inverse of Acorn, where Laravel runs inside WordPress. In Pollora, Laravel's front controller receives the request and WordPress core loads inside a service provider. The front end is rendered with Laravel routing, controllers and Blade, and the WordPress admin, database, plugins and REST API keep working. Route::wp() lets a Laravel route match a WordPress conditional tag such as is_single or is_page, with the WordPress template hierarchy as a fallback.
Registration code becomes PHP 8 attributes. A class carrying #[PostType] becomes a post type, a method carrying #[Action('init')] becomes an action, and REST routes are declared the same way. Pollora discovers them automatically, so there is nothing to register by hand.
Nectar, an optional development package, gives AI coding agents accurate context about a Pollora project.
Pollora owes a lot to Roots: it uses @roots/vite-plugin, a Bedrock-style layout and Sage Directives, and its WordPress models are built on a fork of Corcel. The comparison page on pollora.dev explains where each of these projects fits.
The first stable release, v13.34.0, shipped on 30 September 2026. Version numbers follow the Laravel release Pollora is built on, so 13.34 means Laravel 13.34. A new project needs PHP 8.4+, WordPress 7.1+, and MySQL 5.7+ or MariaDB 10.3+. The framework, the project skeleton, the CLI and Nectar are MIT-licensed. Pollora is published by AmphiBee, a French web agency, and its source is on GitHub.
Français
Courte · 52 mots
Pollora est un framework open source qui fait tourner WordPress dans une application Laravel. Routes, contrôleurs et Blade de Laravel rendent le front ; l'administration et les extensions WordPress fonctionnent toujours. Hooks, types de contenu et routes REST se déclarent en attributs PHP 8. Première version stable, v13.34.0, le 30 septembre 2026.
Moyenne · 163 mots
Pollora est un framework PHP open source qui fait tourner WordPress à l'intérieur d'une application Laravel. Il prend le chemin inverse d'Acorn, où Laravel tourne dans WordPress : avec Pollora, Laravel démarre en premier et charge WordPress pendant son propre démarrage. Le front est rendu par le routage, les contrôleurs et Blade de Laravel ; l'administration, la base de données, les extensions et l'API REST de WordPress continuent de fonctionner. Hooks, types de contenu, taxonomies et routes REST se déclarent en attributs PHP 8 et sont enregistrés par découverte automatique, et Route::wp() associe une route Laravel aux balises conditionnelles de WordPress. Nectar donne aux agents IA de code un contexte juste sur un projet Pollora. La première version stable, v13.34.0, est sortie le 30 septembre 2026 ; son numéro suit celui de Laravel. Pollora s'appuie sur le travail de Roots (@roots/vite-plugin, la structure Bedrock, Sage Directives) et ses modèles forkent Corcel. Il est sous licence MIT et édité par AmphiBee, agence web française.
Longue · 315 mots
Pollora est un framework PHP open source qui fait tourner WordPress à l'intérieur d'une application Laravel. Beaucoup de développeurs Laravel doivent aussi livrer des sites WordPress, et y retrouvent functions.php, des hooks éparpillés et des fonctions globales. Pollora leur permet de garder leurs habitudes Laravel sans renoncer à ce que WordPress fait bien.
L'organisation est l'inverse de celle d'Acorn, où Laravel tourne dans WordPress. Avec Pollora, le contrôleur frontal de Laravel reçoit la requête et le cœur de WordPress se charge dans un fournisseur de services. Le front est rendu par le routage, les contrôleurs et Blade de Laravel, et l'administration, la base de données, les extensions et l'API REST de WordPress continuent de fonctionner. Route::wp() permet à une route Laravel de répondre à une balise conditionnelle de WordPress comme is_single ou is_page, avec la hiérarchie des modèles de WordPress en repli.
Le code d'enregistrement devient des attributs PHP 8. Une classe portant #[PostType] devient un type de contenu, une méthode portant #[Action('init')] devient une action, et les routes REST se déclarent de la même façon. Pollora les découvre automatiquement : rien à enregistrer à la main.
Nectar, un paquet de développement optionnel, donne aux agents IA de code un contexte juste sur un projet Pollora.
Pollora doit beaucoup à Roots : il utilise @roots/vite-plugin, une structure inspirée de Bedrock et Sage Directives, et ses modèles WordPress reposent sur un fork de Corcel. La page de comparaison de pollora.dev explique la place de chacun de ces projets.
La première version stable, v13.34.0, est sortie le 30 septembre 2026. Les numéros de version suivent ceux de Laravel : 13.34 correspond à Laravel 13.34. Un nouveau projet demande PHP 8.4+, WordPress 7.1+, et MySQL 5.7+ ou MariaDB 10.3+. Le framework, le squelette de projet, la CLI et Nectar sont sous licence MIT. Pollora est édité par AmphiBee, agence web française, et son code source est sur GitHub.
Logo and share image
Mascots
Screenshots
Code samples
Three short samples taken from the published guides, ready to copy.
A post type, declared with attributes
The class is found by auto-discovery and registered as the book post type, with an archive at /books/. No register_post_type() call. Read the guide.
<?php
namespace App\Cms\PostTypes;
use Pollora\Attributes\PostType;use Pollora\Attributes\PostType\HasArchive;use Pollora\Attributes\PostType\Rewrite;use Pollora\Attributes\PostType\ShowInRest;use Pollora\Attributes\PostType\Supports;
#[PostType('book', textDomain: 'my-theme')]#[HasArchive('books')]#[Rewrite(['slug' => 'books', 'with_front' => false])]#[Supports(['title', 'editor', 'excerpt', 'thumbnail', 'revisions'])]#[ShowInRest]class Book{}WordPress hooks as methods
Each method carrying #[Action] or #[Filter] is registered with WordPress on an instance resolved from the container. The accepted argument count comes from the method signature. Read the guide.
<?php
namespace App\Cms\Hooks;
use Pollora\Attributes\Action;use Pollora\Attributes\Filter;
class Seo{ #[Action('wp_head', priority: 1)] public function metaDescription(): void { if (is_singular()) { echo '<meta name="description" content="'.esc_attr(get_the_excerpt()).'">'; } }
#[Filter('body_class')] public function bodyClass(array $classes, array $cssClass): array { $classes[] = 'has-js';
return $classes; }}Laravel routes on WordPress conditional tags
Route::wp() matches a WordPress conditional tag instead of a URI: the first route runs when is_single() is true, the second for is_page('contact'). Anything unmatched falls back to the WordPress template hierarchy, rendered with Blade. Read the guide.
Route::wp('single', [BlogController::class, 'show']);Route::wp('page', 'contact', [ContactController::class, 'show']);One-minute video
A one-minute tour of Pollora: watch on YouTube. To embed it:
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/Wk1VzPapqM8" title="Pollora in one minute" frameborder="0" allow="encrypted-media; picture-in-picture" allowfullscreen></iframe>Contact
Olivier Gorzalka, AmphiBee. For questions about the project, use the GitHub discussions. For how Pollora relates to Roots (Acorn, Sage, Radicle) and Corcel, whose work it builds on, see How Pollora compares.