Weave Code
Story Laravel Package
orchestra/story
Orchestra Story is a Laravel CMS package for Orchestra Platform that adds a simple content publishing layer for stories, pages, and posts. It provides Eloquent-backed models, migrations, and admin-friendly workflows for managing structured content.
CMS Extension for Orchestra Platform
Frequently asked questions about Story
- What is Orchestra Story and is it a general-purpose Laravel CMS package?
- Orchestra Story is a first-party content extension for Orchestra Platform v3.2, not a general-purpose Laravel package. It adds a Content Eloquent model for posts and pages, admin CRUD, slugs, publication status, taxonomy, and Markdown authoring. Adopting Story effectively means running Orchestra Platform as your admin and foundation layer.
- How do I install Orchestra Story in a Laravel application?
- Install it with Composer alongside an Orchestra Platform v3.2-compatible stack, then let Orchestra's ModuleServiceProvider conventions load migrations, views, and config. Verify registration with php artisan route:list --path=story and php artisan migrate --pretend, both of which fail loudly on the wrong stack. Without Orchestra present, do not expect a plain Laravel installation path.
- Can I use Orchestra Story without Orchestra Platform?
- No, Story is a downstream consequence of the Orchestra Platform decision rather than a standalone Laravel CMS. Its service provider extends Orchestra\Foundation\Support\Providers\ModuleServiceProvider, and it assumes Orchestra's ACL, routing, and admin conventions are present. If you are not already on Orchestra v3.2, sequence the platform decision first and evaluate a general Laravel CMS instead.
- Which Laravel and Orchestra Platform versions does orchestra/story support?
- Story targets Orchestra Platform v3.2, with the package built against Orchestra's ModuleServiceProvider and ACL conventions. Pin orchestra/platform or orchestra/foundation to a 3.2-compatible line; the supported Laravel version follows whatever that Orchestra line requires. There is no separate broad Laravel support matrix for Story.
- How does authorization work in Orchestra Story v3.2 and what changed?
- v3.2 moves authorization to an AuthServiceProvider plus a ContentPolicy. The old CanManage middleware is removed, so leftover references become hard runtime failures. Register the policy carefully and verify per-role and per-route, because a misregistered policy can either 403 legitimate editors or fail open to unrelated authenticated users. Treat this as a staged rollout, not a routine composer update.
- What content types and fields does Orchestra Story support?
- Story ships one Content model covering both posts and pages, with slugs, publication status, taxonomy, and Markdown authoring through SimpleMDE 1.9.1. It is plain editorial content rather than a structured or typed content modeling system. Nothing in this release signals versioning, editorial approval workflows, or localization, so treat those needs as scoping signals against adoption.
- How should I render Story content on the front end?
- Use Story as a headless content source by querying the Content model from your own controllers and routes, then render it in your own presentation layer. Story owns admin CRUD, but presentation should remain yours. Building rendering inside Story's admin surface goes beyond what StoryPlugin sanctions and becomes merge-conflict risk on the next Orchestra upgrade.
- How do I customize Story's admin menus, views, and assets?
- Use StoryPlugin to register menus, assets, and admin screens, and keep customizations within that sanctioned seam. Anything built deeper inside Story's admin surface becomes a merge conflict against the next Orchestra bump. For custom fields and views, prefer extending at the integration boundary rather than forking the package.
- What breaking changes should I expect when upgrading to Story v3.2.0?
- v3.2.0 removes the CanManage middleware in favor of AuthServiceProvider and ContentPolicy, and it removes Content::$morphClass. Replace morphClass assumptions with getMorphClass() plus an explicit Relation::morphMap(). The release also deprecates ACL aliases in favor of Orchestra\Support\Facades\ACL. These are the most common worked-in-staging failures, so plan verification before rollout.
- Is Orchestra Story actively maintained enough to use in production?
- Story has zero dependents and a low package score, so there is no community to catch the next breaking change. If you adopt it, your team becomes the maintainer across Orchestra upgrades, and you should price that in. Name an internal owner before adoption, not after the first incident. It is a reasonable cheap add-on inside an existing Orchestra v3.2 admin and a risky Trojan horse if it drives an unscoped platform migration.
Weaver
How can I help you explore Laravel packages today?