Currently the Publican generated site lists all books in a product alphabetically. I would like to be able to organize the books by sub-groups like Administration, Reference, etc. Each sub-group would have a heading and a breif description of the group. Books in each group should be able to be listed in a writer specified order - defaulting to alphabetical listing.
At a basic level this is already achievable by using sort_order, simply assign each of the book groups a distinct sort_order and the books will be sorted by sort_order, ascending, then Alphabetically. e.g. if you had two groups of books "admin" and "user" and you gave all the "admin" books a sort_order of 62 and all the "user" books a sort_order of 11, then in the list all of the "user" books would be listed before any of the "admin", and both sets would be internally sorted in alphabetically order. The default sort_order is 50, so any other books would be listed between those two groups, again in alphabetical order. If this isn't enough then please detail the exact behavior required.
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
(In reply to Jeff Fearn from comment #2) > At a basic level this is already achievable by using sort_order, simply > assign each of the book groups a distinct sort_order and the books will be > sorted by sort_order, ascending, then Alphabetically. > > e.g. if you had two groups of books "admin" and "user" and you gave all the > "admin" books a sort_order of 62 and all the "user" books a sort_order of > 11, then in the list all of the "user" books would be listed before any of > the "admin", and both sets would be internally sorted in alphabetically > order. > > The default sort_order is 50, so any other books would be listed between > those two groups, again in alphabetical order. > > If this isn't enough then please detail the exact behavior required. The groups of books need to have headings and descriptions, so: Administration These guides describe how system administrators configure and maintain [product] User These guides describe how end users do X and Y with [product]
Do the headings and descriptions need to be translated?
(In reply to Jeff Fearn from comment #5) > Do the headings and descriptions need to be translated? Definitely
Initial version checked in. It only applies the new content to the langauge index page. Need to add it to the other navigation pages and decide how to apply it to the menu. Need to document how it al works in the PUG. Need to stop the splash pages pulling in the brand CSS file. To ssh://git.fedorahosted.org/git/publican.git 520e668..3dc16dc HEAD -> devel
To ssh://git.fedorahosted.org/git/publican.git 3217d23..c3721e7 HEAD -> devel
Verified in publican-3.9.9-0.fc19.t18.noarch
This comment was flagged a spam, view the edit history to see the original text if required.