You should be able to easily do this with permissions. Create your page structure like this:

• Home
• About
• Contact
• Links
• Login
• Account
  
  • User Page 1
  • User page 2
  • Logout

Then set the permissions for the Login page to only unauthenticated users and set the Account page for only Administrators or Registered Users.

Note: Superusers will still see the Login page.

Another option is to still use the page structure above and then in your skin ascx, wrap it in something like this:

<div class="Skin <%= IIf(Request.IsAuthenticated, "LoggedIn", "NotLoggedIn") %>"></div>

Then just use css to hide and display elements based on the class LoggedIn or NotLoggedIn

Good call on this one. I managed to create the layout using permissions alone. Couple of notes from this approach:

• login page can't be called login.aspx if it doesn't contain an Account Login module, for some reason it stops the pop-up account login from working properly. I had to remove the new login page from the database table to get back in.
• The Login and account pages can't have the same name because they're on the same level, so using "account" as a login page and then using "account" as a hook for the dropdown menu won't work, ended up using "Account" and "My Account".
• The logout function need to link to logoff.aspx and seeing as this page doesn't exist in the site structure, I had to make the page a link (options found in the link type section of the page settings) to http://theDomain.com/logoff.aspx

I have thought of another option using conditional statements to check if the user is logged in and then loading a different menu depending on the state of this, but it's un-tested atm. Will update if this works depending on if my client wants to go down that route.

Thanks for the help on this one.

Rick.