A materials centre: every file needs a version, a purpose and a reason to download it
Help people choose the right file with clear purpose, product edition, document revision and accessible download information.
Article language: English

In this article
A partner calls for a drawing of the Rzeka 80 stand. They receive a link to “Downloads”, containing a catalogue, a folder, a presentation, instructions and a file called “Rzeka_revised_final2.pdf”. Three documents show the same stand on their covers. None says before opening whether it concerns the wide-base version. Soon the phone rings again. The library works, the files download, and the person still does not have the drawing.
In this hypothetical example the problem is not the lack of a search box. What is missing is information that lets someone rule out the wrong material. An attractive grid of covers shortens the route to a download, but not necessarily to the right file. A person can efficiently take away a document they cannot use.
Design a materials centre starting with the sentence “I'm looking for something so I can...”. Decide on folders, cards and filters afterwards. A drawing for fitting the stand into a recess, a photograph for a partner's shop and first-assembly instructions share a product but serve different tasks. The resource should reveal that difference before someone uses their data allowance on the whole catalogue.
One product does not mean one set of documents
For our stand, prepare a short list of real situations. A partner checks dimensions before speaking to a customer. An installer looks for the assembly sequence. A seller wants to show a chosen colour in their shop. Each may type “Rzeka 80” while expecting a different result. Do not require them to know the names of the departments that produced the materials.
In the resource list, describe type and purpose in ordinary words: “Dimensioned drawing for planning the space”, “Wide-base assembly instructions”, “Product photographs on a white background”. “Technical materials” alone does not say what is inside. Equally, “Comprehensive documentation for our modern collection” takes space without helping someone choose.
Identify the model from a marking the recipient actually has: a name from an order, a packaging label or a number on the product. If Rzeka 80 has two constructions, show the distinguishing feature and how to check it. Do not make people guess the production year from a photograph's shade. The documentation owner must confirm which markings correspond to which materials.
A useful division might have only three entry points: “Before choosing”, “Assembly and use”, and “Partner materials”. Do not treat this as universal ready-made navigation. If everyone arrives with a model number, choosing the product may be a better start, with purpose appearing beneath it. The structure follows the first information a person has, not the number of folders on the company drive.
Test search with markings copied from orders, including spaces and hyphens. If the catalogue says “Rzeka 80” and the label says “RZ-080”, both should lead to the same model once confirmed to identify it. The result must not, however, select a similar construction on its own when the marking is incomplete. Show candidates and the feature that lets the recipient distinguish them. Keep the entered query on screen so they can correct it without retyping the whole number. Search becomes an entry to an organised collection, not a replacement for knowing which products the files belong to.
On a specific product page, show its materials without making someone select the whole collection again. Keep the model name visible so a person arriving from search can check the context. When a document helps someone start using an item after unpacking, first steps with product instructions (in Polish) also describes the entry path. The library should lead to those instructions instead of requiring the user to reconstruct a route from the home page.
A resource card should answer before the click
Show the title and scope first, followed by information that helps assess the download. In our example that is “Rzeka 80 - dimensioned drawing, wide base”, Polish, an edition identifier and a PDF with its size. If the file covers the entire family, say so and indicate where the desired model appears. A family cover should not masquerade as a separate drawing.
The GOV.UK Publishing Design Guide's attachment component describes a title, file format and size, online viewing and information about requesting an accessible format for people with disabilities. It is one concrete example of describing a download before opening the file.
In our library, add the reason to choose the material: what task it serves and what it does not cover. “External dimensions, without mounting-hole spacing” can be more useful than a larger thumbnail. Do not add that caveat to every file just in case. Record the real boundary of the specific resource when it can change the recipient's decision.
Separate three labels that are easily thrown into one “version” field:
- Product edition identifies the construction to which the material applies.
- Document revision identifies which state of its content is being provided.
- Language identifies the language in which the recipient will read that document.
A newer revision of instructions does not necessarily describe a newer construction. It might only correct an illustration caption. Polish instructions issued later than English ones do not thereby become instructions for another product. If these field names are unclear even to the editor, agree on their meanings with the material owner first. The interface cannot repair a contradictory classification with prettier labels.
Also consider the file name after download. The page title may look elegant, but the recipient's folder will contain “download_83.pdf”. Establish a recognisable naming convention suited to use and versioning. Someone sending a drawing to a colleague should still be able to identify the model and material. They do not need to read the whole history of internal approvals embedded in its name.

