Jekyll Provider Bundle Laravel Package

Product Decisions This Supports

• Content Strategy Expansion: Enables seamless integration of Jekyll-based static site generation into a Laravel ecosystem, allowing teams to leverage Jekyll’s simplicity for blogs, documentation, or marketing sites while maintaining a unified backend.
• Build vs. Buy: Justifies a "buy" decision for teams already using Bloghoven (or similar headless CMS solutions) and needing Jekyll compatibility without reinventing static site generation from scratch.
• Roadmap Alignment: Supports a phased migration strategy—e.g., migrating legacy Jekyll sites to a Laravel-powered CMS while preserving existing workflows (e.g., Markdown editing, Git-based publishing).
• Developer Experience (DX): Reduces friction for teams familiar with Jekyll by providing a native Laravel integration, avoiding context-switching between tools (e.g., Jekyll CLI + custom scripts).
• Use Cases:
  • Internal Documentation: Teams using Laravel for apps but Jekyll for docs can consolidate tooling.
  • Multi-Channel Publishing: Sync content between a Laravel-driven web app and a Jekyll-powered blog without manual exports.
  • Static Site Hosting: Offload static content (e.g., blogs) to Jekyll while keeping dynamic features in Laravel.

When to Consider This Package

• Adopt if:
  • Your team uses Bloghoven (or a similar Symfony/Laravel CMS) and needs Jekyll integration for static sites.
  • You prioritize Markdown-based workflows and want to avoid rebuilding Jekyll’s tooling in PHP.
  • Your roadmap includes unifying content management across dynamic (Laravel) and static (Jekyll) assets.
  • You’re evaluating headless CMS options and want to test Jekyll’s compatibility with Laravel before committing to a full rewrite.
• Look Elsewhere if:
  • You’re not using Bloghoven/Symfony: This bundle is tightly coupled to Bloghoven’s architecture. For vanilla Laravel, consider alternatives like:
    • spatie/laravel-static-site-generator (PHP-native static site generation).
    • Jekyll API + custom Laravel service (for decoupled workflows).
  • You need advanced Jekyll features (e.g., plugins, complex liquid templating) that this bundle doesn’t expose.
  • Your team lacks Symfony/Laravel familiarity: The bundle assumes familiarity with Symfony bundles and dependency injection.
  • You’re building a high-traffic static site: Jekyll’s performance may outpace this bundle’s abstraction layer for large-scale use.

How to Pitch It (Stakeholders)

For Executives:

"This bundle lets us integrate Jekyll’s simplicity into our Laravel stack without rewriting our static site generation from scratch. For teams managing blogs or docs in Jekyll today, it’s a low-risk way to modernize our tech stack—reducing tooling fragmentation while keeping our content workflows intact. It’s a ‘buy’ decision that aligns with our headless CMS strategy and cuts dev time for static content."

Key Ask:

• Approval to pilot the bundle for a non-critical Jekyll site (e.g., internal docs or a blog).
• Budget for minor customization if the bundle lacks critical features (e.g., plugin support).

For Engineering:

*"This is a Symfony bundle for Bloghoven that bridges Jekyll and Laravel. Here’s how it works:

• What it does:
  • Generates static sites from Jekyll templates within a Laravel/Bloghoven project.
  • Handles Markdown-to-HTML conversion, asset pipelines, and Jekyll’s front matter (metadata).
  • Integrates with Bloghoven’s content model (e.g., syncing posts between dynamic and static sites).
• Why use it:
  • Avoids context-switching: No need to manage Jekyll CLI separately.
  • Leverages existing tooling: Uses Laravel’s service container and Bloghoven’s content API.
  • Future-proof: If we migrate from Jekyll later, the bundle’s abstraction layer makes it easier to swap implementations.
• Trade-offs:
  • Limited to Bloghoven: Not useful for vanilla Laravel projects.
  • Early-stage: Only 2 stars; expect to contribute fixes or extend functionality (e.g., plugin support).
  • Performance: Jekyll’s Ruby runtime may add overhead compared to PHP-native static generators.

Proposed Next Steps:

1. Spike: Test the bundle on a throwaway Jekyll site to validate integration with our Bloghoven setup.
2. Gap Analysis: Document missing features (e.g., custom Jekyll plugins) and prioritize them for custom development.
3. Pilot: Deploy to a low-risk static site (e.g., docs) to measure DX improvements."*

Key Ask:

• Time to evaluate the bundle in a spike (1–2 dev days).
• Clarity on whether the team will maintain/extend the bundle or treat it as a temporary solution.