Weave Code
Fjord Laravel Package
aw-studio/fjord
Fjord is a Laravel package for building admin panels and internal tools. Define resources, fields, filters, and actions in PHP, then get a modern Inertia-powered UI for CRUD, authentication, and customization.
Build content-administration-panels in Laravel
Frequently asked questions about Fjord
- What is Fjord and what can I build with it in Laravel?
- Fjord is a Laravel package for building admin panels and internal tools. You define resources, fields, filters, and actions in PHP and get an Inertia-powered UI for CRUD, authentication, and customization. It suits content administration, internal back offices, and similar admin surfaces inside Laravel applications.
- How do I install Fjord in a Laravel application?
- Install it as a Composer dependency with composer require aw-studio/fjord. Then follow the package setup steps: publish configuration and assets, run migrations if provided, and wire authentication or authorization for admin access. Verify the package's Laravel and PHP version constraints against your app before installing.
- Which Laravel and PHP versions does Fjord support?
- Fjord is distributed via Composer, so its composer.json constraints define the supported Laravel and PHP versions. Check those constraints against your application's framework and PHP versions before adopting it. The provided context does not list exact version numbers, so confirm them in the repository or Packagist metadata.
- How does Fjord compare to hand-building an admin panel in Laravel?
- Fjord provides a structured way to define admin resources, fields, filters, and actions in PHP instead of building CRUD screens from scratch. It adds an Inertia-powered UI and authentication support, which can reduce initial build time for internal tools. Hand-built panels offer full control, while Fjord trades some flexibility for conventions and faster setup.
- Can I customize Fjord's admin UI and resources?
- Yes. Fjord is designed around PHP-defined resources, fields, filters, and actions, and its overview mentions customization alongside the Inertia-powered UI. You can tailor resource definitions and admin behavior to fit your domain. For deeper UI changes, review the package's frontend and publishing options in the repository.
- Does Fjord handle authentication and authorization for admin panels?
- Fjord's overview includes authentication as part of the admin panel experience, so you get a built-in entry point for admin access. You still need to configure who can access the panel and what they can do, typically through your Laravel auth and authorization setup. Review the package documentation for the exact guards, middleware, and policies it expects.
- Is Fjord suitable for production use in a Laravel app?
- Fjord is a Composer package for building admin panels and internal tools in Laravel, so it can be used in production when installed and configured properly. Treat it like any admin dependency: pin versions, test upgrades in staging, and review access control. The repository and release notes are the best source for maintenance status and production readiness.
- How do I test a Laravel admin panel built with Fjord?
- Test the underlying Laravel application as usual with your preferred test suite, covering resource CRUD flows, filters, actions, and access control. Because Fjord's UI is Inertia-powered, include feature tests for the routes and responses your admin screens depend on. Also verify authorization rules so non-admin users cannot reach panel endpoints.
- What are alternatives to Fjord for Laravel admin panels?
- Alternatives include Filament, Laravel Nova, and other Laravel admin panel packages, plus building custom CRUD screens yourself. Fjord's differentiator is its PHP-defined resources, fields, filters, and actions with an Inertia-powered UI. Compare feature fit, Laravel version support, licensing, and maintenance activity before choosing.
- How is Fjord maintained and where can I get help?
- Fjord is an open-source package hosted on GitHub at aw-studio/fjord, so maintenance and support depend on the maintainers and community. Check the repository for recent releases, issues, and documentation before adopting it. For critical internal tools, assign an internal owner for upgrades and configuration.
Weaver
How can I help you explore Laravel packages today?