GitBrand
  1. Home
  2. Guides
  3. Organize brand assets

Guide 03

How to organize brand assets your team can actually find.

Organize brand assets by separating the current identity from historical work, naming variations by purpose, adding guidance next to each decision and sharing one maintained reference. Start with what people request most, then expand from real needs.

By the GitBrand teamUpdated September 23, 20266 min read

What you haveWhat people can find
final-v7-approved-new.pngacme-wordmark-dark-on-light.svg
logo (1) copy.pngacme-symbol-white-transparent.png
LOGO_FINAL_FINAL2.aiacme-lockup-horizontal-black.svg
brand colours latest.docxColors: Forest #456455, Sand #E9C6A3
fonts.zipFonts: Inter (Google Fonts, free to use)

  1. Gather and identify the current set

    Collect assets from whoever owns the identity: the designer, the agency, the founder’s laptop. Confirm which logo, palette and typography are current before uploading anything.

    Move superseded versions to a clearly separate archive in your storage. Do not delete source files just because they are not part of the everyday kit; the archive is where they live, the kit is where the current identity lives.

    ResultOne folder of current files, one archive, nothing in between.

  2. Organize around the task

    A colleague wants a logo for a slide or a color for a page, not a tour of your project folders. Group the essentials into logos, colors, typography and resources, which is how GitBrand structures a repository.

    For several brands, use a separate repository for each so similar filenames never collide and each link can have its own access level.

    ResultFour groups that match the questions people ask.

  3. Replace ambiguous names

    final-v7-approved-new records the production history and nothing else. Describe the brand, the asset and the background instead, and write the convention down so the next contributor follows it.

    • A consistent brand prefix
    • Full logo, symbol and wordmark told apart
    • Light and dark background variants labelled
    • No draft labels in the shared collection

    ResultAnyone can pick the right file without opening it.

  4. Put instructions next to the decision

    Add a short note where people choose: which logo, which type role, what the secondary color is for. In a repository that is the description on each logo, the name on each color and the FAQ section for the questions that repeat.

    Link the long guideline document as a resource. Use the questions people actually ask to decide what to document next; do not write rules for hypotheticals.

    ResultThe answer sits beside the asset, not in a PDF nobody opens.

  5. Share, check and maintain

    Pick the access level for the audience: public, password-protected or member-only, all on the same link. Put the link where work starts: briefs, onboarding documents, handoff messages.

    Assign a maintainer and review the library whenever the brand changes. Tell people what changed and ask them to refresh local copies. A shared reference only works when someone keeps it accurate.

    ResultOne URL, one owner, and a habit of keeping it current.

Folder tree versus repository

A shared drive mirrors how the work was produced. A repository mirrors how the brand is used. The same files, arranged for the person asking instead of the person who made them.

The shared drive

Organized by project history

Brand/
├── Logos/
│   ├── final/
│   │   ├── logo_final.png
│   │   └── logo_final_v2.png
│   ├── old/
│   └── LOGO_FINAL_FINAL2.ai
├── 2023 rebrand/
│   └── colours (latest).docx
├── fonts.zip
└── Guidelines_DRAFT.pdf

The repository

Organized by what people need

  • gitbrand.com/acmeone link, one access level
  • #logosWordmark, Symbol · SVG / PNG / JPG
  • #colorsForest, Sand, Paper · HEX RGB HSL CMYK
  • #fontslive preview, license noted
  • #resourcesguidelines PDF, templates
  • #faqthe questions that repeat

Questions about keeping assets in order

What teams ask once the first version of the library is live.

Should every campaign file go in the brand kit?

No. Keep the everyday identity easy to find. Campaign archives belong in your storage; add resources to the kit only when they help people use the brand.

How often should we review the assets?

Whenever the identity changes, and whenever repeated questions show a gap in the guidance. Add a calendar reminder if your team needs one.

Where do the old logos go?

Into an archive folder in your own storage, clearly separated from the current set. GitBrand is for the identity people use today, not for a history of every version.

What if we manage more than one brand?

Create a repository per brand. Each gets its own slug, its own access setting and its own members, so filenames never collide and a client only sees their own kit. The free plan includes up to five repositories.

Can several people maintain the same repository?

Yes. Add editors as members. Anyone who is a member can also clone the repository as a private draft to try changes before publishing.

Related

Where to go from here.

Brand asset management without the DAMWhat GitBrand does, and what it deliberately leaves out.Open GitBrand for marketing teamsStop answering “where is the logo?” in chat.Open What should a brand kit include?Work through the checklist before you share.Open

Give the library a link and an owner

Start with the logos people ask for most, add colors and fonts, and share one gitbrand.com URL. Free for up to five repositories.