When you publish, Splitleaf uses GitHub and real Git version control. Each publish creates a Git commit in your site's repository.
You choose exactly which changes to publish. Splitleaf leaves the rest for later, and you can view publish history or safely roll back changes that you have not published yet.
What you need
- A GitHub connection for the site. See Connect GitHub.
- A hosting choice: Vercel or manual hosting.
- A Splitleaf publish license. The license is personal: one payment, no subscription.
You can design, edit, and save without a license. You need it only to publish.
Choose your hosting
- Vercel (recommended): Splitleaf creates the site on Vercel and uploads the files. Domains and live status appear in Splitleaf.
- Manual hosting: Splitleaf sends the site to GitHub. You put the built site on your own server.
Publish
- Click Publish in the top bar.
- Review the list of changes.
- Uncheck anything you want to publish later.
- Click Publish.
- Follow the progress steps: Testing connection, Preparing files, Saving changes, Uploading, Deploying, Live.
- Wait until the list shows Live.
Publish part of your changes
Use Select all or Clear all to manage the check marks. Unchecked changes stay safe in the app and can be published later.
Discarding a change is different: it returns to your last publish and cannot be undone. Changes made outside the Designer, such as replacing an asset or editing a file on your computer, also appear in the change list.
When a teammate also made changes
Splitleaf gets your teammates' latest published changes before it builds. If you changed the same item, choose Keep mine or Use theirs for each conflict.