Hello,

I apologize in advance for asking a question that may be self evident if I dig only a little bit more deeply. However, I'm hoping to get the answers I need without lengthy research into DNN, such as setting up my own installation and writing some code.

As background, I was a partner in a web-dev company in 2001 - 2003. We built a CMS system that we then licensed exclusively to our customers. At that time, it made sense to build your own. More recently (2005), I wrote a CMS system for my own moonlighting purposes. Now that I'm starting to get more serious with my moonlighting, I'm considering moving to DNN. Why build it, support it, and extend it yourself from scratch when there is a great platform to start with, right?

I signed up for the demo and played with that a bit. I also spent time with the screenshot walk-through. My main concern is that there doesn't seem to be a well defined "site editor" role with attendant permissions and tools. The DNN tools are more powerful (and confusing) than I want to expose to my customers, but seemingly not quite powerful enough to create the role I want through the GUI. Ideally, a "site editor" would  have access to a dumbed-down interface with limited abilities. Specifically:

• Site hierarchy admin page
• Create/edit pages at appropriate places in the hierarchy (modules pre-defined in a "template" format, no need to choose which modules go where in the layout, no ability to change layout)
• Create / Edit Events and a handful of other modules -- didn't get into these enough to see if I'd want to dumb them down as well
• Limited user management -- full control of end user accounts, ability to create other site editors, not full admin permission

So, did I miss something obvious? If not, is there a free or commercial module available that creates this type of dumbed down access? If not, how difficult is it going to be to write my own (preferably using C# code-behinds)?

Thanks in advance.

Evan