Runway Laravel Package

Product Decisions This Supports

• Build vs. buy for CMS-layer admin UIs: Runway lets a Laravel app expose existing Eloquent models (products, listings, locations, custom domain entities) as first-class Statamic resources—so PMs can choose "reuse the existing schema and add an editing layer" instead of building bespoke admin CRUD from scratch or migrating data into flat-file content.
• Roadmap: "manage everything in one CMS" initiatives. If your roadmap includes consolidating editorial workflows (marketing pages + structured data) into Statamic, Runway is a key enabler: editors gain publish/version/draft behavior over database-backed records without engineering rebuilding the data model.
• Feature scoping for structured data. The new orderable resources support (v9.7.0) means PMs can commit to reordering UIs for database-backed records (e.g., featured products, sortable FAQs, ordered navigation items) without custom sort-field engineering—useful when prioritizing merchandising and content-ordering features.
• Performance/ops tradeoffs. The new config option to disable static cache warming signals a tunable caching story: PMs can make informed decisions about page-generation cost vs. freshness, particularly for large Runway collections or frequently invalidated URIs, and set SLAs accordingly.
• Content-modeling fidelity. The nested JSON field fix in title_field/title_format matters for teams storing structured attributes (e.g., name.{locale}, details.brand) in JSON columns—supports product decisions to keep flexible JSON schemas rather than normalizing every field upfront.

When to Consider This Package

Consider Runway when:

• You already have (or plan) a relational database schema in Laravel and want Statamic's editorial UX, routing, and templating over it without duplicating content into Markdown files.
• You need editors to manage records that have relationships, validation, or lifecycle rules (orders, listings, inventory) that flat-file content models handle poorly.
• You want one control panel for both marketing pages and structured/domain data, reducing tool sprawl and engineering maintenance of custom admin panels.
• Your team is comfortable with Eloquent, migrations, and Laravel conventions—Runway assumes a model-first mental model.
• You need orderable/selectable resource behavior and title derivation from arbitrary (including nested JSON) attributes—both improved in v9.7.0.

Look elsewhere when:

• Content is purely editorial and flat-file friendly; native Statamic collections are simpler with less operational surface.
• You require strict separation between CMS and transactional systems, or cannot grant the CMS write access to core application tables.
• The team lacks Laravel/DevOps depth to own caching, invalidation, and URI strategy (the new cache-warming toggle assumes this ownership).
• You need a fully managed/no-code solution; Runway is developer-oriented and adds an integration layer to maintain across upgrades.

How to Pitch It (Stakeholders)

For executives: Runway is a mature, actively maintained Statamic addon that lets us put a polished editorial interface over data we already store in our database—without a costly content migration or a parallel admin tool. That means faster time-to-market for CMS-driven features, fewer bespoke CRUD builds, and lower long-term maintenance. The v9.7.0 release is incremental and low-risk: it adds configurable cache warming (a performance/cost lever), orderable resources (unlocks merchandising and ordering features out of the box), and a fix for nested JSON titles (improves reliability for structured content). No breaking changes.

For engineering: Adoption is idiomatic Laravel—define a resource around an existing Eloquent model, map fields, and Statamic handles the authoring UX, routing, and caching. Recent releases strengthen production fit: you can now disable static cache warming of Runway URIs for high-churn or large datasets, support first-class ordering on resources, and trust title generation from nested JSON attributes. Upgrade path from v9.x is non-breaking. Effort is primarily configuration plus a caching/invalidation strategy; ongoing cost is version tracking as Statamic and Laravel evolve.

Recommendation: Proceed with a scoped pilot on one or two high-value models, with explicit ownership of cache strategy and a defined upgrade cadence.