Laravel Export Laravel Package

Product Decisions This Supports

• Static publishing as a feature: Enables a Laravel app to emit a deployable static bundle via php artisan export, useful for blogs, marketing pages, documentation, landing pages, programmatic SEO pages, and public content that does not need per-request server rendering.
• Build vs. buy: Strong candidate for buying a narrow capability instead of building an in-house crawler/exporter. The package already handles crawling, explicit paths, asset inclusion, disk targets, shell hooks, streaming for larger sites, and redirect export. A PM should still validate fit because external adoption signals are thin (0 listed dependents; low opportunity score).
• Architecture and hosting roadmap: Supports a “dynamic admin, static delivery” model: manage content in Laravel/Nova/Filament/Wink/Sharp, then publish to Netlify, S3, CloudFront, GitHub Pages, or similar. This can reduce hosting cost, simplify scaling, and reduce runtime attack surface.
• Content freeze and compliance use cases: Useful for archival snapshots, legal/regulatory content freezes, demo builds, and preview bundles where a stable HTML artifact is more valuable than a live server.
• Packaging and monetization decisions: If the product serves Laravel teams, static export can become a premium add-on or managed deployment capability. It may justify pricing around “publish anywhere,” preview environments, or lower infrastructure cost rather than around raw rendering.
• Prioritization signal: High leverage when the target user already has Laravel skills and mostly public content. Low priority when the roadmap depends on personalization, authentication, real-time data, or incremental rendering.

When to Consider This Package

• Consider it when: the team already runs Laravel; content is mostly public and cacheable; an admin panel is the source of truth; static hosting is acceptable; the deploy path is CI/cron-driven; assets live in public; and the team wants one-command exports with optional before/after hooks for builds and deployments.
• Consider it for large sites only with validation: enable streaming and test crawl coverage, memory use, and export duration. Crawl-based export can be fragile if routes are not export-safe or if internal linking is incomplete.
• Look elsewhere when: the product needs personalized or authenticated pages, real-time data, incremental/static regeneration, complex client-side routing, integrated image optimization, or edge SSR. Dedicated SSGs or hybrid frameworks may fit better.
• Look elsewhere when: the team lacks Laravel expertise, needs commercial SLA support, or requires deep CDN invalidation and asset-pipeline integration beyond shell hooks.
• Treat as tactical until proven: the package is MIT-licensed and Spatie-maintained with changelog/release maturity, including Laravel 13 compatibility, but 0 listed dependents and a low opportunity score mean a PM should time-box a spike before making it a core platform dependency.
• Avoid crawling non-idempotent GET routes: export mode should be detectable via the X-Laravel-Export header and routes should be audited for side effects before enabling crawl.

How to Pitch It (Stakeholders)

• To executives: This lets us reuse our Laravel and admin investments while publishing static sites that are faster, cheaper to host, simpler to scale, and smaller in attack surface. It is MIT-licensed, requires no new platform license, and can be validated with a short spike before committing roadmap capacity.
• To engineering: Adoption is low-friction: install via Composer, run php artisan export, configure crawl or explicit paths, point the export disk at local/S3 storage, and use hooks to build assets and deploy. The Exporter class allows programmatic configuration, and streaming supports larger crawls.
• To both: The main caveats are static-only limitations, crawl completeness, lack of incremental builds, and weak external adoption evidence. Recommend a time-boxed proof of concept covering export coverage, deploy pipeline, security review, and fallback plan before treating it as strategic infrastructure.