When to apply multisite or multi domain architecture for your Drupal CMS project

Should a SME want to manage and deploy multiple websites from one Drupal CMS installation — preferably without needing Drupal developers or IT support? That’s a question we get a lot at One Shoe.

The answer isn’t as simple as calculating the cost of developing the multisite CMS solution, and then dividing that by the number of websites that are expected to be needed in a certain timeframe, to assess whether or not the cost per website equals a good business case.

Yes - a multi-site or multi-domain setup allows you to support and manage multiple websites, thus multiplying the ROI in the CMS development with every new website on the platform. And they don’t nescessarily need to be all similar. With multi-domain in Drupal you can deploy many websites that look similar with simple variations in the content of each website. And a multisite architecture allows you to set up websites that are so different from each other that you wouldn’t know they are based one and the same CMS, just by looking at them. But it’s not all gold that glitters.

Based on our extensive experience with working with Drupal and complex multi-domain and multisite setups, we’ve written a series of articles that dive into the pros and cons for using Drupal in a multi-domain or multisite setup.

Read all about in on the following series of blog articles:

  1. Multi-site vs Multi-domain solution: what is it and what are the differences?
  2. What are the advantages of a Multi-site/Multi-domain solution and who’s to benefit from it?
  3. What are the disadvantages of a Multi-site/Multi-domain solution?
  4. When to choose Multi-site, Multi-domain or 1-site-1-cms?