Organize a website resource library

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

Describe each resource by task, audience, prerequisites and limits. Fictional example: “Prepare for a renovation appointment” is a page for homeowners, with questions to ask and no automatic estimate. For files, also state format, size and version; an HTML page should provide essential information before opening an external destination.

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

Assign an owner and review trigger to each resource. Fictional example: guidance from 2024 is replaced but remains linked in emails; its page should explain its status and point to the current version. Update search, categories, links and translations together. Keeping a useful archive requires clearly distinguishing it from applicable guidance.

Check broken downloads and documents citing outdated rules or figures regularly. Removing a file without repairing incoming links leaves the library incomplete.

Fictional library example: four editions represent two logical resources, REF-7 and REF-8. Only one edition is both current and approved in this dataset. REF-7 remains at v1 in English while French has reached v2: disclose the gap, the available language and the chosen fallback. Do not describe all four rows as current resources or present the older translation as equivalent to the current edition.

Keep one reference record per resource and associate its editions, languages and replacement links with that record. Distinguish publication date, effective date where applicable and editorial review date. Changing a date does not demonstrate a substantive review. W3C data versioning guidance provides a traceability reference; applying it to this document library is an editorial decision that must fit the material.

• Version and status visible.
• Language copies aligned.
• Links and facts reviewed regularly.

Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

• W3C : Data Versioning

  W3C, consulted 22 October 2026: data version indicators and history. These identifiers and statuses are fictional.