True. Do also consider that DNN may not be the solution for every website. I personally think DNN is best as an application framework to jumpstart asp.net development and as an instant building website toolkit for low technical people / hobbyists. But DNN is not a CMS that can handle complex content management with ML support and Workflow abilities (in any case, as of current version, 5.1.4). Our solution targets low technical people and hobbyists, while it can still be easily used by developers that are using DNN as an application framework that do not want to code ML logic in their modules.

When considering a ML solution for DNN, do also consider:

- Will the solution require / enable you to manage a site structure for each language
- Will the solution support any menu / are you limited to default DNN Menu
- Will users and data be isolated by portal / how do you manage / share data between languages / portals
- Will the solution provide true SEO urls with keywords in current language
- Will the solution enable you to use any module with multiple languages or require the use of ML modules
- Will the solution be easy to understand and manage for content managers (how much of a learning curve is required)
- How much messing around in your skin files will the solution require
- How much will the solution cost -- to buy, to configure, to manage for admins / content managers
- Will you get support for the solution
- Does the solution work with DNN 5
- Will there be support for: creating localized version of standard pages (after login, after logout, search results, etc.)
- Is the solution extensible
- Will the solution slow the site by decreasing performance

Lets dress a complete list of criterias, then evaluate all current options, including the upcoming DNN 5.3 option. Or do we trust that DNN 5.3 will surpass all of the options and make the other options obsolete? Lets hope so.