Information Architecture & Navigation Principles

This document defines the structural model for the Members Information Hub.
It governs how domains, folders, pages, and navigation behave.


Related page:


1. Domain Structure

Top-level folders represent domains of responsibility.

Examples:

  • Members
  • Operations
  • Governance
  • Archive
  • Site Admin

Each domain must have a landing page.

Domains are stable structural areas, not temporary groupings.


2. Landing Page Role

Every top-level domain has a landing page that:

  • Explains the purpose of the domain
  • Provides structured entry points
  • Does not duplicate sidebar structure
  • Avoids unnecessary narrative

The Members landing page is engagement-focused.
Operations and Governance are reference-focused.


3. Engagement vs Reference Model

The site operates in two modes:

Engagement Mode

  • Events
  • Sections
  • Bookings
  • Payments
  • Calls to action

This is dynamic and member-facing.

Reference Mode

  • Constitution
  • Policies
  • Governance documents
  • Operational guidance

This is structured and informational.

Engagement content takes priority on entry pages.


4. Folder Creation Rule

Subfolders are created only when:

  • Three or more related pages exist, or
  • A stable functional area is clearly defined.

Folders are not created solely for visual tidiness.

Structure must reflect meaning.


5. Sidebar Behaviour

Navigation follows these rules:

  1. Top-level domains are always visible.
  2. Sidebar is collapsed by default.
  3. Only the active branch expands.
  4. Folders containing only pages do not auto-expand.
  5. Navigation supports clarity, not density.

6. External Linking Principle

External systems (website, social media, email, booking systems) link primarily to:

  • The Members landing page, or
  • Specific engagement subpages.

Reference domains remain accessible but are not promotional entry points.


7. Stability Principle

Structural changes should:

  • Improve clarity
  • Support growth
  • Reduce rework
  • Preserve consistency

Experimental restructuring should be avoided without clear architectural purpose.


This framework governs all future navigation and structural changes to the Members Hub.