Weave Code
Mantle Laravel Package
alleyinteractive/mantle
Mantle brings Laravel-style development to WordPress. Build themes and plugins with Eloquent models, Blade views, routing, service providers, and testing tools, plus a familiar application structure that keeps WordPress code organized and maintainable.
Mantle is a framework for building large, robust websites and applications with WordPress
Frequently asked questions about Mantle
- Is Mantle a Laravel package I can install into a Laravel app?
- No. Mantle is a WordPress application framework that brings Laravel-style architecture to WordPress; it is Composer-installable PHP but is not a Laravel package. If your project is a Laravel application, Mantle is not the right fit and the evaluation should stop there. The correct framing is whether to adopt Mantle as the application architecture for a large WordPress build.
- Which Laravel version does Mantle support?
- Mantle does not track a single Laravel release version because it is not a Laravel package. It uses selected Illuminate components and pins their versions, so you need to confirm the supported Illuminate matrix with the maintainers. Treat Laravel major bumps as a compatibility item in your upgrade planning.
- How do I install Mantle in a WordPress project?
- Install it with Composer and bootstrap Mantle alongside WordPress inside a theme, plugin, or mu-plugin. The project needs PHP 8.x, Composer-driven deploys, a Node build step for Blade and assets, and CI that can run the Mantle test suite. No data migration is required because content stays in WordPress tables.
- What are Mantle's system requirements and supported WordPress versions?
- A conventional modern stack works: WordPress 6.x, PHP 8.1+, MySQL, Composer, a Node build for assets, and optionally Redis object cache. Mantle must track WordPress majors and its pinned Illuminate components, so ask the maintainers for the exact supported version matrix and deprecation policy. Verify coverage before committing.
- Can I adopt Mantle on an existing WordPress site without a rewrite?
- Yes, the realistic path is a strangler pattern rather than a rewrite. Introduce Mantle through a new theme or an mu-plugin bootstrap, then route new features and templates through the framework while leaving legacy templates and plugins untouched until retired. Mantle wraps WordPress primitives such as posts, terms, users, and options, so existing content and hooks keep working.
- Does Mantle work with multisite, ACF, Elementor, and object caching?
- Mantle wraps WordPress primitives and leaves hooks and plugins in place, so compatibility is plausible, but you should treat page builders, multisite, and object-cache support as items to test rather than assume. Ask whether those integrations are tested by the maintainers or only community-reported. Run a proof of concept on your actual plugin stack.
- How does testing work in Mantle?
- Mantle includes a PHPUnit-based test harness and a Symfony Console CLI, so tests can run in CI without a browser. Plan for CI that executes the Mantle test suite and a build step for Blade and assets. Testing ergonomics are one of the main reasons to choose Mantle over plain WordPress.
- How does Mantle compare to Roots Sage with Acorn?
- Roots Sage with Acorn occupies adjacent territory and is the closest functional overlap, so a short bake-off is worthwhile. Also compare lighter templating options such as Timber and Twig if you only need view separation. Judge on testing ergonomics, model layer, routing, and long-term vendor risk rather than feature lists.
- Is Mantle a good fit for small WordPress sites?
- Usually no. Mantle adds application container, service provider, routing, Blade, and build overhead that exceeds the benefit for small brochure sites. It is aimed at large, long-lived, multi-team WordPress codebases such as publisher or enterprise sites, multisite portfolios, and teams with Laravel exposure.
- What are the main risks and support options for Mantle?
- Key risks include single-vendor dependency, a double upgrade treadmill against WordPress and Illuminate versions, shallow hiring depth for Mantle experience, GPL-2.0 copyleft obligations for distributed derivatives, and hard failures from container or boot exceptions. Documentation is largely first-party, so verify coverage. Ask the maintainers about commercial support, security disclosure handling, named maintainers, and bus factor before committing.
Weaver
How can I help you explore Laravel packages today?