Document toolboxDocument toolbox

Environment Architecture

Within the Contentful Enterprise, there are 3 different environmental architectures that need to be understood:

  1. Global Client Directory

  2. Client Catalog

  3. Web App

Global Client Directory

The Global Client Directory has a simplistic architecture as it is owned by 14West and will not be cloned across client spaces. The Global Client Directory will have the following environments:

  • Dev - This is the space where the devs will be making their working changes to the Apps and Content Model

  • UAT - Once the work has been finalized in dev, the changes will be deployed to UAT where the product team can conduct testing.

  • Master - This is our production environment where all changes will be deployed to upon approval. Additionally, this is the environment that the Client Catalog and Web App will reference for certain content

 

Client Catalog

The Client Catalog is a bit more unique in that there is a 14West space and separate spaces for each client.

The 14West Space

The 14West space is controlling the content model that each individual client spaces have to follow, as this model is critical for the 14W back-office business functions. The 14West space has the following environments:

  • Dev - This is the space where the devs will be making their working changes to the Apps and Content Model

  • UAT - Once the work has been finalized in dev, the changes will be deployed to UAT where the product team can conduct testing.

  • Master - This is our production environment where all changes will be deployed to upon approval. Once in Master, the content model will be pushed to the Client Spaces Master Environment as well.

 

The Clients Spaces

The Client spaces is where they will setup their business information, such as the items, people, franchise, etc. The information entered here is important for the back-office business functions and therefore the validation is controlled by the 14West Space. The Client Spaces have the following environments:

  • Sandbox - This is the environment where the clients can conduct their own testing of new workflows, procedures, and custom apps. The client will be responsible for cloning their Master environment to the Sandbox environment when they need/want to.

  • Master - This is the environment where the clients will enter in their business information such as the items, people, franchise, etc. This space will be used to reference their Web App when necessary

 

Web App

The Web App space is one of the more complicated architecture. The website is not critical for the 14W back-office business function and therefore it isn’t controlled by the 14West team. The 14West team will create and manage a Content Model that the clients can utilize if they wish; however, the clients can also elect to manage their own content model.

The 14West Space

The 14West space will be used as an example content model that clients can elect to utilize if they wish to. This space will have the following environments:

  • Dev - This is the space where the devs will be making their working changes to the Apps and Content Model

  • UAT - Once the work has been finalized in dev, the changes will be deployed to UAT where the product team can conduct testing.

  • Master - This is our production environment where all changes will be deployed to upon approval. Once in Master, the content model will be pushed to the Client Spaces ‘Reference Model’ environment.

Client Spaces

The client spaces will be managed by the clients, including the environments, content model, and data. The information entered here will be used to run their website and other business functions that are managed by the 14West team. Since the client will manage the environments, below is just a suggested setup they should follow.

  • Dev - This is the space where the devs will be making their working changes to the Apps and Content Model

  • UAT - Once the work has been finalized in dev, the changes will be deployed to UAT where the product team can conduct testing.

  • Master - This is our production environment where all changes will be deployed to upon approval.

  • Reference Model - This is the environment where the 14West team will push the sample Content Model when changes are made. The client will be able to review and determine if they want to migrate that content to their Dev, UAT, or Master environments for utilization.

 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html-macro' is unknown.