Latest / 5 Minute UX / How To Number and Annotate a Site Map
Transcript
- 0:07This lesson is How To Number and Annotate a Site Map. Let's get
- 0:11started.
- 0:18You likely already sketch site maps, but you might overlook the
- 0:21pages that sit before the main entry point. These pre-home
- 0:24pages include login screens, register screens, or even Flash
- 0:27preloaders that users encounter first. We assign these specific
- 0:29entry points numbers in the zero point X format to clearly
- 0:32distinguish them from the rest of the structure. This simple
- 0:35step establishes the baseline for traceability before the main
- 0:37navigation sequence even begins. By capturing every decision
- 0:40point in this zero point X sequence, you ensure nothing
- 0:43gets lost in the transition. It creates a clean anchor for
- 0:45everything that follows, allowing other teams to
- 0:47reference these early interactions accurately.
- 0:55Once those pre-home pages are secured with the zero point X
- 0:57format, you designate the home page as one point zero to serve
- 1:00as the central anchor of the site map. This number acts as
- 1:02the origin point for every other page in the structure, so when
- 1:05you start numbering, you are building outward from this
- 1:07single, stable reference. It prevents the map from feeling
- 1:09like a collection of disconnected islands, because
- 1:11everything ties back to this primary entry point. You treat
- 1:13the home page as the trunk of the tree, and every other
- 1:16section branches off from it in a logical, hierarchical
- 1:18sequence. From that anchor, you assign whole numbers to primary
- 1:20sections branching from the home page to establish the main
- 1:23navigation levels. You might label the blog section as two
- 1:25point zero, the about page as three point zero, and the work
- 1:27portfolio as four point zero. This creates a clear, linear
- 1:30progression that mirrors how users perceive the major areas
- 1:32of the site. By using whole numbers for these top-level
- 1:34categories, you create distinct buckets that are easy to
- 1:36identify and reference during design discussions. It’s a
- 1:39simple system, but it provides the structural integrity needed
- 1:41for complex sites. When pages nest deeper within those primary
- 1:44sections, you use decimal extensions for pages nested
- 1:46within primary sections to show their subordinate relationship.
- 1:48For example, if you have a terms and conditions page that lives
- 1:51under the home page, you number it one point zero point one.
- 1:53This notation immediately signals that the page is a child
- 1:56of the home section, rather than a standalone entity. You can
- 1:58continue this pattern indefinitely, adding decimals
- 2:00for every level of depth, which means the number itself tells
- 2:02you exactly where the page sits in the hierarchy. The real
- 2:05power of this system emerges when you propagate these
- 2:07specific numbers to content matrices, task flows,
- 2:09wireframes, visual design inventories, and QA testing
- 2:11scripts. You apply the same numbering logic across all
- 2:13project documents to maintain traceability of features,
- 2:15functionality, and content. This ensures that a wireframe labeled
- 2:18two point zero clearly corresponds to the blog section
- 2:20in the site map, eliminating ambiguity. QA teams can then
- 2:22author testing scripts dedicated to specific page numbers, which
- 2:25keeps the testing process aligned with the actual site
- 2:27structure. By enforcing this rule, you prevent documentation
- 2:30from drifting out of sync as the project evolves. Wireframes and
- 2:32visual design elements must reference the specific page
- 2:34numbers established on the site map to provide a clear
- 2:36connection between the documents. This shared language
- 2:39allows designers to segment their inventory for handoff to
- 2:41developers with precision. Once the numbering logic is solid,
- 2:43the next step is defining the visual symbols that represent
- 2:46these pages.
- 2:52Once the numbering logic is established, we need a visual
- 2:55vocabulary to represent the pages themselves, which starts
- 2:57with drawing individual pages as plain rectangles. This standard
- 3:00format for representing a single page unit keeps the map clean
- 3:03and focused on structure rather than pixel-perfect design
- 3:05details. You might think of these as instances or views, but
- 3:08the page remains the meaningful unit of user experience on the
- 3:10web, so stick to the rectangle. It is the simplest and most
- 3:13commonly used format, ensuring everyone on the team understands
- 3:16exactly what a single node represents. For dynamic content
- 3:18areas, such as a common blog page created using a publishing
- 3:21system, you should use pagestacks to represent multiple
- 3:23pages of similar content that share one design template. These
- 3:26pages are designed once in a template, but users click
- 3:28through many different pages of content without leaving the
- 3:31original template design. By stacking them, you acknowledge
- 3:33the volume of content while respecting the single underlying
- 3:36structure. This is crucial for areas like blog posts or product
- 3:38listings, where the design is static but the content varies
- 3:41significantly. When a connection depends on a specific
- 3:43trigger, mark conditional connections with a dashed line,
- 3:46either as a connector or as a box around an area, to indicate
- 3:48dependence on another action or event. For example, a login
- 3:51screen might only appear after a failed registration attempt, so
- 3:54the dashed line clarifies that this path is not always active.
- 3:56This visual cue helps distinguish between standard
- 3:59navigation and conditional flows, preventing confusion
- 4:01about which paths are always available. Applying these
- 4:03visual cues to clarify the relationship between static
- 4:06templates and dynamic content flows ensures the map accurately
- 4:08reflects the user's journey. You are describing the use of
- 4:11pagestacks for dynamic content and dashed lines for conditional
- 4:14connections to maintain clarity. With the structure and visuals
- 4:16defined, the next step is ensuring this numbering system
- 4:19propagates to wireframes and QA scripts to prevent loss of
- 4:21traceability.
- 4:28Think about your content matrix and how you map copy to specific
- 4:31wireframe elements. If those documents drift apart, you lose
- 4:33traceability across the entire project. You recover from this
- 4:36by enforcing the zero point x through five point zero plus
- 4:38numbering system immediately. This ensures every artifact
- 4:41references the same decimal identifiers established on the
- 4:43site map. Consider how your quality assurance team authors
- 4:46testing scripts for specific tasks. They need to reference
- 4:48the exact site map page numbers to verify user progression
- 4:51accurately. When wireframes and visual design elements share
- 4:53this numbering logic, the connection remains clear. This
- 4:56prevents documentation from becoming disconnected as the
- 4:58project scope expands and changes. Visual designers also
- 5:01benefit from this synchronization when segmenting
- 5:03their inventory for developer handoff. By syncing design pages
- 5:06to specific site map numbers, they create a precise
- 5:08traceability path. You eliminate ambiguity by ensuring every
- 5:10visual element maps back to a unique decimal identifier. This
- 5:13allows teams to track features and functionality without
- 5:15confusion or redundant effort. Now, look at your current
- 5:18project documentation and identify where traceability
- 5:20might break down. Ask yourself if your wireframes explicitly
- 5:23reference the site map numbers you assigned earlier. If they
- 5:25don't, you are risking disconnected documentation that
- 5:28will cost time to recover later. Implement this system now to
- 5:30keep all project pieces neatly connected across teams. This
- 5:33decimal structure turns a static map into a living reference for
- 5:35every team member. You’ve moved from simple annotation to
- 5:38creating a unified language for your entire design process.
- 5:43Welcome to The Take. I'm joined by a fellow practitioner and
- 5:46together we're going to dig into How To Number and Annotate a
- 5:49Site Map — what it means in practice and what's worth
- 5:52remembering.
- 5:54[HOST] I found myself obsessing over those zero point X numbers
- 5:57for login screens today. It feels counterintuitive to give
- 6:00pre-home pages a numeric identity before the main
- 6:02structure even starts. [LEARNER] That zero prefix is a game
- 6:05changer for traceability. I used to treat auth flows as separate
- 6:08diagrams, but numbering them anchors them to the same system
- 6:11as the rest of the site. [HOST] Exactly, and that anchor
- 6:14prevents the map from feeling like disconnected islands. But
- 6:17the real friction usually happens when developers ask why
- 6:20they need to reference a decimal number in their code comments.
- 6:23[LEARNER] They hate it until they realize it saves hours of
- 6:26debugging. If a bug is reported on page three point two point
- 6:29one, they know exactly which nested template to check without
- 6:32guessing. [HOST] It turns the site map into a living reference
- 6:35rather than a static artifact. I wonder if AI tools are starting
- 6:39to respect these decimal hierarchies when generating
- 6:41wireframes from text prompts. [LEARNER] Not yet, but I’m
- 6:44seeing early signs. If you feed a structured site map with those
- 6:47IDs into an AI generator, it can maintain consistency across
- 6:50generated views much better than before. [HOST] That’s promising,
- 6:54because manual synchronization is where most teams lose the
- 6:57thread. The moment the wireframes drift from the map,
- 6:59the numbering system becomes useless unless everyone enforces
- 7:02it. [LEARNER] True, but the visual cues help bridge that
- 7:05gap. Using page stacks for dynamic content tells the AI or
- 7:08the designer that the structure repeats, even if the content
- 7:11changes. [HOST] It’s about creating a shared language that
- 7:14survives the chaos of iteration. Once that numbering logic is
- 7:17solid, the visual annotations just become the syntax for that
- 7:20language. [LEARNER] I’ll definitely start applying this
- 7:23to my next enterprise project. The complexity there demands a
- 7:26system that doesn’t break under scrutiny. [HOST] And that
- 7:29resilience is the whole point. We aren’t just drawing boxes;
- 7:32we’re building a traceable infrastructure for the entire
- 7:35design process.