Weave Code
Admin Laravel Package
capell-app/admin
Filament panel package for Capell CMS that provides the authenticated editor and operator back-office UI: manage pages, sites, languages, layouts, themes, media, users, roles, settings, packages, and upgrades, with admin extension points. Requires capell-app/core.
Filament administration, page editing, recovery, settings, and operations for Capell CMS.
Frequently asked questions about Admin
- What is capell-app/admin used for?
- It is the Filament panel package for Capell CMS, providing the authenticated editor and operator back-office UI. It covers pages, sites, layouts, media, users, roles, settings, dashboards, and package state. It is intended for Capell installs that need an admin panel, not for public frontend rendering.
- Do I need capell-app/core to use capell-app/admin?
- Yes. The README states that capell-app/admin depends on capell-app/core, which owns the shared content records and migrations. Installing admin without core is not a supported standalone setup. Plan your Capell installation around both packages.
- Which Laravel and Filament versions does capell-app/admin support?
- The README lists PHP 8.4 and Filament 5.7.6, and Packagist publishes a Laravel compatibility badge for the package. Check the badge and release notes for the exact Laravel versions supported by the capell-app/admin release you plan to use. Because the package is tied to Capell CMS releases, confirm compatibility against your capell-app/core version as well.
- How do I install capell-app/admin in a Laravel application?
- Install it with Composer as part of a Capell CMS installation, alongside capell-app/core. Follow the Capell docs for panel registration, migrations, and admin setup rather than treating it as a generic Filament plugin. Verify the installed release's requirements before running migrations in an existing app.
- Can I use capell-app/admin without Capell CMS as a standalone Filament admin panel?
- No, it is not positioned as a standalone Filament admin panel. The package depends on capell-app/core and provides Capell-specific resources, workflows, policies, and settings. If you only need generic Filament resources, use Filament directly or a general-purpose admin package instead.
- How do I extend the Capell admin panel with custom resources, pages, or widgets?
- The package documents admin extension points for contributed resources, pages, widgets, header tools, form schemas, table queries, relation managers, and validation hooks. Use those hooks instead of editing vendor files so your customizations survive updates. Check docs.capell.app for the extension APIs in your installed version.
- Does capell-app/admin handle public frontend rendering or HTML output?
- No. Admin owns the Filament back-office UI, while public request handling and public HTML safety belong to Frontend and frontend add-ons. Do not use capell-app/admin to render public pages. Keep admin routes authenticated and separate from public content delivery.
- How are users, roles, and permissions handled in capell-app/admin?
- Admin includes users, roles, policies, and permission-related resources for the Capell back office. It owns admin policies for its Filament resources, so review how those policies map to your existing authorization model. Confirm whether your app can reuse existing Filament policies or must align with Capell's roles and permissions.
- What migrations, settings, or cache commands does capell-app/admin add?
- Admin owns admin settings migrations and admin-specific cache commands, while shared content records and migrations belong to capell-app/core. Review both packages' migrations before upgrading, especially on an existing database. Treat admin migrations as part of your deployment and rollback plan.
- Is capell-app/admin production-ready and what alternatives should I consider?
- It is intended for production Capell back offices, but assess release maturity, test badges, changelogs, and open issues for the exact version you deploy. Pin versions, test migrations and critical editor workflows in staging, and monitor updates from the Capell project. Alternatives for Laravel admin UIs include Filament on its own, Laravel Nova, Backpack, or custom Filament resources if you do not need Capell CMS.
Weaver
How can I help you explore Laravel packages today?