Use a clear working copy name
Consistent descriptive names and version labels make file organization easier.
Sources for this point: Acquia file naming guide.
Brand_Purpose_Background_Size_Version.extension
Luma_Web_Dark_600px_V02.png| Field | Meaning in this example |
|---|---|
| Brand | Luma is the fictional project name. |
| Purpose | Web says where the copy is meant to go. |
| Background | Dark names the intended surface. |
| Size | 600px records this copy's pixel width. |
| Version | V02 identifies this prepared version. |
| Extension | png names its file type. |
Use only fields that help your team. A pixel width may suit a website copy but not a vector master. A clear version label is more useful than names such as final final new.
Keep originals and working copies separate
Retain the original filenames and README together. The suggested pattern is for copies you prepare for a purpose. It does not prove that a file has clear pixels, true vector shapes or the correct print setup.
Identify the approved set
First record which artwork was actually approved, by whom when known, and on what date. Do not use the file modification date as a substitute for approval. Keep drafts and experiments separate from the chosen identity.
- Which project does this set belong to?
- Which wording and layout were approved?
- Which version is the current one?
- Where is the original delivery and its file guide?
If nobody can identify the approved version, settle that before renaming copies. A tidy folder of uncertain marks is still uncertain.
Group files by purpose
Luma/
Approved_originals/
Web_copies/
Print_jobs/
Icons/
Archive/This is an example folder plan. Keep the original delivery inside Approved_originals. Put task copies in the matching folder. Give each print job its own note and proof rather than mixing it with every other handoff.
LogoTidy kit files share a common prefix. Keep different projects in separate folders so matching names do not overwrite one another. Copy files into your working area instead of renaming the originals.
Use the included file guide
The LogoTidy sample shows file choices and a usage README.
Sources for this point: LogoTidy sample file kit.
- Read the file guide before deciding which copy belongs in a task.
- Compare its listed names with the actual files you received.
- Note any conditional component that is absent from this identity.
- Check the intended background and layout.
- Ask for missing information rather than invent a purpose from the extension.
If a kit lacks a separate symbol, do not label a crop as an approved symbol without a design decision. If it lacks a stitch file, do not treat an SVG as a machine program.
Send a short handoff note
| Field | What the recipient needs |
|---|---|
| Approved version | The exact selected identity and version. |
| Attachment | The copy intended for this task. |
| Destination | Website header, printer job or other named use. |
| Background and size | The planned surface and dimensions. |
| Question | Anything the recipient still needs to confirm. |
Send the useful requested files rather than the whole archive. Ask the receiver to confirm it opened the right version. Finish when a person can find the current original, choose the task copy and understand the handoff without guessing.
Sources
These sources support the points linked above. Each date shows when we checked that source.
- Acquia file naming guide
Consistent descriptive names and versions help organize files Checked . - LogoTidy sample file kit
LogoTidy displays example logo files and layouts Checked .