- How do I install Kompass in an existing Laravel application?
- Install it with Composer using secondnetwork/kompass; the KompassServiceProvider is auto-discovered. Publish the package migrations and stubs, run php artisan migrate, publish the frontend assets, then build with bun install and npm run build so Vite emits into public/assets/build. Confirm that output path does not collide with your host app's own asset manifest before deploying.
- Which Laravel and Livewire versions does Kompass support?
- The package targets Laravel 11 and 12 on the TALL stack, with Livewire 4, Tailwind 4, Alpine, Preline UI and DaisyUI on the admin surface. There is no published compatibility matrix, so treat that version list as current intent rather than a guarantee. If Livewire 4 is not stable in your dependency graph, that is a hard blocker.
- Does Kompass work with Livewire 3?
- No. Kompass uses Livewire 4 attributes including #[Locked] and #[Layout] proactively, so it pins you to Livewire 4. If your app is still on Livewire 3 you would need to upgrade first or choose another CMS package. Because this ties your framework upgrade cadence to a package's prerelease choices, verify Livewire 4 stability before adopting.
- Can I use Kompass with an Inertia, Vue or React frontend?
- Kompass is built for Blade plus Livewire, with both admin and public rendering going through views namespaced kompass::. If your product surface is Inertia, Vue, React or a separate SPA, the admin and public paths diverge and you absorb integration cost on both sides. It is a good fit mainly when your frontend is already Blade and Livewire.
- How do I override Kompass views and keep changes after composer update?
- Publish the package views and stubs, then override the kompass:: namespaced views from your application. Published copies live in your resources/views/vendor directory and survive composer update, whereas edits inside the vendor package do not. Pin the package version and re-check overrides after each upgrade, since no back-compat policy is stated.
- Does Kompass have tests, and is it safe for production?
- The repository states no dedicated test suite in tests/, which is the single largest risk for a CMS that owns content, routing and slugs. Adoption is thin, the bus factor is effectively one, and there is no security disclosure policy or compatibility matrix. The MIT license means you can fork and maintain it yourself, but budget for that rather than assuming vendor support.
- How does Kompass model content beyond pages and posts?
- Content modeling uses pages, posts and datafields, with slugs generated through Str::slug. That covers conventional flat pages plus posts and custom fields, but localization, multi-site, structured content types and versioning are not documented features. Assess those as gaps you would have to build rather than capabilities you can assume.
- Will Kompass conflict with morph maps in my application?
- KompassServiceProvider registers morph maps for Page, Post and Datafield at boot, which is convenient but reaches into polymorphic resolution for the whole application. If your app or another package already defines relations on those morph aliases, expect collisions. Audit existing morphMap entries before installing and test the interaction on a staging branch.
- How does Kompass handle cache invalidation?
- Cache flushing is implemented in model boot hooks on create, update and delete. That is simple and correct for normal editorial traffic, but it couples cache writes to model writes and can cause invalidation storms during bulk imports or programmatic content sync. For large imports, wrap or disable the hooks and flush deliberately.
- What are the alternatives if Kompass looks too risky?
- Compare it against established Laravel CMS packages and headless CMS options if you need multi-language, roles and permissions, a media library or audit trails out of the box. Kompass is MIT licensed and forkable, so the risk is maintenance budget rather than legal exposure. The deciding factors are your Blade and Livewire commitment and whether you can absorb an unaudited upgrade path.