As far as I can tell, there's a lead programmer on this thing: libardo. Then it seems that nazjunaid did his batch of essential fixes, but that's it for active development.

The lagging documentation, which breathes down libardo's neck for a while now, makes it a thougher sell. On the other hand, the move to nuget was a keystone in making the thing easily usable out-of-the-box.

Now, a CMS like Orchard - which seems to me about feature par with N2CMS - is being backed up by Microsoft. This means (1) it's getting a lot of exposure, (2) it's getting assigned development resources and (3) it makes it an easier sell ("hey, it's endorsed by MS"). Also the nuget gallery integration makes it a better candidate for adoption, because it's so easy to integrate extra's (I'd *love* to see that in N2CMS. Heck, if I find resources, I'd implement it myself).

While I think architecturally, N2CMS is a lot more mature and exposes a seldom seen flexibility for a CMS, I'm also afraid it will be kept back by it's own succes. I mean: in order to make this thing survive, documentation must be fixed, different versions need to be supported (asp.net, mvc, dinamico, 2.1.1 until 2.2.3, ... ), forums need to be addressed, a single point of responsibilty has to be created and maintained (instead of info scattered over sites). It's clear that, even though one can wonder when libardo sleeps and whether he's not just 2 persons acting as one, it's nearly impossible for him to keep this up.

Given all these thoughts, libardo, what's your feedback? Maybe you already have such a plan? Maybe you need more direct help from the community?

It's my fault. I've been hacking away while essentially ignoring a lot of good support offered. Sorry guys! I'm starting immediately to sketch down a project. BRB