Version Control

Version Control allows you to work on changes in isolation using branches, then merge them back when ready. Track what's changed, discard unwanted edits, and safely experiment without affecting your main project.

Overview

Stellify's version control system works similarly to Git. Your project has a main branch that contains your stable content. You can create feature branches to work on changes without affecting the main branch. When you're ready, you can view a diff of your changes and merge them back.

Getting Started

Creating a Branch

To start working on changes in isolation:

1. Open the branch selector in the editor toolbar
2. Click "Create Branch" and enter a descriptive name
3. Your new branch is now active - all edits will be saved to this branch

Switching Branches

Use the branch selector to switch between branches at any time. When you switch:

• Elements, routes, files, and other content will update to show that branch's version
• Items you haven't modified on the branch will show the main branch version

How It Works

Copy-on-Write

When you edit something on a feature branch, Stellify creates a copy of that item just for your branch. This means:

• Efficient storage - Only changed items are duplicated
• Clean separation - Your changes don't affect main until you merge
• Easy rollback - Discard changes to revert to the main version

What Gets Versioned

All major content types are versioned:

• Elements - HTML elements, components, and their properties
• Routes - Page routes and their configurations
• Files - Code files (JavaScript, CSS, etc.)
• Methods - Server-side methods and logic
• Components - Reusable component definitions

Viewing Changes

Before merging, you can view a diff showing all changes between your branch and main:

• Added - New items created on your branch
• Modified - Existing items you've changed, with field-level details

The diff summary shows how many changes by type (elements, routes, etc.) to help you understand the scope of your changes.

Merging Changes

When you're ready to apply your changes to main:

1. Review the diff to confirm your changes
2. Back up your project - Consider exporting before merging
3. Click "Merge to Main"
4. Your branch changes overwrite the main versions
5. You're automatically switched to the main branch

Discarding Changes

Discard Single Item

Changed something you don't want to keep? You can discard changes for individual items:

• The branch copy is deleted
• The item reverts to the main branch version

Discard All Changes

To reset your entire branch and start fresh, use "Discard All Changes". This removes all branch-specific copies, reverting everything to main.

Subscription Requirements

Version control features require an active subscription:

• Free users - Can create and switch branches
• Subscribers - Full access to diff, merge, and discard features

Merge History

Stellify keeps a record of all merges performed on your project. You can view merge history to see:

• Which branch was merged and when
• Who performed the merge
• A summary of what was changed (how many elements, routes, etc.)

This audit trail helps you track changes over time and understand how your project has evolved.

Best Practices

• Use descriptive branch names - "add-contact-form" is better than "branch-1"
• Review before merging - Always check the diff to confirm your changes
• Back up before merging - Export your project before merging important changes
• Keep branches focused - One feature or fix per branch makes changes easier to track
• Merge regularly - Don't let branches diverge too far from main