Brand portals
A brand portal you can set up before lunch.
A brand portal is a web page where people find and download approved brand assets. GitBrand turns each repository into one: a clean page at your own slug, with previews, exports, guidance and a QR code, ready to share with clients, partners and press.
North Outfitters
Gear for long walks. Updated today.
Logos
Colors
Fonts
North Serif for headings
North Sans for body text, previewed with your words.
Resources
- Brand guidelinesPDF · 2.1 MB
- Slide templatePPTX · 4.8 MB
- Product photographyZIP · 38 MB
FAQ
Which logo goes on dark backgrounds? +
Can partners use the wordmark? +
Who do I ask about co-branding? +
Anatomy of a portal
Six parts, numbered as above.
Each section only appears when it has content, so a small brand with one logo and three colors still looks complete.
- 1
Address, description and access
The portal lives at gitbrand.com/your-slug. The header shows the brand name, a short description, the website link and the current access level. Copy and QR buttons sit here too.
- 2
Logos with exports
Upload SVG. Every variation is shown on its intended background and can be downloaded as SVG, PNG or JPG without opening a design tool.
- 3
Named colors in every format
Each color shows HEX, RGB, HSL and CMYK. The whole palette exports as CSS, SCSS, Tailwind, JSON, TXT or an SVG swatch sheet.
- 4
Fonts with a live preview
Visitors type their own text and adjust the size to see the typeface in use, then download the files where the license allows it.
- 5
Resources
Guideline PDFs, templates, photography archives, anything with a name and a description. This is where the brand book lives next to the assets it explains.
- 6
FAQ
The questions people keep asking, answered once. "Which logo on dark?" stops arriving in your inbox.
Who can open it
Public, password or member-only. Same link.
Pick the level that fits the audience. Change it later without sending a new URL.
Anyone with the link, and search engines.
A public portal is a brand page. It opens without an account, can be indexed and, if you turn on AI access, publishes brand.json, Markdown, llms.txt and an MCP endpoint alongside the page.
- Press kits, partner assets and open-source projects
- Indexable, so a search for your logo lands on your version
- Optional AI endpoints for assistants and agents
Distribution
Put the link where the work starts.
A portal only helps if people reach it before they ask. Four places that cover most requests.
Website footer
A "Brand" or "Press" link in the footer is where journalists and partners look first.
Footer → Brand → gitbrand.com/northProject briefs
Put the link at the top of every brief so agencies and freelancers start from the right files.
Assets: gitbrand.com/north (password in thread)Onboarding docs
New hires learn where the brand lives on day one instead of asking in a channel on day three.
Week 1 · Read the brand portalEmail signatures
A one-line "Brand assets" link under your name answers the request before it is sent.
Brand assets → gitbrand.com/northEmbed and QR
On your own site, or on a printed page.
Two ways to bring the portal to people who will not type a URL.
<!-- Renders the portal without the GitBrand header and footer --> <iframe src="https://gitbrand.com/embed/north" title="North brand assets" width="100%" height="900" loading="lazy" ></iframe>
The embed URL is gitbrand.com/embed/{slug}. It serves the same sections as the portal, respects the same access level, and stays current when you update the repository. Removing the small "Powered by GitBrand" footer is part of Premium.
A QR code for print
Every repository generates a QR code for its link. Put it on packaging, event banners, business cards or the last slide of a deck. It opens the portal at the current access level.
After launch
A portal is the current source, not an archive.
It cannot recall files people already downloaded, so the job is to make sure the next person who opens the link finds only the right thing.
Name one maintainer
A portal with an owner stays current. A portal owned by everyone is owned by nobody.
Update everything together
When the identity changes, replace logos, colors, fonts and the written guidance in one pass, then tell people to replace their local copies.
Remove, do not hoard
Old logo versions belong in your design files, not in the portal. If it is in the portal, someone will use it.
Answer questions in the FAQ
When the same question arrives twice, write the answer into the repository FAQ so the third person finds it there.
Keep the link stable
Change the access level instead of creating a new repository. The URL stays the same, so briefs, footers and signatures keep working.
FAQ
Portal questions, answered.
Can I use my own domain?
Custom domains are part of the Premium plan. On the Free plan your portal lives at gitbrand.com/your-slug, and you can embed it on any site you control.
Can I embed the portal on my website?
Yes. Every repository has an embed URL at gitbrand.com/embed/your-slug that renders the same content without the GitBrand header and footer, so it fits inside your own page.
Does a public portal expose everything to AI tools?
Only if you enable AI access for that repository. Private and password-protected repositories are never exposed through the AI endpoints.
Can I change the access level after sharing the link?
Yes. Public, password-protected and member-only portals all use the same link format, so you can start private during a project and open the portal at launch without sending a new URL.
Can I see who visited the portal?
Yes, in aggregate. Insights show views over time, unique visitors, referrers, countries and which assets get downloaded or fetched through the API. Nobody is identified by name; if you need to know exactly who took which file, a full digital asset management system is a better fit.
Related: Brand asset management · For agencies · Brand kit checklist
Your portal is one slug away.
Create a repository, fill the sections that matter, pick the access level. The link works from the first minute and stays the same as the brand grows.