Weave Code
Blade Academicons Laravel Package
codeat3/blade-academicons
A Laravel Blade component package for using Academicons icons in your views. Render scholarly and academic SVG icons with simple Blade tags, with support for sizing and styling via CSS classes. Ideal for Laravel apps needing academic iconography without hand-writing SVG markup.
A package to easily make use of Acamedicons in your Laravel Blade views.
Frequently asked questions about Blade Academicons
- How do I install codeat3/blade-academicons in a Laravel app?
- Install it with composer require codeat3/blade-academicons. Laravel package auto-discovery registers the Blade components automatically, so there is no service provider to add by hand. Optionally publish the config file if you need to change defaults.
- Which Laravel and PHP versions does blade-academicons support?
- The 1.9.0 release widened its constraints to add Laravel 13 compatibility and shipped no API, config, or output changes. Check the constraint block of the specific tag you pin against your current Laravel and PHP versions, especially if you are still on Laravel 10 through 12. If a framework upgrade is already on your roadmap, that release reduces the risk of a blocker.
- How do I render an ORCID or Google Scholar icon in a Blade view?
- Every Academicons glyph is registered as a Blade component, so you write tags like x-academicons-orcid or x-academicons-google-scholar directly in your template. Each one renders as inline SVG at request time, with no npm install or asset build step. The same tags work in regular Blade views, component views, and Blade-rendered Markdown.
- How do I change the size and color of an Academicons icon?
- Attributes passed to the component, including class and fill, are forwarded to the root svg element. That means you can size and color icons with ordinary Tailwind or utility classes rather than package-specific options. Because it is plain SVG with currentColor-friendly styling, it also composes with dark mode conventions in your existing layout.
- Can I change the component prefix used by blade-academicons?
- Yes. The package ships a single publishable config file that controls the component prefix. After editing it, clear your compiled views and config cache, because a stale compiled view or cached config referencing the old prefix can throw errors on every page that renders an icon.
- Does blade-academicons work with Livewire and Blade Markdown views?
- Yes. The package is a presentation-layer wrapper that registers Blade components, so it works anywhere Blade renders, including Livewire component views and Blade-rendered Markdown templates. It is not intended for JavaScript or React SVG build pipelines, where a sprite sheet or a JS icon library is the better fit.
- Why am I getting an unable to locate component error for an Academicons icon?
- That error usually means the slug does not match a registered component, so confirm the exact icon name in the package's component list. It can also appear after a component prefix change or a composer update if the compiled view or config cache is stale. Run the view and config clear commands and retry, then verify the installed version's tags.
- Do I need to install the Academicons CSS or font files manually?
- No. The package registers the required icon styles and ships the icons, so there is nothing to import by hand and no npm or asset build step. Each component outputs inline SVG rather than depending on an external font file. That keeps setup to a composer require plus a quick check that a component renders.
- Can I pass extra attributes like aria-label or class to the icons?
- Yes. Attributes such as class, aria-label, and fill pass through to the root svg element, so icons inherit your styling and accessibility conventions. This makes them easy to pair with existing utility classes and screen-reader labels. A common pattern is wrapping the icon in your own component that also handles the anchor tag, rel attributes, and link text.
- Is codeat3/blade-academicons actively maintained, and what are the alternatives?
- It has a single primary contributor and a small install base, so expect compatibility and icon-sync maintenance releases rather than new features. To limit lock-in, consume the icons behind your own wrapper component so swapping icon packs is a one-line change. Alternatives include writing the SVG markup yourself, using a sprite sheet, or using a broader icon package if it already covers the academic marks you need.
Weaver
How can I help you explore Laravel packages today?