Craftable Laravel Package

Product Decisions This Supports

• Back-office build vs. buy. Craftable is a decision input for the recurring "do we hand-roll an admin panel or start from a kit?" question. It bundles the commodity 80% of an internal admin — auth scaffolding, roles/permissions, CRUD generation, media handling, AdminLTE UI, translations — so the decision narrows to "which starter do we fork?" rather than "do we build from zero?"
• Time-to-first-admin for greenfield Laravel products. For an MVP or internal tool where the admin surface is a cost center, not the product, this shifts weeks of scaffolding into days. That directly affects launch sequencing on the roadmap.
• Feature scoping for internal tooling. Useful when scoping PRDs for ops/support/CS consoles: it sets a realistic baseline for what "table stakes" admin functionality looks like (list/filter/create/edit/delete, role gating, audit-adjacent concerns), so product specs don't over-index on custom admin UX.
• Roadmap risk register. With a last release in Oct 2023, ~987 stars, and zero dependents, it is a signal that the ecosystem has moved on (Filament, Nova, Backpack, Orchid). This informs a "modernize the admin stack" roadmap item rather than a "adopt this" item.
• Build/buy/borrow triage. The high opportunity score is best read as market signal — demand for admin scaffolding is durable, maintained supply for Laravel 8 specifically is thin. That supports a decision to borrow patterns, not the dependency, or to fund a fork if the org is Laravel-8-pinned.

When to Consider This Package

Consider it when:

• The codebase is pinned to Laravel 8 and a migration is not on the near-term roadmap.
• You need a functioning internal admin quickly for a small team, and the admin is not customer-facing or revenue-critical.
• You are comfortable vendoring or forking — MIT license, no dependents, and a stale release cadence mean you own the code, not a vendor relationship.
• You want a reference implementation of Laravel admin patterns (CRUD generation, policy/permission wiring, AdminLTE integration) to inform an in-house build.
• The team already knows Blade + AdminLTE and does not want to adopt a new reactive stack.

Look elsewhere when:

• You are on Laravel 9/10/11, or plan to upgrade — Laravel 8's security window has closed, and this package tracks it.
• The admin handles PII, payments, or regulated data — an unmaintained dependency in the auth/authorization path is a compliance and security liability, not a convenience.
• You need a maintained vendor relationship, SLAs, or a security response channel. Zero dependents means no crowd-sourced bug pressure and a thin issue-response signal.
• You want modern DX — Livewire/Inertia, Tailwind, first-class testing and generators. Filament, Nova, Backpack, or Orchid cover this with active release cadence.
• The admin is a product surface with differentiated UX. Code-generation scaffolds optimize for speed, not for a design system you'll have to fight later.
• You need API-first or headless admin — this is server-rendered Blade; retrofitting a SPA or mobile client means a rewrite.

Decision framing for the PM: treat adoption as an expedite with a known expiration date, and write the exit criteria (Laravel upgrade trigger, security review trigger) into the same doc that approves it.

How to Pitch It (Stakeholders)

For executives — one paragraph: Craftable is a free, MIT-licensed starter kit that gives us a working admin back office in days instead of weeks — login, roles and permissions, user management, media handling, and auto-generated create/read/update/delete screens. The trade-off is lifecycle: the last release was October 2023 and it targets Laravel 8, which is past its security support window, and it has no downstream dependents to pressure maintenance. So the ask is not "adopt a vendor" — it's "buy time with a fork we own," for internal, non-customer-facing tooling only. Estimated benefit is a multi-week acceleration on internal tooling; estimated cost is ongoing internal ownership of the code we fork. It is a schedule lever, not a platform bet.

For engineering — the practical case:

• Ships the commodity layer: AdminLTE shell, auth scaffolding, roles/permissions, media library, translations, and a CRUD generator that produces controllers, requests, routes, and views from a model. That's the part nobody wants to write twice.
• MIT and dependency-light — straightforward to vendor into app/ or a private fork, strip what we don't need, and pin.
• What we own if we adopt: Laravel-version upgrades, security patches in the auth/authorization path, and any UI modernization. Budget for that explicitly; it is not free.
• Recommended posture: use it as a scaffold and reference, evaluate Filament (or equivalent) for anything greenfield on Laravel 10+, and keep the admin surface behind our own abstractions so a future swap is a contained change rather than a rewrite.
• Kill criteria: any new customer-facing admin requirement, any move to Laravel 9+, or any audit finding in the auth path — at which point we migrate or rebuild.