Abstract: In today's web, it's straightforward to publish in any single language. The cool Web 2.0 sites are organised around user-supplied content: postings, tags, comments, photos, videos. But what happens when you try to do all that in more than one language at a time? Do you translate the user-supplied content? And how? Can you crowdsource the localisation? This talk looks at the business, technical, and design issues of multilingual web sites. We'll look at role models, examine social translation, see how technologies like Joomla, Drupal, WordPress, HTTP, and URLs fit in. Get inspired to add another language to your site!

• What is multilingual Web 2.0: we see who's doing it in multiple languages, and how well. Wikipedia and cousins are massively multilingual and user-contributed. Facebook's Translations application has successfully crowdsourced their localisation, and has a fascinating in-situ editing UI.
• Value: we look at business issues. Who needs multiple languages and what for? Is content in various languages the same or different? How/why different?
• Structure: we look at design issues. How to link content in one language to another? How to distinguish UI language from content language from geography focus? What are options for the URL structure? What special issues do non-text content (like videos, tags, links) bring?
• Technology: we look at tagging content with language, at the need for localised URLs and meta text. We look at capabilities of Joomla, Drupal, WordPress CMSs for multilingual content. And we see how to use HTTP and URL clues to help select which language to supply.
• Translation: we look at options for translation: paid translation, social translation, machine translation. What tools and structures are needed? Crowdsourcing of UI translation, its risks and concerns, with Facebook as an example and cautionary tale. Linking the web CMS to translator's tools like translation memory and workbenches. And Process: tha challenge of making all the parts move together and on time.