Name the destination, not the department
An internal team name may be precise inside an organization and opaque outside it. A visitor arriving to find a guide, an object, or a service does not necessarily know which department maintains the material.
Begin with the thing a person is trying to locate. Describe the destination in language that can be understood before the link is opened. A label such as “Reading guides” gives a different kind of information from “Resources,” and the distinction should be intentional.
Give competing routes different jobs
Two nearby links can appear to offer the same destination even when they are organized differently. “Browse,” “Explore,” and “Discover” do little to explain those differences on their own.
Routes can instead state their organizing principle: by subject, by format, by date, or through a selected reading path. These approaches can coexist, but the page should help a visitor choose between them rather than make the choice feel arbitrary.
Show a little of what lies ahead
A short description or a few representative entries can make a category more intelligible. This is especially useful when the subject is unfamiliar or the label could be interpreted in several ways.
The preview should represent the destination honestly. A category promoted with one exceptional item may create expectations that the rest of the collection cannot meet. The purpose is orientation, not surprise.
Preserve the sense of location
After a visitor follows a route, the destination should confirm where they have arrived. A meaningful page title, a visible relationship to the parent section, and a consistent route back can support that understanding.
Navigation is also an interaction. A menu needs to remain available through different input methods, and its expanded or collapsed state should be communicated. These are part of the route’s usability, alongside its wording.
Provide a second entrance
An empty category or an unsuccessful search should not leave the person at a dead end. Offer an alternative that relates to the original intention: remove a filter, browse a broader group, or read an explanation of the collection.
When reviewing a route, ask someone to predict the destination before opening it. Then compare the prediction with what the page contains. A mismatch is useful information about the label, the preview, or the organization of the content.
Further reading
W3C WAI — Menus tutorial ↗This guide is a general design resource. Any assessment of a real interface needs its own defined scope and review.