Movember is run all over the world; unfortunately they weren’t quick enough to purchase .co.nz, .co.uk and a couple of other domains. We still need to cope with international sites, multiple languages and one domain for SSL (Certificates cost a fortune – why buy extras when you can avoid it.)

So we need the following capabilities from the Zend Framework Routing:
1.    http://country.movember.com/Country homepage, default language English.
2.    http://language.country.movember.com/Translated country-specific homepage – Option 1
3.    http://country.movember.com/language/Translated country-specific homepage – Option 2
4.    https://www.movember.com/country/donate/Country-specific donation page, default language English.
5.    https://www.movember.com/country/language/donate/Country-specific donation page, language provided.
6.    http://www.movember.com/International sites directory (Fine, it’s a splash page…)
7.    http://www.movember.com.country_suffix/Country homepage, default language depends on the country.

First of all, I ask, what do you think?
Route all traffic through www.movember.com or even just movember.com using a Locale URL structure /au/en/ or /en_AU/, or split traffic to sub-domains? This is not required from an infrastructure perspective, although potentially for analytics.

Should sites where the domain is available (www.movember.com.au) redirect to the www. or au. or just host the entire site from that domain (except for secure traffic)? As a programmer I like setups to be consistent, so it’s very hard for me to support (for example) movember.com/ca (defaulting to English) and movember.com/ca/fr/ (French) and movember.com/ca/en/ (English) As I’m not sure what will be used in the end, I’m currently writing a router setup that supports every format mentioned above, and we’ll be able to develop the site without ever needing to think about which of the configurations (above) the user is using.

James Turle