I just love your site examples you showed - those images are simply beautiful of those snakes! I'm not sure if DNN is as mature as all the offerings of Joomla (yes I'm on the core team and actually saying that because I also know about Joomla) BUT it has the ability to be extended, in my opinion, in a manner that's far more diverse to other CMS products. I think that's why we've changed the name to be a Web Application Framework - it's working closely with the functions and power of the Microsoft aspnet framework - so I guess that's what I think gives it an edge over other applications.
My comments - and only my personal thoughts ok - since everything is quite subjective when it comes to comparisons.
1. Can have multi-lingual content EASILY
Easily - well I think think the multi-lingual aspect is one of our drivers of success - and there are developers who work with other developers who make sure their products are as search engine friendly as possible. For example - Erik from Holland - http://www.apollo-software.nl -he's quite big into module development and ML functionality and has his own modules which he's worked with other people to make user friendly.
However, the limitations I've noticed and heard about may be in the countries with RTL requirements (Right to Left) and special character functions that still bring up some errors. I can't tell you specifically but I can tell you that it's one of the key areas of DotNetNuke that's getting rectified and it moves faster because the languages are not tied in to DNN, and simply have to work, so we get them in place fairly quick.
2. Search Engine Friendly URLs
- My site is well listed on google - and it was before I used friendly urls - but I kow that http://www.inventua.com have a href exchanger that allowes you to put in much SE Friendly URLS.
However, what I like about this module is that the guys from Inventua - collaborate with other developers - meaning that if a developer has a problem in getting their module to work exactly - then they'll work on improving the products they offer. What this means is that whether it's ML or ecommerce or just a new product, the fact the guys talk to together, they seem to resolve problems fairly quickly.
I use the href exchanger on many sites - either with my own custom extension - http://www.xd.com.au/home.xd - or just in it's standard format (for those who don't have server/IIS access to do this ) and http://www.skincovered.com/home.aspx is the standard version of this. It requires some simple changes, but it's very flexible.. AND it works with ecommerce.
3. Excellent Template and presentation abilities
That's why so many people use DotNetNuke - it's flexibility to make a static or pre existing website skinned into the DotNetNuke framework is simply world class - there is nothing that matches it and that's the space I work in - Skinning and site design and deployment since I don't code, so can't tell you about the intricies.
4. Enable me to easily add content
It is easy to modify - I'm working with clients all the time, some who have little or no web experience and once they grasp a few of the basics, well they're set - and they love it. From my impression, you seem to have more knowledge and in particular enough knowledge of what these products do, so managing should be very easy - the trick is to plan your site out and get the right modules to manage long term (that was just my opinion based on working in this space for nearly 3 years)
5. Great catalogue of items for sale with more than 1 picture per item (does not need to be ecommerce enabled).
Well, there are some catalogues around, but there are also modules around that let you manipulate the data display - products that might have some obscure name but they do a fantastic job. So there are straight ways to add a catalogue module on (I have not tested all) and then there are more creative ways to do this using other modules - which a knowledge of DotNetNuke helps so you can identify what you're looking for, if an off the shelf solution doesn't help.
I use the Catalook ecommerce application and love it - and it can be used as a cataloging system, and then just a couple of check boxes, turn it into an ecommerce application. Which is great for someone thinking but not yet ready to offer ecommerce.
These are just my opinions based on a few minutes answering you direct questions - and I also run a linux server, so I think I'm reasonably objective. (don't we all) but the areas you are descritbing which are weaknesses in other products make DotNetNuke stand out even more in my opinion, and I'm speaking to and hearing of more other CMS users - not just joomla/mambo who are comparing the benefits of DotNetNuke and making the steps to integrate this product.
Thanks for your post - it was the sort of post that has specific questions and requirements, something you can look at and I hope I've answered a few of your questions in a way that allows you to make choices that better build your business.
Nina Meiers