Edit Your LaraDocs Site from the Statamic Control Panel with Sidecar
Statamic's new Sidecar package ships with a first-party LaraDocs driver. Your Markdown stays in Git, your writers get a proper editor, and nothing about your deployment changes.
Last week the Statamic team announced Sidecar, an experimental package that lets you manage Markdown-based sites from the Statamic Control Panel without migrating a single file. LaraDocs is one of the four static site generators it supports out of the box, alongside Jigsaw, VitePress and HydePHP.
I'm chuffed about this one, so here's what it means if you run a LaraDocs site.
The problem it solves
LaraDocs was built for developers. Docs live as Markdown files in your repo, front-matter controls titles and ordering, folders define the structure, and changes ship through the same pull requests as everything else. That's the whole point, and I'm not changing it.
But every docs site eventually hits the moment where someone who isn't a developer needs to fix a typo, rewrite a confusing paragraph, or add a page. Support teams, technical writers, product people, the customer who spotted the mistake. Up to now the answer has been "send it to a developer and they'll sort it", which works right up until it doesn't.
Sidecar is the third option. Your files stay exactly where they are and LaraDocs keeps rendering them exactly as it does today. Statamic just rides alongside and gives non-developers a nice interface to edit through.
What you get
Install Sidecar next to your LaraDocs app and the Control Panel picks up your docs directory as a content source. From there you get:
- A real editor for every page, with the body and front-matter fields laid out as a proper publish form rather than a raw text file.
- A drag-and-drop content tree that mirrors your folder structure. Moving a page in the tree moves the file and updates
order:for you. - Live Preview rendered through LaraDocs itself, so what you see in the panel is what ships.
- Customisable blueprints if you want to expose fields like
badge,group,hiddenorupdated_atas dropdowns and toggles instead of asking people to remember the YAML. Nothing gets imported into Statamic collections. There's no second copy of your content, no sync job, no webhook glue. Sidecar reads the LaraDocs tree straight from disk and writes changes back as ordinary Markdown with ordinary front-matter.git diffwill show you exactly what your writer did.
How the LaraDocs driver works
Sidecar uses drivers to handle the fact that every generator organises content differently. The LaraDocs driver knows that:
- Folders are sections and nested folders are nested sections.
order:in front-matter drives sort position, andgroup:buckets pages into tabs and sidebar headings.hidden: truekeeps a page out of navigation while leaving the URL live.- Slugs come from filenames unless
slug:overrides them. So when someone reorders pages in the tree, the driver rewritesorder:values rather than inventing a parallel structure. When they rename a page, the file moves. Everything Sidecar does is expressible as a change LaraDocs already understands, which is exactly why the site keeps working without you touching anything.
Unknown front-matter keys are preserved too, so any custom metadata you're reading via $document->metadata->get() survives a round trip through the editor.
Trying it out
Because a LaraDocs site is already a Laravel app, install is two commands:
composer require statamic/cms statamic/sidecar
php please install:sidecar
The installer detects LaraDocs, sets up the driver, and points it at your docs directory. Sign in to the Control Panel and your docs are there.
A few honest caveats
Sidecar is explicitly experimental. Statamic have been upfront that the APIs and on-disk behaviour may change, and that they haven't stress-tested it against large real-world sites yet. A few things I'd suggest:
- Do it on a branch. Point Sidecar at a checkout, let your writers edit, review the diff before it hits
main. You get the editing experience without giving up code review. - Keep an eye on ordering. Reordering in the tree rewrites
order:across the affected files. That's correct, but the diff can be wider than you'd expect from "I moved one page". - Report the weird stuff. If your LaraDocs setup does something the driver didn't anticipate, open an issue on the Sidecar repo and tag me. I'd like the LaraDocs driver to be the one that just works.
Why I think this matters
I don't want LaraDocs to become a CMS. Files in Git, rendered by Laravel, deployed however you deploy the rest of your app: that's the design and it's staying. What I do want is for the people who aren't developers to stop being blocked by that decision.
Sidecar gets there without compromising either side. Developers keep their workflow, writers get an editor, and the source of truth is still a folder of Markdown you can cat. That's a good outcome and I'm glad Statamic built it.
Go and take it for a ride. Let me know how it goes.