As we've explained in the previous page, your Admin panel's layouts configurations are saved on Forest Admin servers. As a result, you can't version them. But don't worry, we've got you covered with some great tools!
The notion of a branch cannot be explained without first explaining what a layout is.
A layout is all the configuration that define your user interface (UI). In Forest Admin, there is 1 layout per environment and per team:
A Branch is a fork (i.e. copy) of the layout of the Environment it is attached to. A Branch can only be created in your own Development Environment.
The origin of a branch is either specified using the
--originoption or selected when prompted otherwise). You should choose the environment you want to make some layout changes on.
Once you've created a Branch, your layout will look exactly like the layout of its origin Environment.
Imagine the following situation where you have 3 Environments:
This also means that any changes made to the origin of your Branch will instantly reflect on your Branch.
For those familiar with git's rebase, this means you will never have to rebase your Branch on its origin, as it is done automatically.
forest branch my-branch --origin production
Using kebab-case is recommended. However, if you prefer to use spaces in your Branch names, don't forget to surround them with quotes, like so
forest branch "my branch" --origin production.
On your interface, you can check at all times what is your current Branch and how many layout changes were made on it. These information appear in the top banner of your admin panel. The "branches pushed" information is only relevant for Remote Environments: it shows how many Branches were already pushed onto it.
Your current Branch will be displayed at the top.
Now that you've mastered Branch creation and management, let's dive into the next step of the development workflow: deployment.