Microsite Bundle Laravel Package

Product Decisions This Supports

• Microsite Strategy: Enables rapid deployment of standalone, self-contained websites (e.g., marketing campaigns, regional hubs, or product-specific landing pages) without duplicating full infrastructure.
• Symfony Ecosystem Alignment: Leverages existing Symfony bundles (e.g., atoolo/resource-bundle, atoolo/rewrite-bundle) to reduce integration friction for teams already using the framework.
• Build vs. Buy: Avoids reinventing URL routing, security, and resource isolation logic for microsites, accelerating time-to-market.
• Use Cases:
  • Marketing Teams: Deploy campaign-specific microsites (e.g., /summer-sale) with custom templates/CMS content.
  • Regionalization: Serve localized content (e.g., /eu, /us) with shared backend services.
  • A/B Testing: Isolate variants (e.g., /variant-a, /variant-b) for analytics without full app duplication.
  • Legacy Migration: Gradually migrate monolithic features into microsites while maintaining a unified auth/security layer via atoolo/security-bundle.

When to Consider This Package

Adopt if:

• Your team uses Symfony 6.3+ or 7.x and needs lightweight microsite support without full microservice architecture.
• You require URL-based isolation (e.g., /brand-x) with shared backend services (e.g., auth, database).
• Your microsites share templates, assets, or CMS backends but need independent routing/rewrites.
• You prioritize developer velocity over custom solutions (e.g., no need for Kubernetes or separate domains).

Look elsewhere if:

• You need full microservice independence (separate databases, APIs, or domains).
• Your stack is non-Symfony (e.g., Laravel, Node.js, or static site generators).
• You require multi-tenancy with dynamic subdomains (e.g., brand-x.yourdomain.com).
• Your team lacks Symfony expertise or prefers headless CMS integrations (e.g., Strapi, Contentful) over bundle-based solutions.
• You need advanced SEO controls (e.g., canonical URLs, hreflang) beyond path-based routing.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us launch standalone microsites (e.g., /summer-sale, /eu-launch) in days, not months, by reusing our existing Symfony backend. It’s like creating a ‘lightweight website’ within our app—no extra servers, no duplicate code—just a clean URL path. For example, our marketing team could run a Black Friday campaign without IT overhead, while our dev team avoids context-switching between monolith and microservices. The MIT license and active maintenance (latest release Oct 2025) make it a low-risk bet."

For Engineering: *"The atoolo/microsite-bundle solves three key pain points:

1. Routing: Automatically rewrites /microsite/* to a dedicated template/controller while preserving shared auth (via atoolo/security-bundle).
2. Isolation: Each microsite gets its own YAML config (e.g., microsites.yaml) for templates, assets, and rewrite rules—no global app changes.
3. Integration: Works with our existing resource-bundle for CMS content and rewrite-bundle for clean URLs (e.g., /products → /microsite/products). Tradeoff: It’s Symfony-only, but if we’re already using Symfony, this cuts microsite dev time by 70% compared to building from scratch. The bundle’s maturity (PHPStan level 9, E2E tests) and dependency on atoolo/* bundles suggests it’s battle-tested internally at Sitepark."*

For Product/Design: *"Imagine launching a microsite for a new product line without waiting for a full website rebuild. With this bundle:

• Design: Use the same templates as your main site but override specific sections (e.g., hero banner, CTA).
• Content: Manage microsite copy in the same CMS as your main site (via resource-bundle).
• Analytics: Track /microsite/* traffic separately in Google Analytics with minimal setup. Example: A ‘limited-edition’ microsite could live at /le-collection with its own styling, but share user accounts and checkout flows with the main app."*