Examples
See how a library
holds together.
These structures and rules show ways of organising material. They illustrate the services; your own library is agreed around the assets you provide.
Example material
Folders and names
Library
Product information
Guides
product-guide_v02.pdf
Archive
A place with context
The folder route groups a guide with the product material it supports. Archive provides a distinct location for earlier material when the agreed rules call for it.
The filename uses a subject, a version and an extension: product-guide, v02, .pdf. The naming pattern explains which part changes when a later version is added.
Tags and an index
An index puts descriptive terms alongside filenames. Here, material type and subject make different assets recognisable without relying on their extensions alone.
| File | Material type | Subject | Version / status |
|---|---|---|---|
| product-guide_v02.pdf | Guide | Product information | v02 / Current |
| product-photo_front.jpg | Image | Product information | Front view |
| product-overview_v01.pdf | Overview | Product information | v01 / Current |
Versions and additions
Archive
product-guide_v01.pdf
Earlier version, retained separately.
Current
product-guide_v02.pdf
The version identified for present use.
For an addition: choose the subject folder, use the agreed naming pattern, then record the version or status. The guideline makes the next file part of the same system.
Location. Description. Version.
A folder tells you where to look. An index explains what is there. Version rules help you recognise which material to use.
Your guidelines connect these decisions: where an asset belongs, which terms describe it, and how an older copy is handled. The final structure follows your materials and the written project scope.