- What is roelofjan-elsinga/aloia-cms-gui used for?
- It is the graphical admin interface for the Aloia CMS Laravel package. Instead of building a custom backend, you get a ready-made dashboard where you can create and organise pages, edit content, and manage site settings. It is a presentation and management layer, so it expects the core aloia-cms package to be installed alongside it.
- How do I install aloia-cms-gui in a Laravel application?
- Installation is a normal Composer require: composer require roelofjan-elsinga/aloia-cms-gui. Because it is a GUI layer, you will also need the core CMS package installed and configured, and you should check the repository README for any publish tags or migration steps. The package README was not included in the evidence reviewed here, so confirm the exact post-install commands before wiring it into an existing app.
- Does aloia-cms-gui support Laravel 11?
- Yes. Release 4.2.0 is documented as adding Laravel 11 support. It is a minor version bump under semver, which typically signals an additive compatibility change rather than a breaking API change. What is not stated in the release note is whether Laravel 9 and 10 support was retained or whether the minimum was raised.
- Can I still use this package on Laravel 10?
- Most likely yes, since 4.2.0 is only a minor bump and dual-version support is common for that kind of release. However, the release evidence does not confirm it, so read the composer.json illuminate constraint rather than assuming. If you are already on Laravel 10, there is no urgency to upgrade beyond your normal cadence.
- What PHP version does aloia-cms-gui require?
- Laravel 11 itself requires PHP 8.2 or newer, so any release claiming Laravel 11 support will generally require at least that. Check the php constraint in the package composer.json to confirm the exact floor. If your runtime baseline is older, verify compatibility before scheduling the upgrade.
- Do I need the aloia-cms package installed as well?
- Yes. This package is only the GUI for roelofjan-elsinga/aloia-cms, so the core CMS provides the models, storage, and content API the dashboard talks to. Installing the GUI on its own will not give you a working content store. Set up and configure the core package first, then add the GUI.
- Will upgrading to 4.2.0 break my existing site?
- A minor version bump should not introduce breaking API changes, and the release note only advertises Laravel 11 support. The realistic risk is indirect: if the minimum Laravel or PHP version was raised, consumers on older frameworks are effectively stranded even though the version number looks safe. Run composer update --dry-run -W on a throwaway branch to see the full transitive change set before committing.
- Can I customise the admin dashboard views and configuration?
- The supplied release evidence does not document customisation options such as publishable views or config files, so this needs checking in the repository README. The usual Laravel pattern for a GUI package is to publish assets, views, and config with artisan vendor:publish and then override them in your app. Confirm the available publish tags before planning any custom styling or layout work.
- How should I test this package before rolling it out to production?
- Do the upgrade in two steps: bring your application to Laravel 11 first, then move the package to 4.2.0, so a failure points to a single cause. Pin the versions in a branch, run your test suite, and validate the dashboard in staging against real content. Pay particular attention to indirect upgrades to Symfony components, nesbot/carbon, and monolog, which often ride along with a framework bump.
- Is aloia-cms-gui actively maintained, and what are the alternatives?
- Maintenance activity cannot be judged from a single release note, so check the Packagist release history and the GitHub issue tracker for recent commits and responses. If the package looks dormant, the common alternatives are a general-purpose admin builder such as Filament or Laravel Nova, or a different Laravel CMS package with its own admin panel. Weigh that against the migration cost of moving content off an existing Aloia CMS install.