...
The below image shows how the folders are structured in the organization’s Git repository. The folders with black text are the folders that can be updated with custom content.
...
EmpowerID — – This is the root installation folder. (Note that this folder should not be the root of the source control).
EmpowerID.Web.Overrides and EmpowerID.Web.CDN/Overrides — – These folders are where Web customizations, such as .CSHTML pages and CSS files, are saved.
WFS/_assemblies — – This folder contains compiled custom Workflow Studio items.
WFS/<Customizations> — – This folder stores any custom Workflow Studio design items, such as new workflows, forms, connectors, etc., as well as any modifications made to stock EmpowerID Product items. Note that stock EmpowerID product items should first be copied to this folder and then modified. The folder can be renamed to reflect the organization. For example, if you belong to organization “Foo,” the folder can be renamed to “Foo.”
...
Notice that Steve’s and Heidi’s development clouds remain separate , but share a common dev environment. This allows them to review and validate each other’s work if needed. Once a developer has their feature at a mature enough stage, they can push their work to a designated branch on the Git repository. This automatically kicks off the build process.
...