CMS

How do you even get started in your planning for a large Web Site migration?  Of course, you want to have strong Web Strategy, Web Governance, and Web Team in place.

Migrating to a new system can be surprisingly difficult (some reasons).  The following steps can help in your migration:

Many decisions made early in the design of a multilingual site will determine the capabilities for years to come, so all aspects should be carefully considered. That said, many key issues aren’t immediately obvious when developing a multilingual Web site the first time, so this blog post aims to pull out some important questions to ask when defining the requirements of your multilingual Web site:

Does your organization have a lot of information to share with your users/customers/members?  

If so, you probably want to distribute your content via RSS.  Not only can individuals subscribe to your feeds using Google Reader, NetNewsWire, Netvibes, or whatever, but your content can then be re-used on other sites.  

So your organization decided to get a new Content Management System (CMS), either replacing an existing CMS or as your first CMS. A strong organizational temptation will probably be to treat implementing the CMS for your institution as a project rather than as an internal product. But in addition to project management, you'll need product management. It's unfortunate that project, product, and program management all have the abbreviation of PM, and that may contribute to the confusion between these terms.

 CMS migration is a resource-intensive undertaking.  The following graph of central team effort isn’t strictly accurate but hopefully will illustrate some key points: