Meui Theme Laravel Package

Product Decisions This Supports

• Roadmap prioritization: v0.2.0 turns a visual theme into a configurable admin UX layer, so teams can defer building an in-house theme customizer and redirect engineering time to core product work.
• Build vs. buy: MIT-licensed and free to adopt; the package now covers light/dark refinement, per-user appearance preferences, panel/guard isolation, authorization closures, control allowlists, and callbacks into an existing preferences store. Buy/build reduces to integration and support risk rather than feature construction.
• Feature decisions: Product can choose between theme-only adoption and optional personal appearance controls. The customizer is disabled by default, making it a reversible feature flag rather than a day-one commitment.
• User personalization: Supports signed-in users customizing neutral palette, accent, corners, density, card treatment, navigation, workspace layout, and contrast, with immediate application and reset.
• Accessibility commitments: Mobile 44px targets, forced-colors styles, reduced-motion styles, and keyboard dialog dismissal provide concrete evidence for accessibility-related roadmap items.
• Admin/internal tooling UX: Split authentication artwork, refined tables/forms/statistics, and live customization improve perceived polish in Filament panels without bespoke design work.
• Upgrade safety: Existing theme-only installs need no migration; personal customization requires publishing migrations and registering MeUiPlugin::make()->customizer(). This supports staged rollout and avoids forcing preference storage on all users.
• Integration flexibility: Authorization closures, customizerOptions(), and persistence callbacks let product teams restrict access and connect existing preference stores instead of adopting a parallel system.

When to Consider This Package

Consider adoption when:

• The product uses Laravel 12 or 13 with Filament 5 panels.
• The team wants a refined Filament admin theme with light/dark support and optional per-user appearance controls.
• Product needs a low-cost way to improve internal tools, SaaS admin dashboards, or customer-facing panel UX without owning a full design-system build.
• Accessibility requirements include mobile target sizing, forced-colors support, reduced motion, and keyboard behavior.
• The team can accept an independent community theme and wants to evaluate support, upgrade cadence, and long-term maintenance before relying on it.
• Personalization should be scoped by panel, guard, and user, with authorization and control allowlists.
• The application already has a preferences store and wants callbacks rather than a new persistence layer.

Look elsewhere or defer when:

• The product is not on Filament 5 or supported Laravel versions.
• The organization requires an official vendor-backed theme with commercial support SLAs.
• The design needs exceed the provided customization controls and require a bespoke design system.
• The team cannot own database migrations or user-preference data, even optionally.
• The product has no signed-in panel users or no need for appearance personalization; theme-only use may still fit, but the v0.2.0 customizer value is lower.
• Engineering cannot absorb future upgrade risk from a community package across Laravel/Filament major versions.

How to Pitch It (Stakeholders)

To executives: MeUI v0.2.0 is a free, MIT-licensed Filament theme that now adds optional per-user appearance customization, accessibility-focused mobile and contrast support, and integration hooks for existing preference stores. It offers a quick UX upgrade for admin panels while keeping personalization disabled by default and requiring no migration for theme-only installs. The main trade-off is that it is an independent community package, so adoption should include a support and upgrade-risk check.

To engineering: The release is additive and non-breaking for theme-only users. Personal customization is opt-in via published migrations and MeUiPlugin::make()->customizer() in the panel provider. It supports panel/guard/user isolation, authorization closures, control allowlists, and callbacks for existing preference stores. Validation covers Pint, Larastan, Composer validation, dependency audit, SQLite/PostgreSQL tests, and a Laravel 12/13 and Filament 5 compatibility matrix. Engineering should review the customization guide, confirm migration ownership, and decide whether to use the included store or existing preferences callbacks.