Key takeaway: If your team ships Laravel and wants a marketing or docs site without adding a JavaScript build culture to the company, Jigsaw is a reasonable and pleasingly boring choice. Blade templates and PHP helpers mean day-one productivity from people you already employ. Outside a Laravel shop there is no argument for it over Astro or Eleventy.
Quick facts
- LanguagePHP
- CategoryPHP
- LicenseMIT
- Created2017
- GitHub stars2.5k
- Statusactive
Templating: Blade Markdown
What it is
Jigsaw is a Laravel-flavoured SSG by Tighten. Blade templates, PHP toolchain. Useful for Laravel teams who want a static marketing site with familiar tooling.
Best for
- Laravel teams shipping marketing or docs sites
- PHP shops that want to stay in the PHP toolchain
When not to pick it
For non-Laravel teams pick a JS-based SSG with a bigger ecosystem.
My take
Right tool for Laravel teams; niche otherwise.
Blade templates producing static HTML
Jigsaw gives Laravel developers the templating they already use and outputs plain HTML files. Collections are folders of Markdown with front matter, mapped to templates and permalinks in a config file, which covers blogs, docs, and any list-and-detail shape without ceremony. The asset pipeline is the standard Laravel frontend tooling, so Tailwind and a bundler behave the way they do in the main application. The practical win is shared vocabulary: your developers write layouts and partials the same way in both codebases, design decisions stay consistent without anyone learning a second syntax, and the deployment target is a static bucket with no PHP runtime in production. For a team with PHP developers and no JavaScript specialists, that alignment is worth more than a feature comparison suggests it should be.
The ceiling arrives sooner than you expect
Jigsaw is maintained by an agency alongside its client work, and the cadence reflects that: stable rather than growing. There is no image pipeline, so responsive images and modern formats are your problem to solve. There is no component hydration model, so interactivity is scripts you attach by hand. Translation, structured content at scale, and any kind of content-collection type safety are all things you build yourself. The plugin and theme ecosystem is small enough that you should assume nothing exists for your specific requirement. For a fifty-page marketing site none of that matters. For a content operation that keeps growing, the accumulated do-it-yourself work overtakes the familiarity benefit, and Astro's built-in image handling and content collections start looking cheaper even after the language switch.
Frequently asked questions
Does Jigsaw need PHP on the server?
No. Jigsaw runs PHP at build time and outputs static HTML, CSS, and JavaScript, so the production host can be any static file host or CDN. You need PHP and Composer in your development environment and in CI, but nothing PHP-related has to exist in production at all.
Jigsaw or Astro?
Jigsaw if your team is Laravel-first and the site is a straightforward marketing or docs build you want shipped in familiar tooling. Astro if the site will grow, needs proper image handling, wants component islands, or will be maintained by people who are not PHP developers. Capability favours Astro; team fit often favours Jigsaw.
Is Jigsaw good for documentation?
It handles a docs site adequately through collections and Blade layouts, but you build search, versioning, and the page tree yourself. If documentation is the primary job rather than a section of a marketing site, a purpose-built docs tool saves weeks. Jigsaw is at its best on marketing pages next to a Laravel application.
Links
Similar tools you should also consider
If Jigsaw is your pick, the next conversation is short
The 30-min call is where your project gets a real architecture, an SEO transport plan, and a price range you can take to your team. Describe your site, your timeline, your existing content. I tell you whether Jigsaw is genuinely the right call for you, and what the build actually looks like.