1. Download and install
http://www.typolight.org/wiki/extensions:changelanguage
That is a great extension that you will have a lot of use for. It works with 2.6.1, and actually, on it's page, you will find good starting tips
2. Create a site structure in the primary language
So, first create a Root of a new website, and specify its language. Set this as the fallback language.
Under this Root, create the site structure as you normally would.
3. OPTIONAL, but RECOMMENDED: Add all content to the primary language site and set it up as you wish
It is really useful to now make all the modules you need, set up layouts as you wish, etc. Test that everything works as you want. So, DEVELOP your website. If you will do a lot of direct translation (i.e. you have the same content in both languages), it will help you that you enter all of it now. See the next step to understand this step.
Make sure you add a Change language module somewhere in your layout, so it's displayed on every page.
4. In Site structure, for the default language Website Root, do a "Duplicate page ID 1 with subpages" (this is a green button with a down arrow)
This will copy the entire site structure, as well as all the articles you entered, setups etc. Set this new root to your new language (uncheck Fallback language option),
5. In Site structure, translate everything to the new language and connect them to the primary language
Now go from page to page, translate their names, set their Language, and select appropriate page in the Fallback-Page field (this field is provided by the extension you got in the first step).
The fallback-page is the other-language-equivalent of that particular page. Now, when you click the output of Change Language module (in the frontend) for each one of your pages, it will direct you to the equivalent page in another language. This is very cool.
6. If you already created your articles, publish them and translate them in the secondary language site
When you copied the site structure, you also copied all the Articles in it. You will need to translate them and publish them (they are unpublished by default after copying).
7. Crate new news archives and front-end modules
I'm still not sure how to best go about this, but for each news archive in the primary language, I have a secondary news archive in the secondary language. I also created modules for displaying those, and added them to the secondary language. There must be a nicer way to handle this though...
Bookmarks