Get size and format from the actual resource rather than re-entering them by hand every time it is replaced. Schema.org's MediaObject description separates size, data address and format into contentSize, contentUrl and encodingFormat. The existence of those fields alone does not establish that a file is correct or current.
In the library model, separate the material's description from its individual files. The same drawing may have a version for reading and a file intended for further work. The recipient chooses the purpose, then the appropriate form. Do not create two nearly identical cards without explaining the difference, or people will compare names instead of using the documentation.
A bundled download makes sense when someone actually needs the whole set. Next to the button, show what the archive contains and which edition the set concerns. A change to one drawing then also requires checking the bundle. Otherwise the individual download will provide the new document while the convenient “Download everything” button supplies its predecessor. For extensive sets, include a short file list inside that agrees with the page description. Someone extracting the archive a week later should still know where the materials came from and whether they form one set.
Aeneia Design As part of a website project, we can organise the materials library, design resource cards and the path from a product to the right download. The scope starts with documents and markings confirmed by their owner. Design a clearer materials centre
“Current” for whom and for what?
On Monday the stand's base changes. A new drawing reaches the site and the old one disappears from the default list. On Tuesday a customer who bought earlier looks for the dimensions of their own item. Replacing everything with the new version would be convenient for an administrator but wrong for the recipient. Material current for new sales may be inappropriate for an older product.
Show material for the selected edition and mark older revisions separately with their scope. A grey “Archive” label is insufficient if a person does not know whether the document still fits their stand. “For the narrow-base construction” tells them more. The content owner decides whether a document remains approved for use; the design determines where and how that decision is shown.
A material page may retain a stable address and show files currently offered. A separate address for a specific edition points to an exact revision. Agree what a link sent to a partner means: “always check the latest version” or “open this approved state”. Do not mix the promises. When a file's meaning changes, silently replacing it at a familiar address can mislead someone returning to a bookmark.
Retaining an older resource also requires a decision. A document withdrawn from use should not reappear as an ordinary result when its exact name is entered. The distinction between history and active instructions in archiving company knowledge (in Polish) is useful here. In a downloads centre apply it in results, on the document page and in the successor's description, not only on the administrative list.
Sometimes there is no successor. Instead of sending someone to a general catalogue with “Download current”, show that no equivalent exists and the right way to clarify the issue. A general catalogue does not become a substitute for a drawing merely because it is the only new PDF. Contact should concern the specific material or model so the person does not need to repeat the whole story.
A similar order applies to a partner logo package (in Polish). A set of files must be identifiable by purpose and marking, and an older mark variant should not masquerade as the recommended choice. A library can contain different kinds of resource without imposing identical fields on all of them. A construction drawing and a mark for a dark background need different explanations.
Do not force a download to discover that the answer is missing
When someone needs one value, consider showing it in the page text beside the document. The PDF can still serve printing or sharing. PDF or HTML on a company website (in Polish) explores the choice. In a materials centre the question is whether a download is needed for the task or has become a compulsory stop between a question and a one-sentence answer.
A preview helps assess contents if it shows the right part of the file. A first-page thumbnail with a decorative photograph does not establish that mounting-hole spacing is inside. A scope description may be faster and clearer. For a substantial resource, also lead to the specific chapter in the online version; contents and returning to a place in a long guide (in Polish) develops how to organise that reading.
A no-results state should retain the selected product and filters. If there is no drawing for the wide base in the chosen language, show that exact absence and the available options. Do not silently remove the language restriction and display a list as if it satisfied the query. If a document exists in another language, the recipient can choose it knowingly.
Also check what happens after a click on a phone. Did the document open in the browser or did a download begin? The action label should match the agreed behaviour. If transfer fails, the person must still see the selected material's name and be able to retry. Do not send them to an empty screen from which they return to the start of the catalogue. A download alone is not proof that the document was opened and fulfilled the task.
Test the library without giving the route. Ask a person to find a drawing for an older construction and then identify the file they would send on. Observe not only the first click but also the downloaded file name and confidence in the choice. A second trial can concern material that has not been published. The person should recognise the absence rather than treat a neighbouring document as sufficiently similar.
For discussion with the implementer, prepare several actual resources: two similar models, two revisions, a missing translation and a withdrawn item. They can support acceptance of the layout and behaviour as part of an Aeneia Design project. When a partner chooses the right drawing without opening five trial files, the materials centre has done its job. The next call can be about the order.










