Naming and organizing assets

A project's asset library grows fast. A few habits keep it usable.

Naming conventions

• Use lowercase with dashes: team-logo-red.png, not Team Logo Red.PNG.
• Include the content, not the context: logo-premier-league.png tells you what it is; pl-logo.png does not age well when you get a second league.
• For variants, put the variant last: logo-white.png, logo-black.png, logo-color.png.

Swapping versus re-uploading

• Upload a new file to change a logo everywhere — but only if the filename is different. Templates reference specific paths; uploading a new file with a new name leaves the old templates pointing at the old image.
• Overwrite by re-uploading with the same filename to update in place. Every template that used the old image now uses the new one.

Cleanup

There is no built-in "unused assets" view yet. For spring cleaning: list assets on the project page, cross-reference with template bindings, remove what no one uses.

Cross-organization re-use

Assets are per-organization. Uploading the same logo twice (once per org) is acceptable; direct sharing between orgs is not supported.