- Can I use aerni/font-awesome in a Laravel app without Statamic?
- No. aerni/font-awesome is a Statamic addon, so it only makes sense in an application that already runs Statamic on top of Laravel. In a Laravel-only app, the addon adds a CMS dependency for a problem that a simple enum, config select, or small Blade component already solves.
- Which Statamic, Laravel, and PHP versions does aerni/font-awesome support?
- The supported matrix is defined by the addon's composer.json constraints, not by your host application's constraints. Statamic addons are tightly coupled to core majors, so check the resolved statamic/cms version and the PHP and Laravel requirements before adopting. Pin the addon to a Statamic major and treat upgrades as deliberate, tested events.
- How do I install aerni/font-awesome?
- Install it with Composer using composer require aerni/font-awesome. Statamic addons are typically auto-discovered via the addon manifest, and you may have an optional config file to publish. Then add the Font Awesome fieldtype to the relevant blueprint or fieldset and render its output in Antlers or Blade.
- Does aerni/font-awesome support Font Awesome Pro?
- Yes. The package is described as supporting both Font Awesome Free and Pro. Pro icons require a paid Font Awesome license and usually a hosted kit or licensed assets, so confirm how the addon expects those assets to be supplied. Treat Pro usage as a recurring cost and a compliance obligation.
- Does the addon bundle Font Awesome assets or rely on a CDN or kit?
- That detail is not clear from the overview, so verify it before adoption. Whether assets are bundled, loaded from a CDN, or require a hosted Font Awesome kit affects CSP rules, page weight, offline behavior, and licensing. For production, self-hosting a subset or using a controlled kit is usually preferable to a full CDN CSS payload.
- How are icons rendered in Antlers and Blade templates?
- The package provides simple components and helpers for Blade views and is intended to drop scalable SVG icons anywhere in your app. For Statamic templates, confirm whether the fieldtype augments to raw icon markup, a tag, or class output. Check that you can override the output so you can control accessibility attributes and markup.
- Is aerni/font-awesome actively maintained and tested?
- Signals are thin: 5 stars and 0 dependents suggest a single-maintainer addon with a small audience, and the overview does not advertise CI or test coverage. The maintainer is known in the Statamic community, but there is no ecosystem redundancy. Audit the small codebase, add smoke tests, and pin versions before production use.
- Can editors choose from custom icon sets or only the built-in Font Awesome icons?
- The addon is focused on Font Awesome, so expect the selectable set to be Font Awesome icons rather than arbitrary custom SVG sets. Check the configuration to see whether the available icons or version can be constrained. If you need custom icon libraries, a custom fieldtype or a simpler select field may be a better fit.
- How should I handle accessibility and CSP when using Font Awesome icons?
- Decide per icon whether it is decorative or meaningful. Decorative icons should be hidden from assistive technology, for example with aria-hidden, while meaningful icons need an accessible label or visible text. If you use a CDN or hosted kit, add the required origins to your Content Security Policy and consider self-hosting a subset to reduce payload.
- What happens if I remove aerni/font-awesome later?
- Removal is usually straightforward because the fieldtype persists icon names as strings in your content. You can remove the addon and rewrite the Antlers or Blade templates without a data migration, but keep a value-mapping table and keep the old field for one release cycle so you can roll back. This low lock-in is one of the addon's main advantages.