Skip to content

Commit f600836

Browse files
authored
Centralize branding assets (#18806)
* Centralize branding sources to @posthog/brand * Refactor brand asset references and update build scripts - Updated package.json to include new prebuild scripts for generating brand assets. - Changed references in documentation and components from the old brand assets path to the new path. - Removed the obsolete company brand assets page and updated links across the handbook. - Deleted the sync-brand-assets script as it is no longer needed with the new asset management approach. * Remove forced react component from cool-tech-jobs.tsx * Refactor logo imports and usage across components - Removed references to the `Logo` component from `@posthog/brand/logo` in multiple files. - Updated logo usage to directly reference SVG paths instead of the React component. - Adjusted related logic in `useCustomers` and other components to accommodate the changes. * address posthog review items
1 parent f238555 commit f600836

119 files changed

Lines changed: 549 additions & 946 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

contents/founders/registering-trademarks.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Those first crucial months present bigger problems to worry about - like finding
2323
A word mark is basically just the name of the brand (as written in a specific font, if applicable). In our case, it's the word 'PostHog.' A logo mark is typically pictorial - in our case, the hedgehog logo either alone or combined with a stylized word. The word mark is the most versatile, so that should be your first trademark priority.
2424

2525
<div class="text-center my-8">
26-
<img src="/brand/posthog-logo.svg" class="w-full" />
26+
<img src="/brand/posthog-logo.svg" alt="PostHog" class="w-full" />
2727
</div>
2828

2929
When you decide to register your trademark, you don't need to spend a fortune doing it. With a tactical combination of using the right type of lawyer and doing it yourself, you should be able to get trademarks filed in the US, UK, EU and China for ~$3,000 _in total_.
@@ -45,4 +45,3 @@ We’ve currently secured our brand name ('PostHog') and word mark in the four t
4545
The phrase 'open source' might denote a public codebase, but a brand name can definitely be trademarked. For example, we want people to [deploy our open source edition](https://github.com/PostHog/posthog) wherever they please, but we don't want them to slap the 'PostHog' name on random products. Besides, if you’re [raising money](https://posthog.com/blog/open-source-business-models) for your startup in the future, IP is a box that investors will want you to check as part of their diligence.
4646

4747
<NewsletterForm />
48-

contents/handbook/brand/assets.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,7 @@ Each logo below is rendered live from our [`@posthog/brand`](https://github.com/
4747
- On **light backgrounds, prefer the standard logo**, and only reach for the **dark logo** (solid black) when a single-color mark is required.
4848
- Use the **print (4-color)** version only for print or other limited-palette contexts where the gradients can't be reproduced.
4949
- Use the **logomark** on its own only at small sizes — favicons, app icons — where the full lockup won't fit and the overlapping gradients would get too busy.
50+
- Use a **square logomark** for avatars and integrations that require a square image. Its transparent square canvas keeps the logomark's proportions intact — never stretch the standard logomark to fill a square. Use the standard gradient version on light backgrounds, or the light solid-white version on dark backgrounds.
5051
- Use the **stacked** logo for portrait or square placements where the standard (landscape) lockup is too wide.
5152

5253
_Never_ modify the colors in the logomark (for example, don't recolor the hedgehog's face white on a dark background — use the light logo instead).

contents/handbook/brand/visual-identity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Find logos on our [brand assets](/handbook/brand/assets) page.
2929
| Stacked logo | When horizontal space is limited but the full name is important. |
3030
| 4-color logo | Print version, when gradients can't be printed. Only use the 4-color logo for this case. |
3131

32-
Download all variants at [/handbook/company/brand-assets.md](/handbook/company/brand-assets). SVG is always preferred.
32+
Download all variants from [brand assets](/handbook/brand/assets). SVG is always preferred.
3333

3434
### Rules
3535

@@ -264,4 +264,4 @@ The same light/dark rule applies: if a visualization appears on posthog.com, it
264264

265265
**Annotations and context**
266266

267-
A chart without context can mislead. When publishing a chart – especially in a blog post – annotate significant moments: a feature launch, a spike, a known data anomaly. Readers should understand *why* something happened, not just *that* it happened.
267+
A chart without context can mislead. When publishing a chart – especially in a blog post – annotate significant moments: a feature launch, a spike, a known data anomaly. Readers should understand *why* something happened, not just *that* it happened.

contents/handbook/company/brand-assets.md

Lines changed: 0 additions & 212 deletions
This file was deleted.

contents/handbook/marketing/events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Our brand is a reflection of us and [how we’re experienced by others](/blog/br
9292

9393
**Words:** Naming products is hard. Same goes for naming events and writing their descriptions. As a prerequisite, read our primer on [writing for developers](/founders/writing-for-developers). Try your best to come up with event names that communicate the 'what?' and will attract the 'who?' And then again ask yourself, "would I attend this?"
9494

95-
**Pictures:** Every event is improved with a flyer or poster that showcases the essence of the experience. We keep a comprehensive list of brand assets and guidelines on the [brand assets page](/handbook/company/brand-assets). Share your assets and we’ll give feedback. Depending on the scale and timing of the event, our team may be able to help with branding as well.
95+
**Pictures:** Every event is improved with a flyer or poster that showcases the essence of the experience. We keep a comprehensive list of brand assets and guidelines on the [brand assets page](/handbook/brand/assets). Share your assets and we’ll give feedback. Depending on the scale and timing of the event, our team may be able to help with branding as well.
9696

9797
### Event recaps
9898

contents/handbook/marketing/ownership.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ Read [art and branding requests](/handbook/brand/art-requests) first!
128128
<details>
129129
<summary>I need a font, logo, etc.</summary>
130130

131-
See [Logos, brand, hedgehogs](/handbook/company/brand-assets)
131+
See [Logos, brand, hedgehogs](/handbook/brand/assets)
132132
</details>
133133

134134
<details>

contents/handbook/marketing/speaker-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ A few principles for building out slides:
8686
* If a slide doesn't support the one true thing you identified in step 3, cut it.
8787
* Speaking of speaker notes, you will save yourself time and head space if you always have notes.
8888

89-
For feedback on design or help with navigating the [PostHog brand assets](https://posthog.com/handbook/company/brand-assets) ([Hoggies](https://www.figma.com/design/I0VKEEjbkKUDSVzFus2Lpu/Hoggies?node-id=2226-55&t=1sj1GezTKuCfaybF-1) included), stop by [\#team-graphics](https://posthog.slack.com/archives/C0AU440KS6P)
89+
For feedback on design or help with navigating the [PostHog brand assets](/handbook/brand/assets) ([Hoggies](https://www.figma.com/design/I0VKEEjbkKUDSVzFus2Lpu/Hoggies?node-id=2226-55&t=1sj1GezTKuCfaybF-1) included), stop by [\#team-graphics](https://posthog.slack.com/archives/C0AU440KS6P)
9090

9191
## **6. Practice out loud. Twice minimum.**
9292

@@ -130,4 +130,4 @@ If you receive a question that you believe is off-topic or unfitting for the set
130130
* Feb 2026 - <TeamMember name="Michael Matloka"/> - [10 learning from launching an agentic AI product at scale](https://www.figma.com/slides/zMNBsNihNxKyS6z7sSwiRK/10-learnings-from-launching-an-agentic-AI-product-at-scale?t=6hlWStUDlHsITOKo-6)
131131
* Nov 2025 - <TeamMember name="James Hawkins"/> - [How to build a cult](https://drive.google.com/file/d/1BMgl2y817m5t43D6NCr9hstnGO1kKxJy/view)
132132
* Oct 2025 - <TeamMember name="Joshua Snyder"/> - [Code that fixes itself](https://docs.google.com/presentation/d/1sYsmTPugdttQqshPa6yIKQcUu5Rje3-fPMbRGtyrfZg/edit?slide=id.p#slide=id.p)
133-
* Oct 2024 - <TeamMember name="Michael Matloka"/> - [Parsing at the speed of light](http://figma.com/slides/y0rMgEaWbYe0nSpEhWkyY6/Parsing-at-the-speed-of-metal?node-id=1-536&t=uiCktez3IWxAKI8D-0)
133+
* Oct 2024 - <TeamMember name="Michael Matloka"/> - [Parsing at the speed of light](http://figma.com/slides/y0rMgEaWbYe0nSpEhWkyY6/Parsing-at-the-speed-of-metal?node-id=1-536&t=uiCktez3IWxAKI8D-0)

contents/library/ops/registering-trademarks.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Those first crucial months present bigger problems to worry about - like finding
2525
A word mark is basically just the name of the brand (as written in a specific font, if applicable). In our case, it's the word 'PostHog.' A logo mark is typically pictorial - in our case, the hedgehog logo either alone or combined with a stylized word. The word mark is the most versatile, so that should be your first trademark priority.
2626

2727
<div class="text-center my-8">
28-
<img src="/brand/posthog-logo.svg" class="w-full" />
28+
<img src="/brand/posthog-logo.svg" alt="PostHog" class="w-full" />
2929
</div>
3030

3131
When you decide to register your trademark, you don't need to spend a fortune doing it. With a tactical combination of using the right type of lawyer and doing it yourself, you should be able to get trademarks filed in the US, UK, EU and China for ~$3,000 _in total_.
@@ -44,4 +44,3 @@ We’ve currently secured our brand name ('PostHog') and word mark in the four t
4444
The phrase 'open source' might denote a public codebase, but a brand name can definitely be trademarked. For example, we want people to [deploy our open source edition](https://github.com/PostHog/posthog) wherever they please, but we don't want them to slap the 'PostHog' name on random products. Besides, if you’re [raising money](https://posthog.com/blog/open-source-business-models) for your startup in the future, IP is a box that investors will want you to check as part of their diligence.
4545

4646
_Enjoyed this? Subscribe to our [newsletter](https://newsletter.posthog.com/subscribe) to hear more from us twice a month!_
47-

contents/media-contents.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ You can find biographies and social links for our founders, [James](/community/p
4040

4141
## PostHog logos
4242

43-
We've created brand assets for you. You don't have to negotiate legal agreements for them. You can find them on our [brand assets](/handbook/company/brand-assets) page.
43+
We've created brand assets for you. You don't have to negotiate legal agreements for them. You can find them on our [brand assets](/handbook/brand/assets) page.
4444

4545
## Founder headshots
4646

contents/tutorials/how-to-connect-posthog-and-notion-with-zapier.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ First, head to the [‘My Apps’ section of your Zapier account](https://zapier
3030

3131
Next, we need to create a Zapier bot in Notion, which will perform the action of updating a database with information whenever an action is defined in PostHog. You’ll need to be a Notion admin to do this.
3232

33-
Start by heading to Notion’s Settings page, then click the Integrations tab and select ‘Develop your own integrations’ to start creating your bot. Here you can follow the instructions to give your bot a name, as well as customize it in other ways. You can even grab the PostHog logo from [our brand assets](/handbook/company/brand-assets) and use it as the icon for your bot!
33+
Start by heading to Notion’s Settings page, then click the Integrations tab and select ‘Develop your own integrations’ to start creating your bot. Here you can follow the instructions to give your bot a name, as well as customize it in other ways. You can even grab the PostHog logo from [our brand assets](/handbook/brand/assets) and use it as the icon for your bot!
3434

3535
![Notion Integrations Page](https://res.cloudinary.com/dmukukwp6/image/upload/v1710055416/posthog.com/contents/images/tutorials/notion/create-integration.png)
3636

@@ -59,4 +59,4 @@ If the action is specific to a page or on-page selector, this information is als
5959

6060
As an output, we want the workflow to populate the information to a Notion page — so we’ll use Notion’s ‘Write to database’ output. With these options created you can tailor how the information contained in the event is written to your Notion database. Instituting best practices, such as requiring action creators to include descriptions for their actions, will enable you to track all tracked actions within a simple Notion table.
6161

62-
<NewsletterForm />
62+
<NewsletterForm />

0 commit comments

Comments
 (0)