lmeljalb wrote
Ok - I am VERY new to DotNetNuke. I got it installed and am just looking through it and trying to understand it. We would like to have a portal type website for our intranet. This looks like it might do the trick...but it's probably a bit more robust than we need. I tried using the old portal...but it wasn't quite robust enough. See my thing is - we don't want to have the users register or login...there is no need...it's on our intranet. Can dotnetnuke be used in this way? And if I want some users to login to be able to update content...is this possible? Can anyone recommend a book for dotnetnuke 3 that can help me understand it?
You can achieve this, but it can take a little effort. The AD provider can be configured to allow users to auto-login. In the future AD integration will become more robust.
Or, you can just display everything to the ALL USERS role and then secure only certain content/pages by login. That has scenario worked well for me, but the caveat is you have to manually manage the users and roles. In my intranet scenario, the vast majority of users(hundreds) just view content (without logging in), but I also have about 50 content administrators who manage their own pages. They are the only ones who login to the site. Each department has a page or section of pages and a page administrator. The page administrator belongs to a security account that can only edit that page, or create sub pages.
Ex: The HR page has an admin named Mark. Mark belongs to the HR Admin role that I created. The HR page can only be edited by those in the HR Admin, or the site administrator (aka me).
I tend to not suggest buying a book, since they get outdated rather quickly. There is plenty of info on the web and in the DNN documentation.
I would not recommend using DNN 3 if you can help it. It's not really supported anymore and you'll be limited in the modules you can buy and use.
BOL