PostHog Handbook Library / Brand

366 words. Estimated reading time: 2 min.

Ownership & approvals

We don't want to be a place where everything has to funnel through a single person or group, but it's also important we maintain consistency as we grow. We try to make this easy with the #design-review channel.

What needs designer approval

Not everything needs sign-off. Here's a rough guide:

| Asset type | Approval needed? | | ------------------------------------------------------------ | --------------------------------------------------------- | | New illustration or hedgehog | Yes – submit a request | | Conference booth design | Yes | | Print materials (going to a vendor) | Yes, before print | | Merch design | Handled by Team Graphics | | Partnerships or third-party co-branding | Yes | | Major website changes outside of the handbook, docs, or articles | Yes | | Social media graphics (simple) | Recommended if it's a significant post, otherwise no | | Blog post, changelog, tweet | No – but self-check against this guide | | Product UI copy, tooltips, empty states | No – but read out loud before shipping |

When in doubt, ask in the #design-review Slack channel. Lottie and Cory are, for now, the only people who can approve work or otherwise.

Who owns what

Graphics team responsibilities

This is who owns what on #team-graphics:

Canonical URL: https://posthog.com/handbook/brand/approvals

GitHub source: contents/handbook/brand/approvals.md

Content hash: 696dd26ab5379524

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: SmallTeam.