Time to throw another wrench in the works!
I have a client (a small private school) that wants to be able to have a landing page, like http://wesleyan.edu/
, where the visitor can chose:
For Potential Families
For Faculty / Staff
Then get directed to the appropriate place based on that selection. Wesleyan has /alumni/ & /students/ & /parents/ etc.
What they want is for the menus to be appropriate based on that initial selection. So Application Forms would be shown to Potential Families, but not Students or Parents. Make sense?
What I was thinking is that this is *close* to what we were doing with Languages. Basically En = Parents, De = Students, Cz = Alumni, etc.
We could then have a dropdown list with the different languages (Parents, Students, Alumni, etc.) and if you go to Contact Us for Alumni, you'd be @ /alumni/contact_us/index.aspx and all the other menus you saw were pages meant for Alumni. If you went to contact us for Students, you'd be @ /students/contact_us/index.aspx and all the menus would be pages that were turned on for Students. Does that make any sense?
The only problem is that all the content will actually be in English. I was, therefore, thinking of Shared Content, like SharedContactUs, for example.
Am I trying to make this do something is wasn't intended to do, and therefore shouldn't be made to do, or do you think this could work.
The biggest thing is basically having people be able to go in, pick an area that applies to them, and then be able to see navigation and content for them, specifically, and not have to see all the stuff that doesn't really apply to them.
Have I made myself clear? Do you think it could work? Or is there a better way to do what I'm trying to accomplish?