"Give me six hours to chop down a tree and I will spend the first four sharpening the axe." - Abraham Lincoln
You We may be testing an existing tree (e.g. the structure of your our existing site) or trying out some new trees (revised, or completely rethought) to see how well they work.
In either case, your our tree will need to be prepared for testing. In many cases, this is just a matter of minor housekeeping (importing the tree into a spreadsheet, excluding certain headings like “Search”, and so on), but sometimes you we need to make some bigger decisions about your our tree (e.g. whether to prune a large tree).
In this chapter, we’ll cover everything you’ll we need to consider when preparing your a tree for testing.
Working in an electronic format
- overview text here
Using a spreadsheet
- overview text here
or text file, sourcing the content, using the right format
Which part of the tree?
- overview text here
How to cut big trees down to size for testing
Which headings to include/exclude?
- overview text here
Global nav, footer links, utility links, etc.
Spotting missing content
- overview text here
Content that doesn't have a page of its own might be missed
Dealing with shortcuts and duplicated content
- overview text here
Handling topics that appear in more than one place
Breaking up double-level topics
- overview text here
Handling multi-level navigation (e.g. mega menus)
Using link names instead of page titles
- overview text here
Link names represent the nav better than page titles do
What to call “Home”
- overview text here
In certain cases, "Home" may cause problems
Transferring the tree to
youra testing app
- overview text here
Sanitizing text, importing to a tool, and randomizing subtopics