Partials Module Laravel Package

Product Decisions This Supports

• Feature enablement: In-CMS reusable content fragments — promo banners, CTA blocks, legal/boilerplate copy, shared footers, campaign snippets — editable by non-engineers without a deploy. This is a content-ops self-service primitive, not a personalization, A/B, scheduling, or localization engine; don't let it be scoped as one.
• Roadmap / feature parity: Closes a checkbox most stakeholders assume a CMS already has (WordPress reusable blocks, Drupal blocks/paragraphs, Contentful reusable entries). Cheap way to defer a "we need a real CMS" conversation by a quarter.
• Build vs. buy: This isn't really a "buy." The decision is adopt ecosystem module vs. hand-roll a snippets table + admin CRUD. If the app already runs the Anomaly/Streams Platform, adoption is hours; hand-rolling is roughly 1–3 dev days plus ongoing admin-UI upkeep and permission work.
• Replatforming input: Signals how much custom content tooling the current stack forces you to assemble from parts. A long list of niche addons like this is an argument for consolidating onto a maintained CMS or headless provider.
• Risk budgeting: Sets the expectation that this capability is community-maintained internal tooling — fine for back-office editing surfaces, not fine for anything customer-critical or compliance-bearing without a wrapper and tests.

When to Consider This Package

Adopt when:

• Production is already on the Anomaly/Streams Platform (PyroCMS lineage) and you want admin-managed reusable rich content without building the CRUD, permissions, and stream schema yourself.
• Editors — not engineers — need to change shared copy (disclaimers, promos, global banners) routinely.
• Failure mode is tolerable: a missing or stale snippet degrades a page, it doesn't corrupt data or take down checkout.
• The team is PHP/Laravel-fluent enough to read the source and vendor-patch a dependency that isn't being actively maintained.

Look elsewhere when:

• You're on vanilla Laravel. The real dependency is the entire Streams addon system; pulling in a CMS to get a snippet table is a bad trade. A snippets table plus Filament/Nova/Twill is a day of work and you own the roadmap.
• You need versioning, draft/publish approval, scheduling, per-locale variants, or audit trails. Assume these are absent and will be your build.
• You need vendor support, an SLA, security responsiveness, or upgrade guarantees. Zero stars, zero dependents, zero ecosystem pull means you are the maintainer.
• Composer resolution conflicts with your current Laravel/PHP versions, or the module's last commit is well behind your framework baseline.
• A maintained alternative fits: Statamic, Twill, Filament block builders, or a headless CMS (Sanity, Storyblok, Contentful) if content velocity is the actual goal.

How to Pitch It (Stakeholders)

Executives: "The CMS platform we already run has a small add-on that lets marketing edit reusable content — banners, disclaimers, promo copy — directly, instead of filing engineering tickets. Because it plugs into infrastructure we've already paid for, integration is measured in hours, not a sprint. The trade-off is real: it's community code with no support contract and effectively no user base, so we own its upkeep. Recommendation: adopt it as an internal content tool, pin the version, and don't build product strategy on top of it. Revisit when we replatform."

Engineering: "It's a Streams Platform addon — a partials stream with the standard repository/entity pattern and admin CRUD, rendered into templates via a tag/plugin. No new infrastructure, no new datastore; the cost is a composer require, a migration, and permission wiring. The risk is maintenance: unmaintained upstream, so pin it and be ready to vendor-fork. Keep the coupling at the presentation layer — put a thin interface in front of it so swapping to a Filament resource or headless CMS later is a contained change, not a refactor."