- Is gabriel2m/filament-starter-kit a Composer package I can install into an existing Laravel app?
- No. It is a Laravel application scaffold built on Filament, not a drop-in library, so you do not composer require it into an existing production app. Its value is accelerating greenfield admin and back-office builds. For an existing application, treat it as a reference implementation and extract the patterns you need.
- How do I install the Filament starter kit and start a new Laravel admin panel?
- Generate a new application from the repository template or fork it, install the Composer dependencies, and run the normal Laravel setup steps such as environment configuration, application key generation, and migrations or seeders. Then review the Filament panel provider, auth scaffolding, and user/resource conventions. Plan to remove demo resources and branding before feature work.
- What Laravel and Filament versions does this starter kit support?
- The kit is tied to specific Laravel and Filament major versions, and starter kits tend to track those majors closely. The provided context does not state an explicit version-support policy, so confirm the pinned constraints in composer.json and composer.lock. Record those versions in an ADR and test upgrades on a branch.
- Can I merge filament-starter-kit into my existing Laravel application?
- An in-place merge into a live codebase is not recommended. The realistic path is to generate a disposable reference instance, inventory what you would inherit, and then fork into a new repository you own. If you already have an app with its own design system or auth model, implement only the Filament configuration idioms natively.
- What are the main technical risks of using a single-maintainer Filament starter kit?
- The dominant risks are version coupling, release opacity, and fork drift. Filament majors have historically carried breaking changes to resources, forms, tables, and panel configuration, and v1.4.0 ships with only a compare link and no narrative changelog. Single-maintainer starter kits also have a finite shelf life, so your fork becomes the product.
- Does this starter kit include multi-tenancy, SSO, or granular authorization?
- The provided context does not state that multi-tenancy, SSO, or granular authorization are in scope upstream. You should assume you own those extensions unless you confirm the project roadmap. Port your RBAC policy, SSO, and audit trail as the first commits on your fork.
- How should I handle upgrades and changelogs for a forked Filament starter kit?
- Treat upstream as a read-only reference and schedule periodic diff reviews. Because releases such as v1.4.0 may ship with only a compare link, upgrade on a throwaway branch and run the full test suite plus manual checks. Adopt upstream changes as diffs you choose, not automatic merges.
- Is filament-starter-kit suitable for production use in a back-office or internal tool?
- Yes for greenfield internal tools, customer portal back offices, and CRUD-heavy operational surfaces, provided you reconcile it with your own conventions. You still need to add roles and permissions, audit logging, localization, observability, CI, static analysis, and container build. The kit removes boilerplate but does not provide a versioned upgrade contract.
- What testing and CI setup does the starter kit provide, and what do I need to add?
- The scaffold includes a testing setup that you should inventory before forking, but the provided context does not detail its coverage. Plan to add your own CI pipeline, static analysis, and container build. Because there is no versioned upgrade contract, verification for every upstream diff is your responsibility.
- What license does gabriel2m/filament-starter-kit use and where do I report security issues?
- The provided context does not state the license or the contribution and security-disclosure channels. Verify both in the repository before adopting the kit. If no security process exists, treat your fork as your own security responsibility and confirm who is accountable for patches and on what cadence.