Start with the task, not the label
Teams use “brand guide,” “style guide” and “brandbook” in different ways. The useful distinction is practical. If a designer needs the correct logo file, they need an asset. If they need to know which version to use on a dark background, they need a rule.
| Question | Brand kit | Brandbook |
|---|---|---|
| What does it contain? | Logo files, colors, fonts, images and layouts | Context, principles, usage rules and examples |
| When is it used? | While creating a deliverable | When deciding how it should look or sound |
| What keeps it useful? | Clear file names and current assets | Clear ownership, examples and revisions |
A product brand needs more than a logo folder
Consider a skincare launch. The product page, packaging preview, social post and retailer presentation should look related. The kit supplies the logo and images. The book explains color roles, type hierarchy, product framing and voice. A beautiful handbook without usable files creates more work; a folder without rules invites inconsistent interpretation.
Build a small system first
Start with one approved primary mark, an appropriate reverse version, a compact palette and a clear type hierarchy. Add the main product image treatment and two or three actual applications. Write rules against these outputs, then expand only when a new channel introduces a real decision.
Review the handoff
- Can the next person identify the latest logo?
- Are color values supplied in the format they need?
- Are fonts available and licensed for the intended use?
- Do the examples show both correct and incorrect use?
- Is it clear what is final and what remains a draft?
In Brandfolia, the brand kit workspace and the brandbook maker share one set of inputs. That keeps the starting system together while leaving the strategic decisions with you.