Guides
Short guides for a brand kit people can use.
Six articles on what a brand kit needs, which files to send, how to name and organize them, and how to keep the rules next to the assets. Written for the person who has to share the brand this week.
6 guides · about 40 minutes in total
What should a brand kit include? A practical checklist.
A brand kit checklist for designers and small teams: logo variations, color values, fonts, usage guidance and access settings to check before you share the brand.
Guide 01 · 6 min readRead the checklistBefore you share
What has to be in the kit, in which formats, and how to hand it over.
What should a brand kit include? A practical checklist.
A brand kit checklist for designers and small teams: logo variations, color values, fonts, usage guidance and access settings to check before you share the brand.
6 min readSVG, PNG or JPG: which logo file should you use?
When to use SVG, PNG and JPG logo files, what to ask a print supplier, and how to name logo exports so clients pick the right file every time.
7 min readHow to package logo files for a client.
What to include in a client logo package: file formats, color versions, folder structure, naming, licensing notes and how to deliver it as a link instead of a zip.
7 min read
Keeping it in order
Naming, rules and color values that stay correct after the launch.
How to organize brand assets your team can actually find.
A practical process for sorting brand files, naming logo variations, documenting usage and sharing one maintained brand library with your team.
6 min readHow to write brand guidelines people actually use.
How to create brand guidelines that get read: what to include, how long they should be, and how to keep them next to the logos, colors and fonts they describe.
8 min readBrand colors: HEX, RGB, HSL and CMYK, and how to share them.
What HEX, RGB, HSL and CMYK color codes mean, when each is used, why conversions differ, and how to document brand colors so web, print and design teams match.
6 min read
Why these guides
Every one of them answers a question we hear from people using GitBrand: what goes in the kit, which logo file to send, why the printed blue is wrong, how to stop the “final-v7” folder from growing. They stay short on purpose and do not invent numbers or customers; where a claim needs a source, the guide links it.
GitBrand itself is a repository at gitbrand.com/your-slug with logos, colors, fonts, resources and a FAQ, shared as one link. The guides mention it where it does something specific, and stand on their own where it does not. See features, how it works or the docs for the product itself.
About the guides
Which guide should I read first?
Start with the brand kit checklist. It lists what a kit needs before you share it, and every other guide expands one item on that list.
Do I need a GitBrand account to use the guides?
No. The guides describe how to build and share a brand kit in general terms. Where GitBrand does something specific, such as exporting PNG and JPG from an SVG, the guide says so.
How often are the guides updated?
Each guide shows its last updated date at the top. We revise them when the product changes or when readers ask a question the guide should have answered.
Can I share these guides with a client or colleague?
Yes. Every guide is public and lives at a stable address under gitbrand.com/guides, so a link keeps working.
Apply what you read
A free GitBrand account gives you up to five repositories, each with logos, colors, fonts and resources at one shareable link. No credit card.