Hello all --

Can anyone tell me if DNN is designed to be a user-personalizable portal OR is DNN more for designing fixed-page web sites?

What i mean by that is in the first case can DNN be used to let users create pages (like IE7 tabs) and then place and arrange 'modules' (which are like portlets) thereby creating their own portal experience, like an enterprise portal (think Plumtree or WebSphere).

Is DNN *more* suited to building dynamic websites by giving *developers* or *managers* the ability to easily create websites by using pre-defined parts (modules) but yet where end users aren't given the ability to personalize the content and layout.

Thanks for your help!!!

Jeff --

Thanks for the quick response! However, i'm still not sure *who* this extensibility was meant for -- the website 'designer' or registered users of the 'portal'.

That's why i ask if DNN is more like a very nice website building tool, and/or a tool for building portal applications that let USERS define the content they want (typically by 'subscribing' to content in the form of modules/portlets that you've made available to them based on privilege) and the layout they want to see it in (typically by creating any number of tabbed pages, then specifying where on the page to place the module).

I realize that good developers can code almost *anything* however i want to know if DNN was designed MORE for building a portal or a website.

Can anyone knowledgeable comment on this distinction??

DNN is suited for both scenarios. You could build a static HTML site in minutes. Or you can develop custom modules with ease...

Hector Minaya
Microsoft Visual Basic MVP | Speaker INETA - Latam
MCSD | MCT | MCTS : SQL Server
blogs: Hector Minaya | DotNetNuke SEO | Blogger SEO | facebook junkie | Google SEO Tools