A content project contains the deploy configuration and the downloaded ArcGIS Enterprise content.

The following item types are officially supported:

• Webmaps
• Webapps
• Dashboards

The following item types are not fully supported and deploying these items might fail in some cases:

• Experiences
• Story maps

Binary files are not supported and cannot be included in a content project:

• Zip files
• Service Definition Files
• Micrsoft Office files
• Images

Create a content project

Open ArcGIS Pro, open a project and navigate to the Add-In Section of the Ribbon. Click Create New Content Project

1. Enter the path for the deploy configuration JSON file. The parent directory of this file will be used to save the content files to as well.
2. Click browse items to select the Portal Content Items you want to include in the project. The browse window doesn't show all types of content, Web Mapping Applications are not supported by the browse window of ArcGIS Pro. When the item is not visible in the browse window:
   1. Open a browser and navigate to your portal
   2. Navigate to the item
   3. Copy the item id from the address bar: https://your.portal.com/portal/home/item.html?id=**990c3dba96884f6aac3c989e7ec9b25f**
   4. Paste the item id in the text box and Click Add ItemID
3. When one or more items are selected from your portal, the Environment registry from the current portal will be loaded. This will populate the Environments table
4. Configure each environment
   1. 🔒 will add delete protection to all selected items
   2. ✔️ will mark the items as authoritative
   3. 🏢 will share the items with your organization
   4. 🌎 will share the items to anonymous users. This checkbox is disabled when the current portal is configured to block sharing with anonymous users.
   5. Enter the group names when the items should be shared with one or more groups (optional)
   6. Enter the portal folder (optional)
5. Select the source environment from the dropdown menu
6. Select 'Overwrite existing unregistered items with the same ItemID' when you want to overwrite the existing content in one or more target portals where the content already has been deployed in another way to these portals. When unchecked and content with the same ID exists on a portal, GaiaBuilder will deploy the content with a different ItemID and leave the existing content as is.
7. Optionally, configure the Rewrite Item ID's. These items will not be downloaded locally, but they will be updated using the GaiaBuilder Item Registry.
8. Click Import

The deploy configuration file and JSON are stored on disk. Next steps:

1. Finetune the deploy configuration JSON to optimize your deployment
2. Commit the content to a GIT repository
3. Update the content from your Development Environment
4. Deploy the content to Test, Acceptance or Production

More informtion

More information on how URL's, ItemID's and other texts are updated during the deploy process can be found under JSON rewrite

Vertigis Server workflows

Vertigis Server workflows have limited support. By default the server workflows are stored on the Vertigis Workflow Server and not in the Portal. Saving the workflow temporarily as a client workflow makes it possible to apply version control and deploy the workflow to ArcGIS Enterprise. After deploying, creating the content project and updating the content, the workflow must be switched to a Server Workflow manually.

• Don't store credentials in the Server Workflow when deploying them with GaiaBuilder, because the credentials might be exposed to third parties via GIT, log files etc.
• Make a separate content project for each Server Workflow. This makes it possible to deploy the other content parts of the application without the manual switch to server workflow step