- What is bluestormdesign/inertia-statamic used for?
- It is an Inertia.js adapter for Statamic that lets you build Statamic-powered sites with Inertia responses and modern JavaScript components. Content management stays in the Statamic control panel while your frontend renders Inertia pages. It is intended for Laravel applications that use Statamic and want an Inertia-driven UI.
- How do I install inertia-statamic in a Laravel app?
- Install it with Composer using composer require bluestormdesign/inertia-statamic. Then follow the repository README for the required Inertia server-side setup and adapter registration. Because exact setup steps can change, rely on the README and composer.json rather than copying generic Inertia instructions.
- Does this package support the Laravel and Statamic versions I am using?
- The package is an Inertia.js adapter for Statamic, so it targets Laravel applications running Statamic. Exact Laravel and Statamic version constraints are defined in the package composer.json and should be confirmed there or in the README before installing. If your app uses older or newer major versions, check open issues and releases first.
- How do I configure Inertia with Statamic using this adapter?
- Configuration is handled through the package's documented adapter setup, which typically involves Inertia middleware, a root Blade view, and Statamic route handling. The README is the source of truth for the exact files and registration steps. Avoid assuming config keys from other Inertia adapters.
- Can I use Vue, React, or Svelte components with Statamic through this package?
- In general, yes: the point of an Inertia adapter is to return Inertia responses that render JavaScript components, so you can use Vue, React, Svelte, or another Inertia-compatible frontend. Statamic still supplies the content and control panel experience. The adapter bridges Statamic routing and data into Inertia page props.
- How do I test Inertia responses in a Statamic site using this adapter?
- Test your pages with Laravel's HTTP testing tools and Inertia's testing helpers where available, asserting component names and props. For package-level behavior, check the repository for its own test suite and CI status. Keep tests focused on the responses your app returns rather than the adapter internals.
- Is inertia-statamic suitable for production Statamic sites?
- It can be used in production if you pin a compatible version, build your frontend assets, and follow the README setup. Pay attention to caching, asset versioning, and any SSR configuration if you use Inertia SSR. Review the repository's issue history and releases for known production concerns.
- What are alternatives to inertia-statamic for building Statamic sites with JavaScript?
- Alternatives include using Statamic's native Antlers or Blade rendering, building a custom Inertia integration, or evaluating other community Statamic-to-Inertia packages. The right choice depends on how much JavaScript-driven UI you need and whether you want to keep Statamic's standard routing. Compare maintenance activity and Laravel and Statamic version support before switching.
- How do I keep inertia-statamic updated and check its maintenance status?
- Check the GitHub repository for recent commits, releases, and open issues, and confirm the package on Packagist. Pin a known-good version in composer.json and review changelogs before upgrading. If the project is inactive, plan for forking or a custom adapter.
- Do I still manage content in the Statamic control panel when using Inertia?
- Yes, the adapter is designed to let you keep content management in the Statamic control panel while serving Inertia responses to the frontend. Editors work in Statamic, and your JavaScript components receive the data as Inertia props. You still need to define how collections, routes, and templates map to Inertia pages.