Yes, that is correct. If you have 6 languages, our solution may not be the most adequate for your needs, since you will have to manage 6 pages with their own modules. You can use the copy page to make the initial creation better, but still, this will be a pain to manage.

-- Do you really have 6 languages? If so, is DNN really your best choice? --

Our solution is designed to be really easy to use (virtually no learning curve compared to a non ML DNN portal). A better ML content implementation should be designed at the CMS level, which DNN is currently not (it doesn't have true CMS features, such as content versioning, centralized / normalized content management / editing, etc.). ML Content support is planned in future DNN 5 releases. But if you need a solution now, you have a few options, all with their respective limitations.

Some available ML solutions require for the usage of ML specific modules. This will enable you to have 1 set of pages, with modules that can be configured with content for each language. However, this will limit you to using ML modules. For non ML modules, you can hack around with solution that will require to add a module for each language on the page, configure it with culture specific content, then show / hide the module based on current language using a special configuration. That will be 6 modules on the page -- how will that affect performance, etc.?

If you have 1 set of pages, there will be some sort of hack to localize the page names. I have not verified, but my guess is that the solutions that use 1 set of pages will not produce SEO friendly URLS (giving an URL with keywords in the respective language). And also your choice of menu will be limited to default DNN Menus (no support for Telerik, or Snapsis, or XMenu, etc.). Also, how will the search results look like?

Bottom line is... DNN 5 will eventually have built-in ML support. In the meantime, every ML solution has some limitations. The limitation of our approach is having to manage 1 page per language, but with some other added benefits, such as supporting most menus (including 3rd party menus), producing SEO friendly urls, having virtually no learning curve. And our solution is free (which shouldn't matter to you if you are implementing a 6 language portal, but still...). We are targetting portals with 2 languages, which is what we believe is the most common use. For portals with more languages, they are usually larger portals, for which we would not recommend DNN.

Etienne