Voting starts in March for the Drupal Association Board election.
This documentation section covers how to build an international Drupal site that will cover the required functionality for modifying the site structure, content, and integration with other services in order to have an effective and manageable site. We will also offer some tips on using custom modules to extend i18n and the locale module.
Determining your use case
Before you start building your site, you will first need to determine the overall use case for your site's current needs, and likely needs in the future. For example:
- Will end users be submitting content in their own language or for their own country?
- Will content editors need to localize their own content, or are you translating content only?
- Does the site behavior/user experience need to change per country?
- Do service integrations need to change per country?
- Will site configuration happen in one central office, or will tasks be split among international offices?
- Further, are the permissions the same?
- Are you planning one language per country, or possibly multiple languages per country or multiple countries per language?
Drupal's locale module provides a means of translating content and localizing per language, and i18n modules provide a means of extending this localization to menus, variables, and many more parts of a site as covered in the Multilingual Guide. However, translation does not cover every use case for an international site, and this guide aims to begin with covering how to configure per-country settings and per-country user experience.