Spintax Laravel Package

Product Decisions This Supports

• Feature enablement (content variation): Unlocks lightweight "spintax" templating — the {Hello|Hi|Hey} pattern — for personalized email greetings, subject-line rotation, marketing copy variants, and notification text. This is the core product feature the package directly de-risks.
• Build vs. buy: Strongly favors buy (or vendor) over build for teams on Laravel/PHP. The parsing logic — including nested expression handling — is small but fiddly (recursion, delimiter edge cases, escaping), and this package already covers it under MIT. The realistic alternative is often "build a ~50–100 line parser," so the decision is low-stakes either way; the package merely saves a sprint of yak-shaving.
• Roadmap input: Sits in the "content generation / personalization" bucket. If your roadmap includes dynamic content, drip campaigns, or randomized test fixtures, this is a cheap primitive to layer on — but it is not a templating engine, so don't roadmap Blade/Twig-level feature ambitions onto it.
• Use cases to validate: (1) email marketing personalization, (2) generating varied seed data and test fixtures, (3) A/B copy rotation, (4) anti-spam-avoidance text variation.
• Risk posture: Near-zero dependency footprint, framework-agnostic, optional Laravel service provider/facade for clean wiring. Low adoption (8 stars, 0 dependents) means you should treat it as vendorable source rather than a critical live dependency.

When to Consider This Package

Adopt when:

• You're already in the Laravel/PHP ecosystem and want drop-in spintax parsing with an optional facade.
• You need nested spintax ({Hi|Hello {friend|there}}) and don't want to hand-roll recursion.
• The feature is a utility, not a core product surface — content variation, fixtures, or copy rotation.
• You're comfortable pinning a version and, if needed, forking the source, given the 2022 last release.

Look elsewhere when:

• Your stack isn't PHP (port the trivial logic to your language rather than fight it).
• You actually need a templating engine (conditional logic, loops, escaping, i18n) — reach for Blade, Twig, or Handlebars instead.
• You need deterministic/seeded output for reproducible tests or compliance — verify the random selection is seedable, or wrap it yourself.
• Your requirements are production-critical and you need an actively maintained dependency with a support commitment. Here, the maintenance signal is weak (single maintainer, infrequent releases, low adoption), so plan for vendoring.
• You need security-sensitive or high-volume parsing where escaping/DoS characteristics matter and would require audit.

How to Pitch It (Stakeholders)

To executives: This is a tiny, MIT-licensed utility that lets us add content-personalization features (varied greetings, rotating subject lines, A/B copy) without building a parser ourselves. Cost is effectively zero, risk is low because we can vendor the source into our codebase. It's a tactical accelerator, not a strategic bet — no vendor lock-in, no license exposure.

To engineering: It's a small, framework-agnostic PHP library with an optional Laravel service provider and facade. It parses nested {a|b|c} spintax and returns a random variation — clean to integrate, minimal surface area. Caveat: last release was mid-2022 and adoption is minimal, so treat it as vendorable source: pin the version, write a thin wrapper around the API so we can swap or fork it, and add tests around the nested/edge cases. If we'd rather not own a third-party dependency for ~100 lines of logic, porting the parser in-house is a reasonable alternative.