Tom Ogden's blog
I am often asked to explain the differences between the different Content Management Systems. While I try to give an objective evaluation, you must know that I have chosen the Drupal CMS framework exclusively for all our work. This is after having built my own CMS from scratch and spending two years in search of the best possible platform.
There are many CMS's, some proprietary, some opensource. I will focus on the most popular CMS frameworks, which are all opensource.
After so many years of fighting incompatible web coding standards, it's a relief to find a standard that doesn't break things in non-compliant browsers. With CSS, you can breath life into every button, take the stiffness out of graphics and even add animation--all without harming the look in older browsers, like Internet Explorer 8.
The common e-commerce implementation within Drupal is Übercart. It is simple and has a huge number of contributed modules, including a few very obscure applications. The disadvantage is that it is not a particularly lightweight implementation, and navigation is limited to your ability to build views. However, if simplicity or functional flexibility are the important considerations, then Übercart excels in these.
Drupal is, thankfully, fully setup for easy internationalization. Careful adherence to the t() function in the display of all strings helps to ensure that.
Localization must be dealt with per locale as per your own marketing strategies. My own experience at international trade events is that most people prefer English, if they cannot get their own language. Thus, it follows that locales should follow a target population base, rather than trying to find a compromise.
This is the most neglected area of web development. It applies to both users managing the website and to anonymous users or casual visitors to the website. Because web developers are often physically distant or inaccessible to their users, the users are too often frustrated and give up without ever resolving their issues.
Recruit EVERYONE. There’s no such thing as too much testing. It’s to your advantage to engage everyone in the company. Ask for their help. Explain the definition of a bug (unexpected behavior) and give them your direct line to contact you immediately if they find something. Encourage company personnel to setup the company websites as their default home pages.