|  |
| |
Our general standards for Web page navigational links is given in the TCC Documentation Guidelines.
Since the pages we generate will be linked to from the
PyStyler part of the TCC web, they should be similar in
style. Hence we will use the module described in tccpage2.py: Dynamic
generation of TCC-style web pages with lxml.
The exact sequence of top and bottom links is flexible, and depends on the expected user workflow, especially for dynamically generated pages such as the ones we are building. Here are the expected use cases for our structure:
The author of a set of Web pages wants to see which pages are actually being visited. From the index page, they will click on the index of personal (or official) pages, then the first letter of the account or directory name, then on the account or directory name.
An author wants to see which of their pages are the most popular. They will start on the hit parade page, and use their browser's text search function to search for their URL. This search will visit their most popular pages in descending order of popularity.
A user has an idle curiosity about what pages are popular on this server. They will click to the hit parade.
Here are the navigational features we'll use, and where they will lead.
: Next page in sequence. None of our use cases really call for sequential visits to either the letter index pages or the personal or official pages. This will be a dummy link.
For the same reason, the button will be a dummy link.
There should be a link that gives the user a place to jump up in the structure. For all subpages of the index page, even the individual personal or official URL reports, this link will go back to the index page and have the text . For the index page, this link will be missing, as it is covered by the next link type.
For those who are really lost, we'll provide a link that goes to the TCC homepage.