Weave Code
Filament admin panel, editor workflows, settings, and extension points for Capell CMS.
Frequently asked questions about Admin
- Can I use capell-app/admin without Capell CMS? What Filament features remain available?
- The package is tightly coupled to Capell CMS, so core Filament features like tables, forms, and widgets will still work, but Capell-specific workflows (e.g., EditorWorkflow) require Capell integration. You can strip down the package to use only Filament components, but Capell-dependent features will be unavailable.
- What Laravel and Filament versions does capell-app/admin support?
- The package requires **Filament v3+** and is designed for **Laravel 10/11**. Check the package’s hidden dependencies (via `composer show capell-app/admin`) for exact version constraints. If using an older Filament version, migration effort may be significant.
- Does this package introduce new database tables, or does it rely on Capell’s schema?
- The package likely introduces tables for **settings, workflows, or Capell-specific resources**, but it may also leverage Capell’s existing schema. Review the package’s migrations or documentation to avoid conflicts with custom admin logic or third-party packages like Spatie Media Library.
- How do I customize Filament widgets or Capell-specific UI components?
- Customization follows Filament’s patterns—override Blade views, extend React/Vue components, or use Filament’s `PanelServiceProvider` for global tweaks. Capell-specific UI (e.g., EditorWorkflow) may require extending Capell’s abstractions, which could limit reuse of existing Filament policies or authorizations.
- Are there alternatives to capell-app/admin for Laravel admin panels with CMS features?
- For Filament-based solutions, consider **Filament CMS plugins** (e.g., `filament/cms`) or **Nova/Backpack** for traditional admin panels. If you need lightweight CMS integration, **Laravel Scout + custom Filament resources** might suffice without Capell’s coupling.
- How do I migrate from an existing admin panel (e.g., Nova, Backpack) to capell-app/admin?
- Migration depends on whether you’re adopting Capell CMS. If not, focus on porting Filament resources manually. For Capell users, check for **data migration scripts** or Capell’s documentation on transitioning from other panels. Test thoroughly—Capell’s workflows may not align with legacy admin logic.
- What’s the maintenance status of capell-app/admin? Is there community support?
- The package has **no visible repository or stars**, raising red flags for maintenance. Verify the **Capell CMS team’s activity** (e.g., GitHub issues, release notes) and check if they offer paid support or a Slack/Discord community. Unmaintained packages risk breaking changes or security gaps.
- Does capell-app/admin support multi-tenancy or role-based access control (RBAC)?
- RBAC likely follows **Capell’s built-in permissions** or Filament’s policies. If your app uses **Laravel’s native gates/policies**, you may need to bridge them with Capell’s RBAC system. Check if the package provides extension points for custom authorization logic.
- How do I handle performance overhead from Filament + Capell workflows?
- Filament adds ~50MB to your project, and Capell workflows (e.g., React/Vue editors) may introduce frontend latency. Optimize by **lazy-loading Filament panels**, caching workflows, and benchmarking critical paths like content editing. Avoid heavy Capell features in high-traffic areas.
- Can I extend capell-app/admin with third-party plugins, or are extensions Capell-exclusive?
- The package mentions ‘extension points,’ but these may be **Capell-specific** (e.g., hooks for EditorWorkflow). Verify if Filament’s `PanelServiceProvider` or event system supports third-party plugins. If extensions are Capell-exclusive, your customization options may be limited.
Weaver
How can I help you explore Laravel packages today?