Yes, every release checklist for product documentation should include a box for a pretty printable version, such as a PDF. It covers several usability edge cases discussed here. Ideally, a technical writer acting as a user advocate would track this. However, this will often fall through the cracks in organizations without a full-time writer. Good advice here for developers and other non-writers tasked with documentation work.
Yes, every release checklist for product documentation should include a box for a pretty printable version, such as a PDF. It covers several usability edge cases discussed here. Ideally, a technical writer acting as a user advocate would track this. However, this will often fall through the cracks in organizations without a full-time writer. Good advice here for developers and other non-writers tasked with documentation work.
When I get asked questions like this I now answer "Well this is a community project so feel free to get involved to improve the situation".
And that's the last I ever hear from them!