Branch-specific Modules

These modules are specific to a branch. When you fork out a branch out of the main branch, you’ll get all the contents of the main branch within this child branch. But once you start making changes within these modules of the child branch, it will reflect only within that particular branch.

When working within specific branches, content types added or updated will be specific to that particular branch.

For example, if you create a new sample content type within the development branch, you will be able to retrieve or access this sample content type only within the development branch.

Global fields added or updated will be specific to a particular branch.

For example, if you create a SEO global field within the development branch, you will be able to use or access this global field only within the development branch.

You can create, update, delete and refer entries only within specific branches of your stack.

For example, if you create an entry within the blog content type of the development branch, you will be able to use or access this entry only within the development branch.

You can add or update assets only within specific branches of your stack. The assets added within any other branch other than the main branch, will contain the branch name in the URL.

For example, the URL for the assets added in the development branch will be as follows: https://images.contentstack.com/v3/assets/blt0000000/blt9c00000000/6748939030339888/AI.jpg?branch=development

For all assets added to the main branch, the URL will be as follows: https://images.contentstack.com/v3/assets/blt0000000/blt9c00000000/6748939030339888/AI.jpg

The system allows the creation of branch-specific workflows, i.e., more than one workflow for the same content type across various branches. For instance, you can set up distinct workflows under the “Main” and “Dev” branches.

You will be able to view publish queues specific to a branch.

For example, if you are working within the development branch, you view the publishing details specific only to the development branch.

You can create releases only within specific branches of your stack.

For example, if you create a release within the development branch, you will be able to access this release only within the development branch.

Any language that you add or create within a branch will be available only in that specific branch.

For example, you are working within the development branch, and you add new languages such as German and Chinese to this branch. These languages will be available only within the development branch.

You can add experience extensions specific to a branch.

For example, you are working within the development branch, and you add new extensions (Custom Fields, Sidebar Extensions, and Dashboard Extensions) to this branch. These extensions will be available only within the development branch.

You will be able to view audit logs specific to a branch.

For example, if you are working within the development branch, you will receive audit logs specific only to the development branch.

Retrieves searched content types, entries, assets, etc. only from the branch you are currently working in.

For example, if you have a home content type within the development branch, you will be able to search for that content type only in the development branch.

You can create different sets of labels for different branches of your stack. This means that labels you create within the development branch can be applied only to content types within that branch.