For freelance and in-house designers
North — outdoor goods, made to last
Deliver the identity with the thinking attached.
You designed a system. The client received a folder. GitBrand lets you present the logo variations, palette, type and usage notes the way you would explain them in person, so the identity survives contact with the real world.
The specimen above works like the font preview in every repository: visitors type their own text and adjust the size before they download.
Upload once
Stop exporting the same PNG for the fifth time
Every “can I get this in PNG at 2x on transparent” is ten minutes you are not paid for. Upload the SVG once and GitBrand renders it, checks it and exports SVG, PNG or JPG on request. The client picks the format; you never open the file again.
For print, provide the supplier’s specification as a resource and keep production files in your own delivery process. GitBrand covers screen use.
Guidance people follow
Write the notes you would say out loud
Most misuse is not carelessness, it is a missing instruction. A specific line beside the asset is followed far more often than a rule on page 14 of a PDF. Here is what the North kit says, asset by asset.
- Wordmark, dark background
- Use on Forest or ink. Never on photography without the overlay.
- Symbol
- Favicons, app icons and anything under 24px. Not a replacement for the wordmark.
- Forest #456455
- Primary. Buttons, headings on Paper, the mark itself.
- Sand #E9C6A3
- Supporting. Backgrounds and highlights only; never for text.
- Heading font
- Weights 500 and 600. The license is per seat; buy it at the foundry linked here.
- Body font
- Open license, download included. Use 16px minimum on the web.
Before and after
A delivery folder stores files. A kit presents them.
The same identity, delivered two ways. The folder is complete and unusable; the kit answers the question before it is asked.
- Logo_FINAL_v3.ai
- Logo_FINAL_v3 (1).png
- logo white.png
- logo-black-NEW.jpg
- colours.pdf
- Fonts.zip
- Guidelines_draft2.pdf
- IMG_4471.png
Logos
- Wordmark, light background
- Wordmark, dark background
- Symbol
Colors
- Forest · Primary
- Sand · Supporting
- Paper · Background
- Ink · Text
Fonts
- Heading · license note
- Body · download
Resources
- Guidelines.pdf
- Slide template
Proof of process
A live kit is a better case study than a screenshot
A case study shows a logo. A public GitBrand repository shows you build identities people can use: the variations, the palette with every value, the type with a live preview, and the care in the notes. Link it from your portfolio next to the visuals.
Keep it password-protected while the project runs and open it at launch. When a client asks whether the logo can sit on a photo, answer and add it to the repository FAQ; over a year the kit becomes the brand guide the client actually reads.
FAQ
Questions designers ask
Does GitBrand design anything for me?
No. GitBrand organizes and presents the identity you designed. Your design tools stay your design tools.
What if the client already has a Google Drive?
Keep the archive there. Put the current, approved identity in GitBrand so the everyday assets are presented, not just stored.
Can I keep the kit private while the project is running?
Yes. Start with a password or member-only access and switch to public when the brand launches. The link stays the same.
Which logo format should I upload?
Upload SVG. GitBrand renders it and exports SVG, PNG and JPG on demand, so you never export a raster by hand again. If a client only has a PNG, you can host it, but the exports work from vector.
How many client brands can I keep on the Free plan?
Five repositories, with uploads for logos, fonts and resources, unlimited downloads and password-protected sharing. Premium removes the limit.
Send one link, not a folder.
Upload the SVG, name the colors by role, write the notes. Free for up to five brands.