- What Laravel, PHP, and Filament versions does miran/mksine support?
- MKSine is advertised as a Laravel + Filament 4/5 CMS foundation, and the technical evaluation lists a practical stack of PHP 8.2+, Filament 4 or 5, Livewire 3, and MySQL or PostgreSQL. Because Filament major-version coupling is material, verify the exact Laravel, Filament, Livewire, PHP, and database matrix before committing. The package is a poor fit if your application is pinned to Filament 3 or runs Nova, Backpack, or a custom admin stack.
- How do I install MKSine in a Laravel application?
- Run composer require miran/mksine, then php artisan filament:install --panels if you do not already have Filament panels. Register MksinePlugin in your AdminPanelProvider, remove the default Dashboard page, and remove the Route::get('/', ...) entry from routes/web.php because MKSine owns the homepage. Finish with php artisan mksine:install --migrate and php artisan mksine:create-super-admin. After that, validate panel routing, publish config and migrations as needed, and configure media storage.
- Is MKSine a starter kit or a regular Composer package?
- MKSine is a Composer package (miran/mksine), not a starter kit fork. The technical evaluation considers the Composer-package approach architecturally preferable because MKSine sits above Filament as a CMS layer without forking Laravel. That also means it is not a small utility: plugin lifecycle, theme installation, and hooks become platform contracts.
- Can MKSine run alongside my existing Filament admin panel?
- Yes, coexistence is feasible in a Filament-native codebase, and brownfield adoption should be additive. Pilot MKSine in a separate Filament panel or route group before replacing any existing admin workflow. The hard part is mapping existing content models, auth and roles, media, routes, and permissions into MKSine without creating parallel admin surfaces.
- How are MKSine plugins installed, and is that safe in production?
- MKSine provides installable plugins with lifecycle management, but the evaluation flags plugin and theme installation as a high-risk capability if exposed through the admin UI, because it is effectively arbitrary code execution. Determine whether plugins are Composer-only, upload-based, or both, and whether installation can be disabled in production. Plugin signing, allowlisting, and sandboxing are not established in the provided context, so govern this capability before exposing it.
- Can I add custom page builder blocks in MKSine, and is the content exportable?
- MKSine's opt-in visual page builder composes typed blocks such as hero, columns, and CTA via drag-and-drop, and the tree is stored as JSON and rendered by the active theme. Whether blocks can be custom-coded and whether the JSON schema is stable and exportable are key questions to validate. Package-specific JSON or schema creates portability and exit risk, so do not migrate existing content until export behavior is proven.
- Can the MKSine Super Admin console be restricted or disabled?
- MKSine includes a Super Admin console, created with php artisan mksine:create-super-admin, and the evaluation recommends hardening it. It should not be internet-exposed without controls. Confirm in your spike whether the console can be restricted by role, IP, or environment, or disabled entirely in production.
- How does MKSine integrate with Spatie Permission or Filament Shield?
- Integration with existing users, roles, and permissions is a key adoption question, especially for teams using Spatie Permission or Filament Shield. The provided material does not document a specific adapter, so validate how MKSine's Super Admin and panel authorization map onto your existing role model. Keep your existing auth and roles where possible rather than running two permission systems.
- Does MKSine support multi-site, multi-tenancy, and localization?
- MKSine is positioned for agency and multi-site CMS work, internal content platforms, and Filament-native products, and it lists translations among its features. The provided context does not establish multi-tenancy or multi-site depth, so confirm the required depth in a time-boxed spike. Localization support exists but should be tested against your content types, menus, and page builder blocks.
- What are the production risks and maintenance outlook for miran/mksine?
- The primary risk is maturity: the evaluation cites roughly 106 stars, zero dependents, and likely single-maintainer stewardship, with an MIT license but no support guarantee. Filament major-version coupling, hidden coupling through hooks, and package-specific page builder schema all affect upgrade fragility and exit options. Ask for test coverage, CI status, a security disclosure policy, release cadence, and an upgrade guide before committing. Treat adoption as a platform decision and time-box a spike rather than estimating from the README.