I would create a node for each language (nl, de, en) and then use a URL rewrite rule to prevent /nl/ being accessed and rewrite all trafic without /de or /en to /nl. This means the client would see www.mysite.nl but your application sees www.mysite.nl/nl/.

Info on the rewrite module for IIS here: http://www.iis.net/learn/extensions/url-rewrite-module/using-the-url-rewrite-module

Hope this helps!

Hi Sander,

The way I would do it, is to create a site node and under the site node three home nodes, one for every language:

site
..nl
....dutch content
..ge
.... german content
..en
.... english content

On the site settings node create a property with the alias umbracoInternRedirectID and use a Content Picker datatype. Then on the site node use the content picker to point it to the homepage of the dutch language version, ie. the 'nl' node. (the setup was described by Sebastiaan Janssen in 'The Ultimate Site Structure Setup'

On the language nodes (nl, ge, en) you will need to configure hostsettings like this:

nl: http://www.mysite.nl
ge: http://www.mysite.nl/de
en: http://www.mysite.nl/en

The best strategy for creating the content is to fully complete one language version, eg the 'nl' node and all the children of 'nl'. And when the 'nl' version is finish, do a copy and check the 'relate copy to orginal' checkbox. This way the visitor can switch between different language versions of a content page.

hope this helps

Anthony

is working on a reply...