Apply a decimal numbering system to site maps to synchronize wireframes, content matrices, and QA scripts. Use pagestacks for dynamic templates and dashed lines for conditional connections to maintain traceability across project documentation.
Learning Objective: By the end of this lesson, learners will be able to apply a decimal numbering and annotation system to site maps to ensure cross-document traceability.
You likely already sketch site maps, but you might overlook the pages that sit before the main entry point. These pre-home pages include login screens, register screens, or even Flash preloaders that users encounter first. We assign these specific entry points numbers in the zero point X format to clearly distinguish them from the rest of the structure. This simple step establishes the baseline for traceability before the main navigation sequence even begins. By capturing every decision point in this zero point X sequence, you ensure nothing gets lost in the transition. It creates a clean anchor for everything that follows, allowing other teams to reference these early interactions accurately.
Key Points:
Identify pages occurring prior to the home page, such as login screens, register screens, or Flash preloaders.
Assign these pre-entry points numbers in the 0.X format to distinguish them from the main site structure.
Recognize that this step establishes the baseline for traceability before the main navigation begins.
Ensure all decision points before the main entry point are captured in this 0.X sequence.
Once those pre-home pages are secured with the zero point X format, you designate the home page as one point zero to serve as the central anchor of the site map. This number acts as the origin point for every other page in the structure, so when you start numbering, you are building outward from this single, stable reference. It prevents the map from feeling like a collection of disconnected islands, because everything ties back to this primary entry point. You treat the home page as the trunk of the tree, and every other section branches off from it in a logical, hierarchical sequence.
From that anchor, you assign whole numbers to primary sections branching from the home page to establish the main navigation levels. You might label the blog section as two point zero, the about page as three point zero, and the work portfolio as four point zero. This creates a clear, linear progression that mirrors how users perceive the major areas of the site. By using whole numbers for these top-level categories, you create distinct buckets that are easy to identify and reference during design discussions. It’s a simple system, but it provides the structural integrity needed for complex sites.
When pages nest deeper within those primary sections, you use decimal extensions for pages nested within primary sections to show their subordinate relationship. For example, if you have a terms and conditions page that lives under the home page, you number it one point zero point one. This notation immediately signals that the page is a child of the home section, rather than a standalone entity. You can continue this pattern indefinitely, adding decimals for every level of depth, which means the number itself tells you exactly where the page sits in the hierarchy.
The real power of this system emerges when you propagate these specific numbers to content matrices, task flows, wireframes, visual design inventories, and QA testing scripts. You apply the same numbering logic across all project documents to maintain traceability of features, functionality, and content. This ensures that a wireframe labeled two point zero clearly corresponds to the blog section in the site map, eliminating ambiguity. QA teams can then author testing scripts dedicated to specific page numbers, which keeps the testing process aligned with the actual site structure.
By enforcing this rule, you prevent documentation from drifting out of sync as the project evolves. Wireframes and visual design elements must reference the specific page numbers established on the site map to provide a clear connection between the documents. This shared language allows designers to segment their inventory for handoff to developers with precision. Once the numbering logic is solid, the next step is defining the visual symbols that represent these pages.
Key Points:
Designate the home page as 1.0 to serve as the central anchor of the site map.
Assign whole numbers to primary sections branching from the home page (e.g., 2.0 Blog, 3.0 About, 4.0 Work).
Use decimal extensions for pages nested within primary sections (e.g., 1.0.1 for Terms & Conditions under Home).
Propagate these specific numbers to content matrices, task flows, wireframes, visual design inventories, and QA testing scripts.
Once the numbering logic is established, we need a visual vocabulary to represent the pages themselves, which starts with drawing individual pages as plain rectangles. This standard format for representing a single page unit keeps the map clean and focused on structure rather than pixel-perfect design details. You might think of these as instances or views, but the page remains the meaningful unit of user experience on the web, so stick to the rectangle. It is the simplest and most commonly used format, ensuring everyone on the team understands exactly what a single node represents.
For dynamic content areas, such as a common blog page created using a publishing system, you should use pagestacks to represent multiple pages of similar content that share one design template. These pages are designed once in a template, but users click through many different pages of content without leaving the original template design. By stacking them, you acknowledge the volume of content while respecting the single underlying structure. This is crucial for areas like blog posts or product listings, where the design is static but the content varies significantly.
When a connection depends on a specific trigger, mark conditional connections with a dashed line, either as a connector or as a box around an area, to indicate dependence on another action or event. For example, a login screen might only appear after a failed registration attempt, so the dashed line clarifies that this path is not always active. This visual cue helps distinguish between standard navigation and conditional flows, preventing confusion about which paths are always available.
Applying these visual cues to clarify the relationship between static templates and dynamic content flows ensures the map accurately reflects the user's journey. You are describing the use of pagestacks for dynamic content and dashed lines for conditional connections to maintain clarity. With the structure and visuals defined, the next step is ensuring this numbering system propagates to wireframes and QA scripts to prevent loss of traceability.
Key Points:
Draw individual pages as plain rectangles, the standard format for representing a single page unit.
Use pagestacks to represent multiple pages of similar content that share one design template, such as blog posts or product listings.
Mark conditional connections with a dashed line, either as a connector or as a box around an area, to indicate dependence on another action or event.
Apply these visual cues to clarify the relationship between static templates and dynamic content flows.
Think about your content matrix and how you map copy to specific wireframe elements. If those documents drift apart, you lose traceability across the entire project. You recover from this by enforcing the zero point x through five point zero plus numbering system immediately. This ensures every artifact references the same decimal identifiers established on the site map.
Consider how your quality assurance team authors testing scripts for specific tasks. They need to reference the exact site map page numbers to verify user progression accurately. When wireframes and visual design elements share this numbering logic, the connection remains clear. This prevents documentation from becoming disconnected as the project scope expands and changes.
Visual designers also benefit from this synchronization when segmenting their inventory for developer handoff. By syncing design pages to specific site map numbers, they create a precise traceability path. You eliminate ambiguity by ensuring every visual element maps back to a unique decimal identifier. This allows teams to track features and functionality without confusion or redundant effort.
Now, look at your current project documentation and identify where traceability might break down. Ask yourself if your wireframes explicitly reference the site map numbers you assigned earlier. If they don't, you are risking disconnected documentation that will cost time to recover later. Implement this system now to keep all project pieces neatly connected across teams.
This decimal structure turns a static map into a living reference for every team member. You’ve moved from simple annotation to creating a unified language for your entire design process.
Key Points:
Prevent loss of traceability by enforcing the 0.X through 5.0+ numbering system across all project documents.
Recover from disconnected documentation by ensuring wireframes and QA scripts reference specific site map page numbers.
Synchronize visual design elements with site map pages to allow designers to segment inventory for developer handoff.
Maintain alignment between content matrices and wireframe elements using the established decimal identifiers.