Mike:
One of the most common challenges with multiple-site web architectures is determining the right level of interaction between the sites. In particular, one of the most common requirements is for some kind of content sharing. The problem with "content sharing" is that it is usually given as a pretty vague requirement at first. It's like a home storage problem - you could be talking about building a second floor on your house, putting up a shed in the backyard, or buying a storage bin from IKEA. Here, I'll try to distill some of the issues and get you asking the right questions when you encounter the problem of content sharing across multiple websites within a web architecture.
Posted 01/11/2012 - 11:37
// 3 comments
Mike:
As I said in a post from last year, nobody wants just one website anymore. I'm increasingly faced with questions about how organizations can use Drupal to build and deploy a whole family of content managed websites. Here, I attempt to partially answer that question by outlining 5 different techniques for using Drupal within your enterprise.
Posted 10/22/2010 - 12:10
// 4 comments
Mike:
It seems like these days if your organization only has one website you're about 5 short of the norm. So, a very common question I get is how organizations can benefit from a common CMS environment. It's easy to argue that standardizing an organization on a single platform definitely has its benefits. Drupal, in particular, is a good choice for such an environment. There are multiple architectures to choose from, depending on your needs.
In this post I outline 3 different levels of multi-site architectures that I've had success in implementing with Drupal.
Posted 03/17/2009 - 10:15
// 4 comments
