Start from use cases
Group resources by task or question, then use document type only when it helps selection. Someone planning a project may seek a checklist rather than a “white paper”. Keep the number of categories small enough to understand.
Avoid placing separate copies of the same file in several sections. Link one source entry from relevant categories. The content operations guide helps assign an owner and review cycle.
- Categories reflect needs.
- One source entry per resource.
- Editorial owner known.
Explain before download
Each resource needs a precise title, summary, audience, format, file size and version date when it changes. Show a brief preview or key topics for a long file. Link wording should clearly announce what opens.
The accessible documents guide covers structure, links and formats. An HTML page summarising essential facts also helps people unable to open the file.
- Format and size stated.
- Useful summary before opening.
- Essential facts available in HTML.
Test search and filters
If volume warrants them, offer search tolerant of common wording and a few reliable filters. Show result count, active criteria and a no-results state that helps people restart. A short list does not need a complex filter interface.
Test keyboard navigation, phone layout and long titles. The filters guide shows how to avoid needless combinations.
- Search fits volume.
- Filters use reliable data.
- No-results state explained.
Keep versions current
State who reviews content and when it should be replaced. For a new version, update entry, file, sharing links and translated versions together. An older resource may remain available if its status is explicit.
Check broken downloads and documents citing outdated rules or figures regularly. Removing a file without repairing incoming links leaves the library incomplete.
- Version and status visible.
- Language copies aligned.
- Links and facts reviewed regularly.