[plum] Different layouts vs. User dependent components

[Dan]

In the Application Framework Overview / About Plum Layouts, it is recommended that if you have similar layouts give each its own copy of the files it needs…   In my project I have roughly two “different” yet similar layouts occurring, the “display” of which is controlled (dependent) on the type of User that is or is not logged in.   Example: the site/project has a top-horizontal SiteNav bar, the options/items shown are based on whether the user is not logged in—a Public User—or is logged in as either a “client” or a “coach”  The layout of the page (index.cfm) or the SiteNav bar itself does not change, only the content of the bar changes (based on the User) and the content then selected/displayed within the “content wrapper” section/div.   2nd example: the site/project has a page centered div “content wrapper” (with the Masthead and SiteNav above it, and “footer/copyright notice etc. below it) For a Public (non-Login) user the “internal layout” of the ContentWrapper div will/can changed based on content items selected. For a Login User the ContentWrapper div will now contain a left-column “subNav” and a primary right-column “content” div.   There are changes in the layout occurring (which is also very similar to the standard Plum layout).  To me it makes sense to have ONE layout set with switch/case conditions controlling which “internal” content div’s to use based on the user’s Login role. I’m using the User’s role to determine which sub-layout condition to use as well as (in part) what content to pull in to that sub-layout condition. Versus having a “public user layout” and a “logged-in user layout”   Am I on the right page with this?     Thanks,     Dan Kaufman       An Elephant Never Forgets [EMAIL PROTECTED]