Website and Docs
Looking for our brand style guide? Look no further.
We’re here to:
- Communicate to prospective customers the value we provide
- Educate customers to deploy, manage and use PostHog very easily
- Own posthog.com
- Own the docs
Q3 2022 Goals
- Make posthog.com a great resource for new and returning users
- Key Results:
- 25% decrease in support tickets per customer
- Ensure the top 50 most visited Docs pages are up to date
- Make sure the conversion rate doesn’t fall
- Whilst we don’t want to eliminate our engineer:engineer interaction, there are likely 10x as many lurkers who never solve their problems.
- Producing an exceptional documentation experience will encourage more word of mouth growth.
- I currently think the dev advocate should go into the website & docs team
- Primary: Quality signups
How we work
The Website & Docs board is used for enhancements to posthog.com (including handbook) and our docs. Artwork for blog is handled separately, and is explained below.
- [Design] Backlog - a mostly stack ranked list of tasks
- [Design] In progress
- Ready for development - completed designs that are awaiting implementation
- [Development] Backlog - mostly stack ranked
- [Development] In progress
Designs for website & docs typically start in Balsamiq wireframes, then progress into hi-fi designs in Figma. Read more about this process.
Blog artwork and marketing assets
Because of the volume of content we publish, blog artwork has its own dedicated Artwork project board managed by Lottie.
When we share a design, we do our best to explain the type of feedback we're looking for. (Ex: Overall visual aesthetic, flow, if a design communicates to our developer-focused audience, etc.)
If a screenshot is posted directly to a Github issue, that's a great place for feedback. (If a comment already covers your feedback, we encourage the use of an emoji response over additional comments like "+1".)
Some of the design tools we use, like Balsamiq and Figma, both have built-in commenting, which is useful for prototypes with multiple pages. If we provide a link to a prototype in one of these tools, please leave a comment using the app's comment system. This helps us review and take action on comments later, and creates a single place for discussion around a particular topic.
Important: We prioritize feedback based on alignment with business goals. Everyone has feedback about design. (If feedback is more of a personal opinion than a business-related perspective, we’ll note it, but don't be offended if your feedback isn't specifically addressed!)