Bug 3869 - "documentation" page "entire set of manuals" is incorrect link
Summary: "documentation" page "entire set of manuals" is incorrect link
Status: RESOLVED FIXED
Alias: None
Product: Website
Classification: Infrastructure
Component: web-content (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: Q1
Assignee: Jeff Osier-Mixon
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-02-07 23:54 UTC by Dave Stewart
Modified: 2013-03-20 21:02 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Stewart 2013-02-07 23:54:47 UTC 
Go to https://www.yoctoproject.org/documentation/current

Click on the link marked "entire set of current manuals". Sends you to this same page rather than the super manual.

Hey, can we also please explain the super manual better? 

" For other manuals, take a look at the entire set of current manuals,"
" Click on this link to see our entire set of manuals as a single book"
Comment 1 Jeff Osier-Mixon 2013-02-12 00:45:40 UTC 
I added the mega-manual to the list of available docs and removed the link, so it should look better now. Please take a look so I can close the bug.
Comment 2 Dave Stewart 2013-02-12 04:03:05 UTC 
Actually, the "complete documentation set" is kind of buried in the middle of the list. It took me several times before I found it. Could you please put it at the top of the page with some additional call-outs?  

Sorry to be so picky...
Comment 3 Jeff Osier-Mixon 2013-02-12 04:54:01 UTC 
No problem at all on the pickiness - specificity is golden.

Do you think the Complete Docset should be actually at the top of the list? Perhaps underneath the Quick Start Guide would be better?  

In the future we can readdress how the documents are presented in order to make some more prominent than others. I'll open a second bug for that.
Comment 4 Jeff Osier-Mixon 2013-03-20 21:02:54 UTC 
This is fixed