We previously introduced a WordPress MVC framework called Themosis Framework. It is built on top of several Laravel components, which can feel heavy if you only need a limited number of MVC-style features in a site. This time the focus is another WordPress MVC framework: WP Emerge.
Like Themosis, WP Emerge is inspired by Laravel. The difference is that WP Emerge does not rely on Laravel components directly, which makes it a much lighter MVC option for WordPress projects.
WP Emerge features
- A full routing system, including controllers, middleware, PSR-7 responses, and view composers.
- Freedom to use any template engine, including native PHP, Laravel Blade, Twig, or something else entirely.
- A service container, with dependencies instantiated through an IoC container that can be swapped for your own compatible implementation.
- Extensibility through service providers, template engines, dynamic route conditions, and error handling customization.
- Advanced error reporting with interactive stack traces, data dumps, and highlighted source files.
- Full support for the WordPress Loop without replacing or breaking it.
- Route middleware support, either globally or on specific routes and route groups, including features such as flash messages and old input handling.
WP Emerge resources
The official project already provides several resources that can help you get started quickly:
- Documentation: https://docs.wpemerge.com/#/framework/overview. This is the best starting point if you want to integrate WP Emerge into an existing theme.
- Starter theme code: https://github.com/htmlburger/wpemerge-theme. Clone it into WordPress if you want to try the framework in practice.
- Starter theme guide: https://docs.wpemerge.com/#/starter-theme/overview. This explains how to modify the starter theme and build on top of it.
- API reference: https://api.wpemerge.com/master/. This is useful when you run into implementation questions.
Common questions about WP Emerge
No, WP Emerge is primarily intended as a framework you can include in a theme. There is no official plugin-centric workflow, although in practice it should not be difficult to include it inside a plugin if needed.
No, even though it is heavily inspired by Laravel, WP Emerge is intentionally lean and adapted for WordPress. It does not ship with illuminate/* packages.
Yes, one of WP Emerge’s strengths is that its adoption can be gradual. You can introduce it into an older project without rewriting all of the site’s logic and templates at once. For example, you might render new templates with Blade while still rendering the older parts of the site with plain PHP.
Yes, WP Emerge is open source and free to use under GPL 2.0. You can submit issues, suggestions, and pull requests on GitHub.
WP Emerge can be used in any theme, but the official starter theme is the best reference point when integrating it cleanly.
If you need help, the official documentation, the Gitter lobby, and the GitHub issue tracker are the main places to look.
After testing it, we found that WP Emerge is fully capable of supporting a proper MVC workflow in WordPress while staying lightweight. If you are building WordPress applications and want more structure, it is well worth a try.
