Umbraco vs DotNetNuke : can't decide which one is more suitable [closed]

Question

Imagine 3-4 different domains (like somesite.co.uk, somesite.com, somesite.com.sg) and each one of them will support different languages under them. The number of pages and type of content will be same on all of them (only the content will differ).

So along with the contents, user will need to specify zone and language. (we may need to edit the CMS backend with some of our controls as well).

We can't decide which .NET CMS will suit our need.

Any help will be appreciated.

Thanks

Answer 1

I think either will probably meet your needs; I work with DotNetNuke every day, so I can confidently say that DNN can handle anything you want to throw at it. I'm not as familiar with Umbraco, but your requirements don't sound like there would be anything to exclude a general-purpose CMS (you may also want to investigate Orchard).

So far as DotNetNuke goes, the ability to have multiple, related sites is one of the core concepts. You can also have one site that displays different content for different languages (I wasn't clear if that the main dividing line between your domains or not).

The development of custom extensions will be done in WebForms if you're using DotNetNuke, which may be a plus or a minus. If that's a minus, there's also a service framework in the newest versions, which enables a web service development approach that mostly ignores WebForms (using knockout.js or a similar library to present a rich interface entirely on the client).

Answer 2

Umbraco will handle this situation quite well - you would create a new node in your content tree for each language, and then assign the domain to it through the node's properties.

This situation is relatively common in Umbraco - I recently launched a six-country, 8-language site (a total of 19 different country/lang combinations), with mappings from existing Belgium domains to the new site structure, without any problems.