Bug #7601
Long online docs pages should be broken up
| Status: | Investigating | Start date: | 05/20/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Keywords: | puppetcamp-eu-2011 | Affected URL: | ||
| Branch: | ||||
| Votes: | -1 |
Description
Our very long docs pages are difficult to use. E.g., http://docs.puppetlabs.com/references/2.6.8/type.html
—
This ticket is a request for comment, coming out of a discussion at Puppet Camp EU, 2011. No promises whatever about implementation, but there were enough people interested to open a public discussion.
History
Updated by Daniel Pittman about 1 year ago
That would be great. Incidentally, we currently generate HTML named anchors in that document that overlap: some index entires go to the wrong place as a consequence. One page per type would totally solve that. :)
Updated by Martin Alfke about 1 year ago
Having one page is fair enough. Sometimes we need to switch from one resource to another. Maybe the TOC should always stay on top and get shortened? My Vote: -1
Updated by Thomas Bellman 11 months ago
The length is not a problem in itself, imo. But the formatting is … non-optimal. It actually becomes easier to read when I select “No style” as the page style in Firefox.
Here are a couple of concrete suggestions:
Don’t f*ck with the left margin! When using the page’s style sheet, the text becomes flush to my browser window’s left edge. Sucks for readability.
Don’t fck with sizes and things for headings. At least for me, the heading for each type is smaller* than the subheadings within each type, and even than the sub-sub-headings (like the name of each parameter).
Raise the “heading level” for most things; put the heading for each type inside h2 instead of h3, and the sections within each type should likewise be headed with h3, not h4.
Use definition lists (dl, dd and dt elements) for parameters, instead of a h5 heading with a paragraph after it.
Updated by Nick Fagerlund 8 months ago
We actually used to have a one-page-per-type version of the type reference. I burned it to the ground, because it’d been created by hand and was many many versions out of sync with reality (and had no concept of versioning at all, come to think of it).
I’m sure we could find a way to do it maintainably; it’s just a question of whether that would actually enhance the usefulness of the reference. That’s what I’d most like more feedback about.
I’m very interested in Thomas’s suggestion of using DL elements instead of h5s, especially since I think that would eliminate a lot of the element ID conflicts! I also think the Markdown dialect Jekyll is using has extended syntax for those, so that’s nice. I’ll look into this.
Updated by Nick Fagerlund 8 months ago
- File Puppet_-_change_type_refs_to_DLs.pl added
I’ve investigated wrapping these in DLs, and my verdict is that I like it VERY much. If you have a copy of the docs repo, you can pass one of the recent type refs through the attached perl script and then run rake generate and rake serve and view your local copy. And yes, that DOES fix the annoying #user-3 anchors and what-have-you. I’ll look into getting this into the generator and patching all the existing type references.
Updated by Nick Fagerlund 8 months ago
Pull request for the changes to Puppet core: https://github.com/puppetlabs/puppet/pull/117 …have tweaked the site CSS, and am about to get started on repairing the older refs.
Updated by Jacob Helwig 7 months ago
- Assignee set to Nick Fagerlund
Merged Nick’s branch into 2.7.x in commit:9d8f256d7448b90da9f18a0d1f2687d6db9dc275
Nick,
Not sure if this closes out the ticket or not, so I’m re-assigning to you for now.