Weave Code
Runway Laravel Package
statamic-rad-pack/runway
Runway lets you use Eloquent models as content sources in Statamic. Register your models as collections, browse and edit records in the control panel, and query them with familiar Eloquent syntax—no custom code or external APIs required.
Use Eloquent in Statamic like never before.
Frequently asked questions about Runway
- How do I install Runway in a Laravel and Statamic application?
- Install Runway with Composer; its service provider is auto-discovered, so no manual registration is needed. Publish the package config, then define a resource for each Eloquent model you want to expose. Each resource gets a blueprint and fieldsets, which is how fields appear in the Control Panel. Start with a single resource and expand after a Control Panel smoke test.
- Which Statamic, Laravel, and PHP versions does Runway v9.7.0 support?
- Runway v9.7.0 is a minor release within the v9 line, which tracks Statamic major versions. The evaluation assumes a Laravel and Statamic application on PHP 8.2+ with a current Laravel LTS, but you should confirm the exact constraints in the package's composer.json at lockfile time. Pin the addon to the same Statamic major as your application. Ask the maintainers about their published policy for the next Statamic major before planning a large upgrade.
- How do I make an Eloquent model editable in the Statamic Control Panel?
- Register the model as a Runway resource in configuration and attach an existing Statamic blueprint with the fieldsets you want editors to see. Records then appear in the Control Panel with Statamic's familiar publishing UI, including publish states and model relationships. No custom CRUD screens or sorting controllers are required. Resources are additive, so they run alongside your existing collections and entries without conflict.
- Can I query Runway resources in Antlers and GraphQL?
- Yes. Runway resources can be queried and rendered in Antlers templates and Blade, and exposed through GraphQL the same way native collections are. You can also query the underlying records with familiar Eloquent syntax from your application code. That means one data source serves both the Control Panel and your front end instead of duplicating content between flat files and the database.
- Do orderable Runway resources require a database schema change?
- Orderable resources were added in v9.7.0 and remove the need for hand-rolled drag-and-drop sorting controllers for models that have an order column. That means the model's table needs an order column, so add it and backfill existing rows in the same migration before enabling ordering. Enable ordering per resource and start with a single low-risk model. Explicitly test writes, how duplicate or tied order values behave, and that reorder positions persist after saving.
- How do I disable static cache warming for Runway URIs?
- v9.7.0 adds a config switch that disables static cache warming of Runway URIs. The flag exists because warming is not universally safe: sites with a large URI surface, or with an existing invalidation strategy, may not want it. Set the flag per environment, leaving warming on in staging to observe the cost, and turn it off in production only after confirming an alternative keeps caches correct. Treat the default as something to evaluate rather than assume.
- Does Runway handle nested JSON fields in title_field and title_format?
- Runway supports title_field and title_format, including nested JSON paths written in dot notation. v9.7.0 includes a fix (#844) for how those nested JSON titles resolve, which affects how resources are labelled in the Control Panel and in listings. Treat it as a behavior change for verification purposes even though it is labelled a fix. Re-check any resource using dot notation in the Control Panel, in listings, and in every template that renders the title.
- How are permissions and authorization handled for Runway resources?
- Permission mapping is one of the residual risks flagged in the technical evaluation, so verify it rather than assume it. Establish how Statamic role permissions and Laravel policies each apply to a resource's records before relying on either. Build a small permission matrix early and test it against real user roles. If you need policy-level control, confirm current behavior with the maintainers.
- How do I migrate existing custom CRUD screens to Runway?
- Adopt Runway incrementally rather than as a big-bang replacement. Start with one read-mostly table that currently has an awkward admin story, ship it as a single resource, and expand only after the Control Panel and templates check out. This replaces the usual alternative of custom CRUD screens or external APIs kept in sync with Statamic content. For orderable models, run the order column migration and backfill before enabling ordering on that resource.
- What are the production risks and maintenance considerations for Runway?
- Technical risk is assessed as moderate-low: v9.7.0 is a minor release with no breaking changes or deprecations signalled, and the package tracks Statamic major versions. The remaining risks are structural: schema drift when a column or table is renamed, coupling to Statamic major upgrades, multi-site and localization semantics, and cache-warming cost on large URI sets. Upgrade in staging, run your test suite plus a Control Panel smoke pass, and confirm blueprints, routes, and GraphQL schemas still resolve. For business-critical reliance, ask about release cadence, maintainer depth, and commercial support options.
Weaver
How can I help you explore Laravel packages today?