Multisite Deployment Options

Agility provides lots of flexibility when it comes to multisite deployments. Depending on the nature of your organization, your branding, and your content itself, you have options for how you deploy your websites.

Multiple Page Management Sitemaps

Each Agility Instance has the capacity for multiple sitemaps. You can use each sitemap for a different website. Managing content for multiple sites using a single instance makes a lot of sense if you have the same content team working on all those properties and you want to share a majority of the content or assets between those sites. 

Some organizations utilize multiple Page Management Sitemaps in Agility to separate their sub-brands or microsites. They can easily reuse content and assets from the primary site on the additional sites.

Multiple Instances

Agility allows you to manage multiple instances that are completely separate from each other in terms of the content, assets and editor team. In a multi-instance scenario, organizations can maintain a one-to-one ratio between an instance and a website. The security and workflow for each instance can be completely different from the next.  

In many cases, it makes sense to have multiple instances where there is also a primary instance that acts as the Content Hub for all content that's shared everywhere. You can read more about how to build a Content Hub here.

Choosing between Multiple Sitemaps and Instances

Here's a simple guide to choosing whether you should be using a single instance with multiple sitemaps or multiple instances to manage content for more than one website.

Single-Instance, Multi-Sitemap

  • You have a single content team, and the content is very similar across all your sites.
  • You have many similar websites with slightly different branding.
  • You have many smaller microsites that pull content from a primary website.

When working with multiple sitemaps, you can use each sitemap for sub-domains of your website, or you can target completely separate domains. 

For example, if you are using subdomains:

  • Sitemap 1 => mysite.com
  • Sitemap 2 => subdomain1.mysite.com
  • Sitemap 3 => subdomain2.mysite.com

If you want to setup completely separate domains:

  • Sitemap 1 => mysite.com
  • Sitemap 2 => anothersite.com
  • Sitemap 3 => mythirdsite.com

Configuring Sitemaps

In the screenshot below, you can see that this instance has been configured with 3 sitemaps, called Website, Documentation Site, and Members Site. Each sitemap has been pointed to its own deployments.

mceclip0.png

Using Multiple Sitemaps In Code

In your website projects, you can specify which sitemap you wish to use for your project.  For example, if you are using Next.js, you can specify which sitemap you wish to use in the project in the .env.local file.  In the code below, you can see the members sitemap is being used.

AGILITY_SITEMAP=members

 

To work with multiple sitemaps, you must be on the Pro Package or higher. 

 

Multi-Instance

  • You have separate teams or users to manage each website.
  • Each website has an entirely different brand, content, or assets.
  • Each website has a different workflow for managing content.

Having a hard time deciding which option is right for your organization? Talk to us!

1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.