Your site is not trapped in a closed document format. It is a folder of standard web files with config beside the code. If you leave Splitleaf tomorrow, the site still opens.
What you get
Real source code you can read, edit, and control. And that is supported nativly by all browsers
Site structure and settings live in the same file structure. Giving bot you and Agents all context needed easly make changes
Every publish is one commit to GitHub. History, versions and diffs comes native.
Duplicate or move your site anywhere, you can litteraly do it in your folder structure.
Today
If the only durable copy lives in a vendor database, you do not own the work. You rent a view of it.
Generating a page is easy. Maintaining it for years means the result must stay editable, reviewable, and movable.
Marketers want a visual path. Developers want a real repo. Splitleaf gives you both without the whole organisation having to use and understand Git.
How it shows up in the product
Pages, components, styles, and content collections live as ordinary files. Publish strips CMS markers and emits clean static HTML/CSS.
Site settings, SEO defaults, redirects, locales, and integration state travel with the project. Clone the repo and the project stays coherent.
Every publish is a real commit and push. Users see friendly change names. History remains auditable in the repository.
Git clone is the export button. No special migration dance to recover what you already built.
In practice
Install Splitleaf on your machine and sign up free, no credit card, ready in minutes.
Every feature is unlocked while you try it out, the designer, the CMS, the AI agent.
Click and connect with a few clicks to store the project in github, and puhblish it on your own domain with vercel.
Take the folder. Take the repo. Keep your host. Splitleaf was the tool, never the landlord of your source.
FAQ
No. Publish handles commits. Git stays infrastructure, not a daily skill requirement.
HTML, CSS, content files, and repo history. Published output is clean static HTML/CSS.
Yes. Because the project is files, technical teammates can inspect and change the same source when needed.
Move workspace ownership. The client receives the same repo and files.
Get a website that stays yours in formats the web already understands.