Record uses rather than files alone
One image may appear in a hero, card and enlargement dialog. Recording only its name makes it easy to replace one view while leaving an old variant elsewhere. Document the source resource and the published uses.
Separate the image’s job from its format too. A photograph, an actual product view and a conceptual diagram need different reviews. Interface screenshots require checks of genuine functionality and language; an illustration should not be presented as product evidence.
Build a small useful register
Begin with a stable resource identity, subject, source, owner and usage locations. Add the available documentation about permitted use and restrictions without guessing what a licence allows. Unclear conditions need resolution before publication.
Across languages, distinguish neutral imagery from assets carrying text. Copying a Swedish screenshot into another folder does not make it English. Demonstration content, template names and alternatives require contextual review too.
| Register item | Question |
|---|---|
| Subject and function | What does the image help someone understand? |
| Source and permission | Where did it come from and what is established? |
| Language | Does the bitmap contain text? |
| Uses | Which pages and responsive variants are affected? |
Rehearse a complete replacement
Choose a fictional product asset in a test environment. Replace the main image, small variant and enlargement link. Read its caption and alternative, and check every language using it. An old asset returning on mobile means the replacement is incomplete even if desktop looks correct.
Check real dimensions and comprehension when scaled. A valid reference can still show the wrong language or panel. Someone needs to inspect the image’s actual content, not only verify that its URL responds.
Maintain resources without falsifying references
Assign approval of replacements and review of their uses. Do not delete a resource simply because its folder label is unclear; older content may still link to it. Genuine customer references should remain authentic rather than having their website images translated into a misleading representation. Use accurate localised surrounding explanations instead. The register should make these decisions traceable for the next editor, not merely make the folder tidy. Keep unresolved rights or language questions visible until someone can approve their resolution.