WDD2 - Multi-level site structure
- I can describe the structure of a multi-level website.
- I can design a site structure with a home page and two additional levels.
- I can choose appropriate pages for a navigation bar.
- I can identify level 0, level 1 and level 2 pages in a site map.
- I can apply the rule: home page plus two additional levels, with no more than four pages per level.
- I can explain why the main navigation bar usually links to level 1 pages, not every page on the site.
WDD1 identified what the wildlife centre website must provide. WDD2 starts organising that content into pages.
Key vocabulary
Designing a multi-level website
The Higher rule
For Higher Web Design & Development, a multi-level website must use a home page and two additional levels. It should also use no more than four pages per level. This rule keeps the site structure big enough to show hierarchy, but small enough for users to understand.
The top of the hierarchy. It introduces the site and links to main sections.
Up to four pages linked directly from the home page.
Up to four pages below each section, used for more specific content.
Why not put every page in the navigation bar?
A navigation bar should help users choose between the main sections of a site. If every detail page is squeezed into the top navigation, the site becomes harder to scan. A good design usually puts the level 1 pages in the main navigation bar, then lets each section page link to its own level 2 pages.
Worked scenario: Meadows Wildlife Centre
From WDD1, the centre needs visit information, animal profiles, school workshop enquiries, volunteering information and fundraising campaigns. These requirements can be grouped into a site structure before any wireframes or HTML are made.
Worked examples
Question: Which pages should appear in the main navigation bar?
A pupil adds a Donate page but does not link to it from Home, Support Us, or any other page.
A local music school needs pages for lessons, tutors, concerts, prices, piano lessons, guitar lessons, tutor profiles and booking an enquiry.
Sketch a three-level site structure: Home, up to four level 1 pages, and suitable level 2 pages.
Home
- Lessons: Piano Lessons, Guitar Lessons, Prices
- Tutors: Tutor Profiles
- Concerts: Upcoming Concerts
- Contact: Booking Enquiry
This uses four level 1 pages and places the detail pages underneath a sensible section.
- Making the site too flat. A home page with ten direct links does not show the required two additional levels.
- Making the site too deep. Higher needs two additional levels, not a maze of level 3 and level 4 pages.
- Putting too many pages at one level. The rule is no more than four pages per level.
- Creating orphan pages. Every page in the structure needs a clear route from another page.
- Confusing site structure with visual layout. Page hierarchy is not the same thing as wireframe layout. Wireframes start in WDD3.
If asked to describe or exemplify a multi-level website, name the levels clearly: home page, level 1 section pages, and level 2 detail pages. If asked about navigation, choose links that help users reach the main sections rather than listing every single page.
Task Set A - Core questions
Task Set B - Extension
File this in OneNote under:
Higher Computing Science > Web Design & Development > WDD2
Suggested timing: 6 min warm up, 12 min notes, 15 min worked examples, 10 min now-you-try, 15 min Task Set A. Use the remaining double-period time for Task Set B or pupils redrawing site maps by hand.
Scope control: this lesson is site hierarchy only. Do not teach wireframe layout yet; that is WDD3.
Key misconception: pupils often put every page into the main navigation bar. Keep returning to the idea that the nav bar should expose the main sections, not every detail page.