aimeos/pagible

Pagible feels like a serious attempt to bring a modern CMS into the Laravel world without forcing teams to leave their existing app. The strongest part is the scope: structured content, a Vue/Vuetify admin, JSON:API for frontend delivery, GraphQL for administration, AI-assisted writing and media workflows, themes, search, imports, backups, multi-domain support, multi-tenancy, and even MCP tooling. That is a lot to take on, but the repository is organized in a way that makes the ambition understandable instead of chaotic.

The README is also much better than a typical early-stage package README. It explains what Pagible is, how the packages are split up, how to install it, how to create CMS users, what scheduled jobs are needed, and how to configure AI providers. For a Laravel developer evaluating whether this can fit into an existing project, those details are useful. The project also has good signs of momentum: hundreds of GitHub stars, regular releases, Packagist availability, tests, PHPStan/Larastan, Testbench, CircleCI, and a large commit history.

The biggest thing I would clean up is trust signals. The repo says LGPL-3.0 in some places, but composer.json and Packagist show MIT, and that kind of license mismatch can make companies hesitate. I would also add clearer CI badges and a short compatibility matrix for PHP, Laravel versions, databases, and frontend builds. The feature set is impressive, but claims like multi-database search, millions of pages, and AI image workflows would land better with screenshots, demo links, benchmark notes, or example projects.

Overall, Pagible looks ambitious, useful, and thoughtfully structured. It already has enough substance to be worth watching or trying in a Laravel project, and with a little more polish around licensing, demos, and verification, it could feel much easier to trust for production use.