Weave Code
Faq Widget Laravel Package
friendsofvictoire/faq-widget
A ready-to-drop-in FAQ widget for Laravel applications. Render question-and-answer lists as clean, collapsible accordion panels, with simple configuration and Blade integration so you can add a searchable, styled FAQ section to any page in minutes.
friendsofvictoire/faq-widget provides a lightweight, reusable FAQ widget for PHP applications. It turns a simple list of questions and answers into a clean, collapsible FAQ block, making it easy to add help content, product FAQs, or support sections without building custom markup.
- Simple configuration for questions, answers, and display order
- Accessible accordion markup with keyboard-friendly interactions
- Customizable templates and styling to match your app
- Framework-agnostic PHP integration via Composer
- Lightweight with no heavy frontend dependencies
Frequently asked questions about Faq Widget
- Does friendsofvictoire/faq-widget work with Laravel?
- No. It is a Symfony bundle (WidgetFAQBundle) built for the Victoire DCMS and integrates through Symfony's DI container, HttpKernel, Twig, and Victoire's widget registry contracts. Laravel's service providers, facades, Illuminate contracts, and Blade have no overlap with those extension points. Installing it in a Laravel app produces an autoloadable library that registers nothing and renders nothing.
- Can I install friendsofvictoire/faq-widget with Composer in a Laravel project?
- Composer will most likely refuse outright, because the bundle pins symfony/* to 2.x/3.x-era constraints and PHP to 5.x/7.0, conflicting with any current Laravel or Symfony dependency tree. Even with platform requirement overrides, the result is code that never hooks into Laravel's request lifecycle. There is no Laravel-side API surface, no config file, and no route or view registration.
- Is friendsofvictoire/faq-widget still maintained?
- No. The last release was 2016-08-22, roughly nine years without a release, and the repository has 1 star, 0 dependents, and no forks to inherit. There is no PHP 8 support and no security response process. Adopting it means owning unmaintained code you have to patch yourself.
- What PHP and Symfony versions does this FAQ widget require?
- Expect PHP 5.x/7.0 and Symfony 2.x/3.x constraints, matching the Victoire DCMS era it was written for. There is no published compatibility matrix and no CI badge of consequence. Read the bundle's composer.json directly to confirm the exact php and symfony/* pins before making any decision.
- Do I need Victoire CMS to use friendsofvictoire/faq-widget?
- Yes. The bundle registers a widget through Victoire's widget interface, abstract widget base class, and DCMS rendering pipeline, so without a running Victoire instance it renders nothing. Standing up Victoire itself (Symfony, Doctrine, its admin and theme layers) just to output a list of questions is disproportionate to the feature's value.
- What is the fastest way to add a FAQ section to a Laravel app instead?
- Reimplement it natively: an Eloquent model plus migration for question-and-answer pairs, an ordering column, and a Blade partial to render them. For editing, use a Filament or Nova resource, or a simple JSON repeater column. The scope is days rather than weeks, and the result is owned in-house, testable, and on a supported runtime.
- Does friendsofvictoire/faq-widget include a service provider, config file, or Blade views?
- No. It ships Symfony bundle classes and Twig templates for Victoire, not Laravel service providers, facades, Illuminate contracts, or Blade views. Laravel's package discovery has nothing to register. Any Laravel integration would mean writing a port from scratch, at which point writing the feature directly is cheaper.
- Are there security concerns with friendsofvictoire/faq-widget?
- Output escaping, CSRF protection on any admin form, and stored-XSS handling for FAQ body content have never been third-party verified and will not be revisited upstream. Combined with the age of the code and abandoned transitive dependencies, you cannot patch the exposure in isolation. A fresh implementation on Laravel's escaping and validation defaults is safer.
- How do I migrate existing Victoire FAQ content into Laravel?
- Keep the content model, not the code. Export the FAQ entities (question, answer, ordering, plus any localization or publishing fields) from the Victoire database and map them into an Eloquent model and migration. If Victoire stays deployed for other reasons, keep the FAQ there and consume it from Laravel through a cached JSON endpoint. The schema is the only durable asset in this repository.
- What are the alternatives to friendsofvictoire/faq-widget for Laravel?
- Most teams build a small in-house FAQ module, since the feature is a title, a body, an ordering field, and a list view. If you want something off the shelf, choose an actively maintained Laravel package with PHP 8 support, recent releases, and CI, or an admin panel resource such as Filament. Avoid any package whose last release predates PHP 8.
Weaver
How can I help you explore Laravel packages today?