Technical document libraries: what belongs on the page or in a PDF?
A buyer checks a product dimension on a phone and finds only a large catalogue download. Another visitor needs to save an installation drawing on a desktop. Rather than asking one PDF link to serve both tasks, give the product page and document library different responsibilities. The example below is an original planning scenario for an imaginary manufacturer.
Start with the first decision a visitor needs to make
Imagine an air grille product. A visitor initially needs its product family, intended application and available size options. Put that concise information into readable page content. Installation drawings, printable data sheets and signed documents can remain separate downloads. Checking basic suitability and saving a formal document then become distinct, understandable actions.
GOV.UK publishing guidance distinguishes regularly updated guidance from documents tied to a particular point in time. Apply that distinction thoughtfully to a commercial catalogue: the update pattern of your product matters more than copying a government publishing format.
Turn download labels into selection information
Replace five identical “Download” links with a document name, language, file type and size. “M-24 installation drawing — English — PDF — 420 KB” is an illustrative label, not verified product data. Measure the actual file before publishing its size. A clear label lets someone decide whether a download is relevant before opening it.
Keep a data sheet separate from a certificate. Designers should not infer a certificate’s scope or validity; obtain an approved description from its owner. If changing the interface language does not change the document, do not imply that a translated file exists.
Distinguish the current revision from the archive
Assign a content owner, publication or revision date, and version identifier to each document. When a new revision arrives, decide what should happen to the previous one. Existing installations may still need historical instructions. Listing archived and current documents identically can make the wrong choice look reasonable.
A stable product page can point visitors to the current file. Separately decide how old direct download links behave. Do not silently replace a historical document with one for a different product. A newly displayed date is not evidence that the technical content has been approved.
Try a small library before importing the full catalogue
Build the first layout with three products and two documents for each. Ask one person to find a dimension and another to locate the English installation drawing. Record where they hesitate. If the team needs to explain a category label during the exercise, improve that label before extending the structure to hundreds of files.
Inspect a sample document record
Finish with link and maintenance checks
Open a document on a phone, return to its product page and check the other language version. Also test the response when a file is removed. A tidy arrangement of cards does not prove that each link reaches the correct revision. Give the person maintaining the library a short procedure they can repeat after every update.
Compare this approach with our catalogue and online-store guide and examine presentation options in the project archive. Include document ownership and maintenance steps in the website design scope. Publish technical values only after the appropriate team approves them.
Frequently asked questions
Must all PDF content become HTML?
No. Put initial evaluation information on the page and provide documents for saving or detailed technical use. Choose according to the task rather than a blanket format rule.
Should historical technical files be deleted?
First establish whether existing installations still need them. If they do, retain clearly labelled revisions in an archive and distinguish them from current product documentation.