3 ms·
> we wanted to provide our clients with a PDF guide How often do you think they printed this guide, and of those instances, how often do you think they cared i
by hunter2_ 3y ago
> we wanted to provide our clients with a PDF guide
How often do you think they printed this guide, and of those instances, how often do you think they cared if the layout/pagination/etc. was identical to seeing it electronically? If that number is sufficiently low, I'd argue that the guide should've just been HTML.
- mypetocean 3y agoUsers seldom or never printed it. I was told that we needed it (a computer requirements document) in PDF for legal reasons. I pushed back and legal confirmed that they did, in fact, need it to be in PDF format. I suspect it had something to do with accreditation, accessibility, and/or student aid policy compliance, since this was a school. But legal may also have found the relative transience of HTML documents to be a liability if a student threatened suit based on frequently changing policies, because I updated the requirements document twice yearly. PDFs made versioning very straightforward from a legal perspective, because the filename and download link always "needed" to be different between versions, without requiring dev work.