Protecting contentHow we can realistically protect content whilst ensuring usability?
1. Forget about PDF permissions or text watermarks. These are too easy to get around.
2. Restrict distribution through deploying HTML content only. No PDF means there's nothing to
distribute except password access.
3. If your require PDFs, apply watermarks via image overlays. QPDF provides a good CLI function
for this that you can integrate into a pipeline.
```yaml
script:
- ./bin/qpdf
--overlay ./_build/develop/_static/watermark_draft.pdf
--repeat=1-z
--
--replace-input ./_build/develop/$DOC-DRAFT.pdf
```
We electronically control revisions for this topic and deploy it directly online. Any copies you generate from the latest revision are uncontrolled. Ensure you refer to the latest revision online when possible.