Group

AIM

MSN

Website URL

ICQ

Yahoo

Jabber

Skype

Location

Interests

Languages

Hello.
My existing website (here) uses a side-nav.
It's currently coded such that I need to copy/paste and then modify the nav code onto every one of my pages... totally lame.
I'd like to be able to easily add primary tabs and secondary tabs to this nav in one master-nav document.
Apparently one easy way to allow for using a master-nav document is through the use of PHP "Include" (or "require"), as explained (here) on w3schools.
I followed the above example, and got it working great as a single-level nav (a 1-level nave with only primary tabs).
Unfortunately, the PHP "include" example doesn't show an example of a 2-level nav (one with primary tabs and secondary tabs).
My questions to you guys:
1. What would be the best way for me to go about coding in order to get a single master-nav document that I can easily edit, and said master-nav will also have the functionality of a 2-level nav?
(I'm guessing I'll be needing some JQuery)
2. Can you point me in the correct direction of an example / tutorial?
Thanks.
-Josh!

Dear members, moderators and administrators,I thought of sharing this item of information with you on W3schools forum, may some members find them useful.Most of us the members concentrate on the technical part of the implementation and sometimes ask how do we know the "Usability, Quality, Measurement Criteria, Effectiveness and Interactivity" of our website projects.I haven't made this information myself; I have just studied during some previous year in university within a course (module) of Human Computer Interaction, thus thought of sharing them with you. Brief Introduction:-A main goal for an interactive system designer,"E.g. Website of any type or content" is to achieve the highest accessibility and usability on different scales for achieving the targeted success whether the website is for E- commerce within an E-business, gaming or even social networking; thus acceptability and user-engagement should be put into consideration.All these aspects are viewed by the three main essential categories that are known as TOP LEVEL PRINCIPLES:-
Learn-ability
Effectiveness
Accommodation
There also exist the key issues that those categories sought to fulfil: -
Usability: - resembles the quality of interaction (A.K.A Quality of Service QoS), in terms of context elements such as time efficiency to perform tasks, number of errors expected and handling them.
Acceptability: - resembles the level the system serves its regarded purpose in context of use and interaction (Note: - could be cultural wise).
Engagement: - resembles and concerns designing to the utmost peak of success, (looks and feel wise), in addition most smooth experience.
Access: - as simple as defining it as an ice-breaking key issue, concerns with the removal or elimination of all the expected barriers between the system and the user "E.g. cultural borders, social borders, and economic borders" ;thus THINK OF DESIGNING FOR THE UNIVERSE! THE TARGET IS UNIVERSAL DESIGN!! so DESIGN FOR ALL..Context: - First: - Learn-ability
Visibility: - simply described as making the system's functionality visible, more like don't hide or immerse functional links or buttons within spots that confuse the users or make them ask where they are.
Consistency: - means that the website's look and feel is not very much of a variable over different pages, “E.g. don't make the home page have this pinky colour while the other pages are darker and less radiant”.
Familiarity: - Includes the usage of familiar language on the lists, menus, buttons and links “E.g. use register or sign up for more formal websites, yet you can use join us now for less formal websites; so it is subjective in an objective way or more like a mixture of both”.
Affordance: - making sure that the design has the suitable Affordance for the users, by using familiar symbols and icons, “E.g. the check mark for okay or is more often used than thumbs up”.
Second: - Effectiveness
Navigation: - providing support to enable the users to move around the system conveniently by different methods, through maps, menu bars, search bars, links and etc.
Control: - making the user in charge and control of the system, having all the “permitted” actions and interactions available for them to successfully interact with the system and experience the system's collaboration.
Feedback: - the rapid feedback to the user from the system, so that they feel the system's environment and get an idea of how their actions have affected the system , “E.g. a thanking message to inform the user that registration has been done successfully”.
Recovery: - the recovery of expected errors, more likely refreshing the page or sending the user back to the home page, or even refreshing the form, “E.g. the errors that rarely occur on Facebook that automatically refreshes the page”.
Constraints: - the denial of some actions or entries by the user from the system, “E.g. invalid entries in the registration form, or even preventing spams from the users”.
Third: - Accommodation
Flexibility: - the allowance of multiple ways of performing any process within the system, either through navigation or any other aspect ,“E.g. allowing users to go to home page by either clicking on home or the website's logo”.
Style: - the style, attractiveness or the user's satisfaction by the website's look and feel.
Conviviality: - the system has to be polite, friendly and generally welcoming to all users regardless of race, beliefs, religions, nationalities or gender.