LaraDocs 1.0 is Here π
We're stable, we're production-ready, and best of all, LaraDocs now generates your whole API reference straight from your routes.
Okay. Deep breath. β
LaraDocs is 1.0.0. Stable. Done. Production-ready. The real deal.
If you've been following along, you'll know it's been a ride. LaraDocs went from a scrappy little v0.1 to a full-featured docs platform in about a month. Search, multi-version docs, an MCP server, internationalisation, a deploy CLI⦠it all landed at a slightly ridiculous pace. And now it's grown up, put on a collared shirt, and shipped as 1.0.
Let me tell you what that actually means, and what's new.
So what does "1.0" actually mean?
Good question, because a version number on its own is just vibes. Here's the substance:
The public API is frozen. The facade, the core value objects (Document, DocumentTree, DocumentCollection, Tag and Metadata) and the contract interfaces are now a locked, documented surface under proper semver. Build on them, lean on the config, wire them into your deploy pipeline, and trust that a composer update inside the 1.x range won't pull the rug out from under you. No surprise breaking changes. That's the whole promise of a 1.0, and I don't make it lightly.
It's tested to within an inch of its life. 100% coverage gate (merging is blocked if coverage drops), PHPStan at max, Psalm at max, Pint keeping it tidy, and a full Playwright end-to-end suite driving a real browser. I sleep well.
It runs on modern kit. PHP 8.3+ (8.4 and 8.5 fully supported) and Laravel 11.14, 12, and 13.
Basically: it's ready for your actual, real, someone-is-paying-for-this application. Not "early-access, cross your fingers" ready. Ready ready.
The headline: native API docs, straight from your routes π§©
Okay, this is the one I've been dying to talk about.
LaraDocs now generates a full API reference from your Laravel routes, using a built-in, dependency-free generator. No third-party packages. No separate spec-writing chore. No hand-maintaining a Swagger file that's stale the second you merge. Just point the command at your app:
php artisan laradocs:openapi
That's it. The native generator is the default, and it needs nothing extra installed. It reads your routes, builds an OpenAPI spec, and LaraDocs renders it into proper API docs sitting right alongside your guides. Your endpoints, your parameters, your responses: documented, versioned, and searchable in the same site as everything else. All from the routes you've already written.
Let that sink in, because it kills the single most annoying thing about API documentation: drift. When your API reference is generated from the actual routes, lives next to the code, and ships in the same pull request, it physically can't wander out of sync with reality. No more docs that quietly lie to you three sprints later.
Already invested in Scramble? You're covered: set --driver=scramble (or LARADOCS_OPENAPI_DRIVER) and LaraDocs delegates to it, reusing the same route filters and config. Leave it on auto and LaraDocs uses Scramble when it's installed and the native generator when it isn't. But here's the thing I really want you to hear: you don't need Scramble, or anything else. Native works out of the box. Zero dependencies, zero config, real API docs.
For a package whose entire reason for existing is docs that live next to your code, generating your API reference the exact same way is the most on-brand thing I could possibly ship. π
Oh, and tabbed code blocks π
Small feature, disproportionate joy. You know those "npm / yarn / pnpm" tabs on the really nice docs sites? You can do that now. Just tag consecutive code blocks with tab:Label:
```bash tab:npm
npm install
```
```bash tab:pnpm
pnpm install
```
They group into one tidy tabbed block automatically. Need tabs around more than code (prose, callouts, images)? There's a :::tabs container for that too. Everything's keyboard-navigable and WCAG 2.1 AA compliant, tabs sync across the whole page by group name (pick pnpm once and every group follows), and your choice sticks between visits. Little thing. Feels great.
Look how far we've come
If you're new here (hi! π), here's what you get out of the box in 1.0:
- π Markdown β a polished docs site. Nested folders become navigation, dark mode, breadcrumbs, on-page TOC, the works.
- π Full-text βK search. Powered by Meilisearch, Typesense, or Algolia via Scout, with a zero-dependency JSON index as the fallback. Nothing extra to host if you don't want it.
- π€ Docs as an MCP server. Flip on
LARADOCS_MCP=trueand AI assistants can read your docs directly. - π Multi-version docs with semantic versioning, plus full i18n and a language switcher.
- π Mermaid diagrams, KaTeX maths, and Blade components right inside your markdown.
- π Automatic SEO. Meta tags, Open Graph & Twitter cards, JSON-LD, canonical URLs, auto-generated OG images,
sitemap.xml, and an RSS/Atom feed. - π₯οΈ A deploy CLI, built-in print styles, icons, configurable layoutsβ¦ I could keep going, but you get the idea.
All of that, stable, today.
Already using LaraDocs? Upgrading is easy
If you're on a 0.x release, first of all: thank you. Genuinely. You're the reason this got to 1.0. π
There are a few small breaking changes on the way to a frozen API, so I wrote you a proper 0.x β 1.0 migration guide. Follow it, run composer update, and you'll be on stable in a few minutes.
New here? Two commands in a Laravel app and you're live:
composer require petebishwhip/laradocs
php artisan laradocs:install
Then open /docs. That's it. Sidebar, search, dark mode: already there. No build step, no Node toolchain to babysit, no separate deploy target. Boom.
The full docs (built with LaraDocs, obviously) live at laradocs.dev/docs.
The bit where I ask nicely π
Here's the honest truth: LaraDocs is free, MIT-licensed, and built in the open by one developer (hi, still me π). It's crossed 5,000+ installs already, which is bananas and I love you all for it, but downloads don't pay for the Tea that fuels the releases.
If LaraDocs has saved you time, if it's made your docs something you're actually a bit proud of, please consider sponsoring the project on GitHub. Sponsorship is what keeps 1.0 from being the finish line and turns it into a starting one: more features, faster fixes, and a maintainer who can keep showing up. Any tier helps, truly. And if a sponsorship isn't your thing right now, a β on the repo genuinely moves the needle too.
What's next?
1.0 is a milestone, not a full stop. There's a hosted, managed version of LaraDocs cooking away π¨βπ³. Point us at your project, we handle publishing, custom domains, and updates the moment you save. Want to know the second it's ready? Pop your email into the box on the homepage. No spam, just the good stuff.
But for today? We're 1.0. We're stable. Go build something, document it beautifully, and enjoy it.
Thanks for being here. This one means a lot. π
Made with π (and a genuinely alarming amount of Tea) by Pete