DrupalCon Amsterdam 2014: Building a Multilingual, Multidomain Drupal Site
Speakers: dagmitaursbucher
We are from Switzerland and do Drupal. What can we do really well? With 4 official languages, of course, we can do multilingual websites! But sometimes this is not enough. Our customers are big and international, and usually have multiple sites for each country. Which makes it really hard for the global webmasters to manage the site and make sure that the country editors do not break the site. So the best solution is to have only one site, with multiple Domains. We're using Domain Access for that, but it's not that easy.
Even harder it gets when the client is listed on the stock market and publishing node to early could cost you multiple millions. But still some stakeholders wants to review if everything will be correct when he hits the publish button. You need a good deployment and workflow for handling such changes.
In the last years we have build such sites, had multiple deployments and published important press releases for our customers.
Our case will show:
how to setup technically multiple domains, multiple languages and how they play together seamlessly
how we set up roles and user permissions to make sure that country editors can only change what they are supposed to
how to manage translations efficiently and what tools we use for that
which project methodology we used for the initial development and future deployments
how we handle deployments via a special staging deployment
how the team is set up
insights directly from the client, how it is to work with Drupal and Open Source
We are from Switzerland and do Drupal. What can we do really well? With 4 official languages, of course, we can do multilingual websites! But sometimes this is not enough. Our customers are big and international, and usually have multiple sites for each country. Which makes it really hard for the global webmasters to manage the site and make sure that the country editors do not break the site. So the best solution is to have only one site, with multiple Domains. We're using Domain Access for that, but it's not that easy.
Even harder it gets when the client is listed on the stock market and publishing node to early could cost you multiple millions. But still some stakeholders wants to review if everything will be correct when he hits the publish button. You need a good deployment and workflow for handling such changes.
In the last years we have build such sites, had multiple deployments and published important press releases for our customers.
Our case will show:
how to setup technically multiple domains, multiple languages and how they play together seamlessly
how we set up roles and user permissions to make sure that country editors can only change what they are supposed to
how to manage translations efficiently and what tools we use for that
which project methodology we used for the initial development and future deployments
how we handle deployments via a special staging deployment
how the team is set up
insights directly from the client, how it is to work with Drupal and Open Source