> For the complete documentation index, see [llms.txt](https://www.information-architecture.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.information-architecture.world/wiad-organizer-guide/your-local-website/findability-information-architecture-and-seo/organizing-your-space.md).

# Organizing your space

Top-level navigation, nesting depth, naming

How you arrange your pages decides whether a first-time visitor can find what they came for in a few seconds. This page gives you a recommended structure, limits on depth, and rules for naming pages. It applies to GitBook spaces and Independent sites alike.

### Start with what visitors want

Most people arrive with one of five questions:

1. What is this event?
2. When and where is it?
3. How do I register or attend?
4. How can I take part (speak, sponsor, volunteer)?
5. Who do I contact?

Build your top-level navigation around those questions, not around how your organizing team is arranged internally.

### Suggested top-level navigation

**Keep it to 5–7 items.** Use the same labels as other WIAD locations where you can, so someone who has visited another World IA Day site already knows where to look.

<table><thead><tr><th width="254.0703125">Page</th><th>What it holds</th></tr></thead><tbody><tr><td><strong>Home</strong></td><td>What WIAD is, who organizes this location, link to the global WIAD site, features a link to the most recent or upcoming event.</td></tr><tr><td><strong>Events</strong></td><td>One page per year, upcoming or most recent event first.</td></tr><tr><td><strong>Get involved</strong></td><td>Call for speakers, sponsorship, volunteering</td></tr><tr><td><strong>Code of conduct</strong></td><td>Link to or copy of the global code of conduct</td></tr><tr><td><strong>Contact</strong></td><td>Location-based email address and social links</td></tr></tbody></table>

### Nesting depth

**Keep pages no more than two levels deep.** A visitor should reach any page in three clicks or fewer from the home page.

* **Level 1:** top-level pages (e.g., *All events*)
* **Level 2:** pages within them (e.g., *Location 2026*)
* **Level 3 (only if needed):** supporting detail (e.g., *Location* *2026 → Speaker bio*)

If a page has more than about 7–8 children, group them or split the topic. If you find yourself nesting a fourth level, the section probably needs a different organization, not another folder.

Page groups and nested pages show up in the left-hand side navigation. You might want to consider hiding pages within page groups or selecting the most recent few to highlight instead of listing all pages within a page group.

### Country sites and city sites

Your structure may need to flex depending on your location's scale.

#### City sites (e.g., Los Angeles, Philadelphia, New York)

Usually one event per year, so a simple structure works:

{% code overflow="wrap" %}

```
Home
├── About
├── Get involved
├── Events  # This is a page group in GitBook
│   ├── All events  # Index page within this page group
│   ├── Location 2027  # Event detail
│   ├── Location 2026
│   └── Location 2025
├── Speakers  # Hidden page group
│   └── Speaker name  # Hidden speaker bio
└── Contact
```

{% endcode %}

#### Country sites (e.g., the Netherlands, Germany, Uzbekistan)

You may have several events in different cities and possibly several languages.&#x20;

```
Home
├── Events  # Page group
│   ├── All events  # Index page in this page group
│   ├── Eindhoven 2026  # Event detail
│   ├── Utrecht 2018
│   └── Enschede 2015
├── Get involved
├── Speakers  # Hidden page group
│   └── Speaker name  # Hidden speaker bio
└── Contact
```

### Naming pages

Page names appear in the sidebar, in search results, and in links people share. Good names are:

* **Descriptive.** "Call for speakers" or "Call for proposals"
* **Short.** Aim for 1–4 words in the navigation. Use the *link title* field for a shorter version of a longer title (see [Page naming and URL conventions](https://www.information-architecture.world/wiad-organizer-guide/your-local-website/findability-information-architecture-and-seo/page-naming-and-url-conventions.md)).
* **Consistent.** If one event is "2027," don't call another "Seattle WIAD Spring Event." Use the same pattern for every year.
* **Plain.** Skip internal jargon, nicknames, and clever names. Visitors don't know your team's vocabulary.
* **Written in sentence case.** "Get involved," not "Get Involved" or "GET INVOLVED."

#### Naming events by year

<table><thead><tr><th width="159.30859375">Site type</th><th>Page title</th><th>Link title</th></tr></thead><tbody><tr><td>City</td><td>World IA Day Seattle 2027</td><td>Seattle 2027</td></tr><tr><td>Country</td><td>World IA Day Amsterdam 2027</td><td>Amsterdam 2027</td></tr></tbody></table>

### What to avoid

* **Renaming or moving published pages without a plan.** Links, social posts, and search results point to the old address. See *Handling renamed or removed pages (redirects)*.
* **Reorganizing the structure every year.** Keep it stable so returning visitors and search engines know where things are.
* **Editing global pages.** Pages managed centrally (branding, code of conduct, and so on) should stay as provided. See *What's locked vs. editable*.

### For independent sites

If you run your own site, apply the same principles:

* Keep the main navigation to 5–7 items
* Stay within three levels of depth
* Match the recommended top-level labels where possible
* Include a link back to:&#x20;
  * World IA Day: <https://www.information-architecture.world/worldiaday>
  * Code of conduct: <https://www.information-architecture.world/policies/code-of-conduct>

By using the same branding and similar structure, we can create a coherent design even though all the sites are independently managed.

### Quick checklist

* \[ ] Top-level navigation has 7 or fewer items
* \[ ] Every page is reachable within three clicks of the home page
* \[ ] The current event is easy to find from the home page
* \[ ] Past events are available by year, not deleted
* \[ ] Page names are short, descriptive, and in sentence case
* \[ ] Event pages follow the same naming pattern every year
* \[ ] No duplicate or orphan pages
* \[ ] Multi-language sites use the same structure in every language
