If your thinking about using DNN (thats Dot Net Nuke) I thought you might want to get a few pointers as to why we think it's worth considering...

1) huge community that seem keen to offer help
2) a really good basic admin management for registration and privilegies
3) developed in microsoft.net so a good pool of talent out there to extend it
4) lots of extra modules (though some are poor quality so try before you buy)
5) skinning options include lots of third party skins
6) a really generous open source license

We have been developing in Dot Net Nuke for many years now - its made a huge difference to the speed at which we can develop web based systems. It's a big system to get to grips with but worth the effort.

When we first started using the term "intranet" we had to quickly stop. The term confused people. Now, though, it's clear the term is in common usage. We get enquiries now from people very clear that they need an intranet system development for them and even clearer as to what they need it to do. For us we'll do that as a sharepoint development or as a DNN development - it depends on what the client preference is - or the technology already in place.

Good to see the term in common usage - no doubt we'll all be using augmented reality soon as well.

DNN - great but limited text books

I guess one of the things that is a frustration is the lack of good text books on Dot Net Nuke - our CMS of choice (DNN).

Maybe it's an age thing but it is useful to have a couple of text books to refer to from time to time. It does mean of course that our DNN development skills can be in high demand - it's a big system and needs good people to make the best of it. But it would be nice to have a few more easy to read manuals around - still there is always Google I suppose.

And in the end that is where developers head to first - the information is probably fuller and more uptodate than any text book could be.