Closed Bug 352282 Opened 19 years ago Closed 19 years ago

Documentation Style Guide should encourage use of <link rel="..."> for intra-page, inter-page and intra-project navigation

Categories

(www.mozilla.org :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

References

()

Details

A growing number of browsers (Opera, Icab, Seamonkey, Lynx, NS 7, etc.) now implement Site Navigation toolbar for assisting intra-page navigation, inter-page navigation and, in the case of mozilla.org each project site, intra-project navigation. Firefox users can install 2 extensions implementing a Site Navigation toolbar. W3C Quality Assurance tip Use <link>s in your document http://www.w3.org/QA/Tips/use-links Link bars http://webcoder.info/reference/LinkBars.html Expected results: add an item at "Linking, Anchors, and URLs" of provided URL which would say something like: { Usage of <link rel="..." is encouraged. Linking section, linking entrance project page, linking table of contents, linking previous and next page within a serie of pages, etc.. help users make use of Site Navigation toolbar. Firefox users can install a Site Navigation toolbar as an extension; Seamonkey and many other browsers implement some sort of Site Navigation toolbar or a Link toolbar. Using <link rel="first" ...>, <link rel="previous" ...>, <link rel="next"> and <link rel="last" ...> should be used in pages arranged/ordered in a slideshow. } Seamonkey project pages, Access Mozilla and DOM project pages have up to a certain extent already implemented <link rel="...">.
Doh! Usage of <link> is encouraged in that document! "Use <link> elements to link to related documents." http://www.mozilla.org/contribute/writing/guidelines#meta Sorry for the bugmail! Resolving as WORKSFORME
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.