Weave Code
Stisla Templates Laravel Package
infyomlabs/stisla-templates
Laravel package that supplies Stisla admin dashboard templates for InfyOm Laravel Generator, helping you scaffold consistent CRUD views, layouts, and UI components with the Stisla theme. Useful for quickly generating admin panels with InfyOm's code generator and customizing generated pages.
Stisla templates for InfyOm Laravel Generator
Frequently asked questions about Stisla Templates
- How do I install infyomlabs/stisla-templates in a Laravel project?
- Install it with Composer using composer require infyomlabs/stisla-templates, then publish the package's Blade views and assets into your application so the generated CRUD screens use the Stisla layouts. The package is a presentation-layer asset set, so it assumes you already have the InfyOm Laravel Generator installed and configured. After publishing, generate a CRUD module and confirm the output matches the Stisla navigation, tables, and forms. Note that the latest release is v4.0.0 from February 2022 and the repository is archived, so treat installation as a one-time scaffolding step rather than an ongoing dependency.
- Which Laravel versions does infyomlabs/stisla-templates support?
- The last release, v4.0.0, added Laravel 9 support and is the documented ceiling for the package. Because the repository is archived, there is no official Laravel 10 or Laravel 11 support. Running it on newer Laravel majors is unverified and typically requires patching the published Blade templates yourself, particularly around auth scaffolding, pagination views, and asset pipeline wiring. Confirm compatibility against your actual Laravel target before adopting it for new work.
- Is infyomlabs/stisla-templates still maintained?
- No. The repository is archived and the most recent tagged release is v4.0.0 from 2022-02-25, so there are no security patches, no new Laravel version support, and no responses to upstream changes. That does not make it unusable, because the package only ships Blade views and assets rather than runtime business logic. The practical approach is to publish and fork the templates into your own repository so you control future changes. Depending on an archived package directly in a critical path is generally discouraged.
- Do I need the InfyOm Laravel Generator to use stisla-templates?
- Yes. This package is a set of Stisla admin theme view templates that are consumed by the InfyOm Laravel Generator when it scaffolds CRUD pages. Without the generator in your stack, the package has no consumer and adds nothing to your application. It also has hidden coupling to the generator's view API and variable contract, so a generator upgrade can silently break published views. Verify that your generator version is compatible with your Laravel target first.
- How do I customize the generated Stisla CRUD views?
- Publish the package views into your resources/views directory and edit the Blade files directly, since customization happens through published, forkable templates rather than configuration options. Once published, those views are yours to change freely and there is no hard runtime coupling at page-render time. The recommended pattern is to vendor the published templates into your repository and treat them as first-party code under your own change control. That converts an archived third-party dependency into an owned asset.
- Does stisla-templates work with Laravel 10 or Laravel 11?
- There is no official support for Laravel 10 or 11; Laravel 9 is the documented maximum and the package has been archived since 2022. In practice, developers report needing to patch auth view scaffolding, pagination view bindings, CSRF-related markup, and asset pipeline assumptions. Because the templates are published into your app, these patches live in your codebase rather than in a package update. Budget time for that manual work if you are on a current Laravel major.
- Can I use Stisla templates with Vite or Tailwind instead of Laravel Mix and Bootstrap?
- Stisla is a Bootstrap-based admin theme, and Stisla-era assets typically assume Laravel Mix rather than Vite. Adopting it alongside Vite requires manually wiring the CSS and JavaScript assets into your build, and the markup will not align cleanly with a Tailwind or component-library design system. Confirm your frontend build pipeline before committing, because the package fits conventional Blade monoliths well and headless, SPA-fronted, or design-system-governed apps poorly. Mixing it into a Tailwind project usually creates a second admin UI you will later have to consolidate.
- Is it safe to use an archived Composer package like stisla-templates in production?
- The blast radius is limited because the package contains only Blade layouts, partials, auth screens, and CRUD view stubs, with no runtime service or business logic. The real risks are the absence of security patches, drift from current accessibility and frontend tooling expectations, and silent breakage when the InfyOm Generator's view contract changes. A safer posture is to use it once to scaffold views, then vendor the published templates into your repository and drop the Composer dependency from the critical path. Also confirm your organization's policy on archived dependencies before shipping.
- What are the alternatives to infyomlabs/stisla-templates for Laravel admin scaffolding?
- If you are committed to InfyOm Generator, other theme packages from the same vendor cover different visual languages, so the generator stays the same and only the view set changes. If you are open to changing tools, Laravel Breeze and Jetstream cover auth and starter scaffolding while Filament, Nova, and similar packages provide full admin panels. The right choice depends on whether InfyOm Generator is already your scaffolding engine and whether Stisla matches your design commitments. Moving away from archived packages usually means moving the templating responsibility in-house.
- Can I copy the Stisla templates into my own repository instead of depending on the package?
- Yes. The MIT license permits vendoring the templates in-repo, and given the repository's archived status this is the likely end state. The recommended sequence is to install and publish into a throwaway branch, generate a representative CRUD module end to end including index, create, edit, show, and auth screens, and diff the output against your current admin baseline. If the result is acceptable, commit the published templates as first-party code and remove the Composer dependency from your critical path. Note that v4.0.0 was a major bump whose changelog only mentioned Laravel 9 support, which implies a breaking drop of older Laravel versions worth confirming.
Weaver
How can I help you explore Laravel packages today?