|
Having followed and used .NET CMS'es since the early days of DotNetNuke, I have to say that DotNetAge is very impressive. It has many of the sorely needed features to support MVC and jQuery in a CMS that everyone can use.
While having a predominant extendable CMS that's based on jQuery and MVC pleases me greatly, I'm afraid DotNetAge does not currently address the next set of problems facing Microsoft Internet Developers. This is support for HTML5 and Mobile applications on non-Microsoft platforms which are becoming dominant in the world. I took the time to view DotNetAge on my iPad, and it does not function well. The menu system is unweildy, and jQuery's liberal use of roll-over effects simply doesn't work on mobile touch devices. It's clear mobile devices have not been seriously taken into consideration when making DotNetAge. Being that DotNetAge is MVC based, it does have a chance to encompass this next generation of devices that are coming out. If it does, it will probably become a very successful CMS that is widely used, and a solution for cutting edge problems. But if it does not, I'm afraid it will be another Microsoft CMS that is several years behind the curve. I strongly suggest iPad/Andriod/Webit HTML5 compatibility be inherently chosen in the default templates that are used in DotNetAge. |