Weave Code
Coreui Templates Laravel Package
infyomlabs/coreui-templates
CoreUI templates for InfyOm Laravel Generator provide ready-made admin layouts and CRUD view stubs, helping you scaffold Laravel apps with a clean CoreUI interface faster and with less manual frontend setup. Includes Bootstrap-based styling, forms, tables, and navigation snippets for generated resou...
CoreUI templates for InfyOm Laravel Generator
Frequently asked questions about Coreui Templates
- What is infyomlabs/coreui-templates used for?
- It is a template and asset package that provides CoreUI-styled Blade views for CRUD pages generated by the InfyOm Laravel Generator. Instead of the generator's default views, you get responsive Bootstrap-based layouts, forms, and tables for your admin dashboard. It is a thin front-end layer, so it only makes sense if your project already uses Laravel and the InfyOm generator.
- How do I install infyomlabs/coreui-templates with Composer?
- Add it with Composer as a scaffold-time tool, ideally on a scratch branch, then publish the templates and assets using Laravel's vendor:publish command. Because it is template-only, there is no runtime service provider integration to configure. You then point the InfyOm generator at the published template files rather than relying on the package's default resolution.
- Which Laravel versions does infyomlabs/coreui-templates support?
- The package was last released in February 2022, so it was pinned against the Laravel, InfyOm, and CoreUI versions current at that time. Laravel 10, 11, and 12 plus PHP 8.2+ are unverified, and you should assume breakage until you test. Validate Blade syntax and asset expectations against your target Laravel version before adopting it.
- Is infyomlabs/coreui-templates still maintained?
- No. The repository is archived, has a single 2022 patch release, and only around 31 stars, so there are no upstream security or compatibility fixes coming. Treat it as a starting point you fork and own rather than a live dependency. If you adopt it, plan internal maintenance for the templates you extract.
- How do I publish and customize the CoreUI templates?
- Run vendor:publish to copy the package's Blade views and CoreUI assets into your application resources and public directories. Once published, edit the files directly, since the repository is archived and you want your build to stop depending on the package. Committing the extracted templates to your own repo is the recommended path.
- Does it work with InfyOm Laravel Generator CRUD scaffolding?
- Yes, that is its whole purpose: it supplies CoreUI-styled stubs that the InfyOm generator uses when producing CRUD views, layouts, forms, and tables. Integration is done by wiring the templates in as a custom template path in your generator configuration. Test with one representative CRUD module before rolling it out across the project.
- Can I use these CoreUI templates without the InfyOm generator?
- Technically the Blade templates can be copied and adapted, but you lose most of the value because the package is designed around InfyOm's output conventions. Teams not using the generator gain little more than raw CoreUI reference markup. For Tailwind, Livewire, or Inertia stacks, a different UI kit is a better fit.
- Will the 2022-era templates work with Vite instead of Laravel Mix?
- Not out of the box in most cases. The templates assume the asset pipeline and Bootstrap/CoreUI major versions that were current in early 2022, which predates the widespread move from Mix to Vite. You will likely need to update asset directives and reconcile CoreUI and Bootstrap versions with your compiled assets. Audit the layouts and partials before generating real modules.
- How do I configure the InfyOm generator to use a custom CoreUI template path?
- After publishing the views, set the generator's template path to your local, forked copy of the CoreUI templates rather than the vendor package directory. That decouples your build from an archived dependency and lets you patch templates freely. Generate one CRUD page, review the output, and adjust the path configuration until it matches your conventions.
- What are the alternatives to CoreUI templates for Laravel admin panels?
- If you want to stay on InfyOm, you can fork these templates or use the generator's default Bootstrap views and restyle them yourself. Other options include maintaining your own Blade admin starter kit or moving to a currently maintained admin panel package built for your Laravel version. Given the archived state and limited upside, most teams should default to rejecting it unless a prototype is imminent.
Weaver
How can I help you explore Laravel packages today?