Hi all,

I'm realatively new to DNN (using it about a month). I volunteer a non-profit and am trying to redo their site using DNN. One thing which I am struggling with is how to set up the portal(s) properly. Currently(I wrote the site from scratch in PHP), the site has two portions, a public portion, and a members(volunteer) portion. The public portion has no login, while the members portion is only available by login.

Here is the problem, I don't know how to structure this using DNN, since if I make it a single portal, the navigation will get ridiculously jammed with both the public and the members entries. If I make it two separate portals (or a parent and child portal), I have the issue that DNN out of box doesn't support syncing of IDs, and some users will have data maint. responsibilities on both the public and members sites.

Am I missing something?  Does anyone have a good way to handle this, short of buying an additional module that does user syncing? This isn't an issue currently, because all of my content updating screens are on the members side (even though some of them are updating content which is showed only on the public site), but with many DNN module types doing inplace content editing, i haven't been able to figure out the best way to set it up.

I had originally thought of having the public pages just visible by unregistered users, so when a volunteer logs in they only see the volunteer-relevent stuff, but as I mentioned above, many volunteers will be responsible for maintaining parts of the public site, so they will need access to those portions.

thanks,
Phil  

I would personally want to be wokring with one portal if you have a need for common logins.  However you are are only concerned about a few administrator accounts I would most likely vote for two portals, to avoid clutter.

It really depends on the actual number of pages etc...

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Sticking with a single portal has a lot of advantages.  Each portal takes overhead to manage and you should want to avoid that

If authenticated users get to see all public content + private then just structure the menuing so that private content is placed in a secondary menu or down in the heirarchy of the primary one.

Take the time to structure your roles properly and the rest will be easy since you can target any module or page.  DNN has excellent granularity to target the content.

---

Mark Trenchard