Lumberjack Core Laravel Package

Product Decisions This Supports

• Framework lifecycle / upgrade planning: v8.4.0 adds support for Illuminate 11, meaning the package now tracks the current major of the Laravel components it borrows (container, routing, Blade, events). This is the signal a PM needs to sequence a Laravel 11 upgrade without being blocked by the WordPress theme layer.
• Build vs. buy for WordPress + Laravel hybrids: Lumberjack Core is the "buy/borrow" option when you want Blade templating, an IoC container, routing, and MVC structure inside a WordPress theme instead of building that glue yourself. This release confirms the maintainers are still actively maintaining that bridge rather than letting it drift behind upstream.
• Roadmap feasibility: If your roadmap includes modernising a legacy WordPress theme to a component-based architecture, Illuminate 11 compatibility is a prerequisite you can now tick off — reducing the perceived risk of the migration in planning estimates.
• Support & security posture: Staying current with Illuminate majors means continued access to upstream security fixes and PHP version support. Pin a decision point: the moment the package falls a major behind Laravel, that's your trigger to reassess or plan an exit.
• Use cases it unlocks: marketing sites and content platforms where editorial teams stay on WordPress but the delivery layer is engineered like a Laravel app (Blade views, controllers, service container, structured routing).

When to Consider This Package

• Consider it when: you are running (or about to run) WordPress as a headless-ish or themed CMS and your team's core competency is Laravel, not WordPress theme development. The value is highest when you want Blade over PHP templates, dependency injection over globals, and testable controllers over template files with logic.
• Consider it when: you are on Laravel 11 / Illuminate 11 and want the surrounding ecosystem aligned. Prior to v8.4.0 this was a genuine blocker; that objection is now removed.
• Look elsewhere when: the team is WordPress-native and has no Laravel background — the abstraction adds cognitive overhead with little payoff. Also look elsewhere if you need a fully headless/API-first content platform (evaluate WordPress as a content API plus a standalone Laravel app, rather than embedding Laravel into the theme), or if you want a supported commercial product rather than a community-maintained package.
• Watch for: a single-maintainer/small-team bus factor; the release being a compatibility bump rather than a feature release means you should validate against your own theme before committing, and confirm the rest of the Lumberjack suite (and any plugins) is version-matched. Treat minor versions as requiring a regression pass, not a blind composer update.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost maintenance release, but an important one — it keeps our WordPress theme framework current with Laravel 11. That means we can adopt the current Laravel major (and its security and PHP support) without the WordPress layer holding us back. No breaking changes, no migration work required from us beyond a normal dependency bump and regression check. It preserves our option to modernise the CMS layer on our own timeline rather than being forced into a rewrite.

For engineering: lumberjack-core v8.4.0 adds Illuminate 11 support (PR #75) — a compatibility release with no API changes or deprecations. It unblocks the Laravel 11 upgrade path for any theme built on Lumberjack, since the package's Illuminate constraints previously capped us below 11. Recommended action: bump the constraint, run the theme test suite and a manual pass over routing, Blade views, and container bindings, and verify any companion Lumberjack packages are on compatible versions. Risk is low; the main residual concern is upstream maintenance cadence, so we should track releases and treat falling a full Illuminate major behind as an escalation trigger.