- How do I install filament-faq in a Laravel application?
- Install the package with Composer using the ^1.1 release, publish its config and migrations, register the plugin in your Filament panel, and run migrations. Confirm Filament and Laravel compatibility first, then configure navigation and access control. Test in a non-production branch before rolling out.
- Which Laravel and Filament versions does this package support?
- The package is built for Laravel applications that already use Filament admin panels, but the provided context does not list an exact support matrix. Check the repository composer.json and README for supported Filament major versions, Laravel 10/11/12, PHP 8.1+, and database requirements. Treat version compatibility as a gate before committing.
- Does filament-faq provide public FAQ pages or only admin CRUD?
- The package is described primarily as a Filament admin resource for creating, organizing, and publishing FAQ entries. It does not clearly guarantee public routes, controllers, or frontend views, so plan frontend work if you need a public FAQ page. Verify the 1.1.0 release contents before assuming rendering is included.
- How are FAQ categories and display order managed?
- The package includes category grouping for organized question sets and sort ordering to control display priority. You manage these through the native Filament resource rather than custom admin code. Review the included models and migrations to map categories and ordering to your existing content schema.
- Can I keep FAQs as drafts and control visibility?
- Yes, the package provides publish toggles for draft and visible states. Use those states when querying content for public display, and confirm how the package exposes scopes or fields. This lets editors prepare FAQs before making them live.
- Does filament-faq support multiple languages and the new 17 locales?
- Version 1.1.0 adds 17 locales, which improves multilingual admin experiences, but translations may be community-contributed and partially reviewed. Configure Laravel localization and verify fallback behavior in your app. If you use RTL locales such as ar, fa, or he, perform in-market QA on labels and validation messages.
- How do I restrict who can manage FAQs in Filament?
- Because FAQ management is a Filament resource, use Filament panel access, policies, and authorization patterns to control who can view or edit entries. Configure navigation and permissions as part of installation. The provided context does not indicate built-in multi-tenant support, so assess that separately if needed.
- Is upgrading from 1.0.0 to 1.1.0 safe?
- The 1.1.0 release is a minor version with no indicated breaking changes, so it should be a low-risk upgrade for compatible apps. Validate the new locale files and fallback behavior, run your existing tests, and review the changelog. Pin to a minor range to avoid unexpected updates.
- What are the maintenance and production risks of this package?
- Key risks include solo-maintainer bus factor, an unclear Filament and Laravel support matrix, and community-contributed translations that may need review. Positive signals include standardized CI workflows and Dependabot updates. Pin versions, monitor upstream Filament changes, and be prepared to fork or patch small compatibility fixes.
- When should I choose this package versus a custom FAQ module or another platform?
- Choose filament-faq when your Laravel app already standardizes on Filament and you want a low-cost FAQ CRUD module with categories, ordering, and publishing. If you do not use Filament, treat it as an indirect dependency and compare a simple custom CRUD module or a standalone FAQ platform. It is not positioned as a public knowledge base or headless content service.