Blog post: What if PostHog looked like a dev tool? #7227
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Twixes
reviewed
Nov 28, 2023
|
I've decided this entire post is trash and needs to be re-written from the ground up. Hopefully I can get this done before it's time to publish. |
Cool. Give me a shout when you have a new fart you're happier with. |
Please tell me this was intentional |
25 tasks
|
Alright, post has been rewritten. Note: Also new slug |
corywatilo
changed the title
Co-authored-by: Joe Martin <[email protected]>
Co-authored-by: Joe Martin <[email protected]>
andyvan-ph
approved these changes
Dec 6, 2023
andyvan-ph
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This explains the rationale for why we're making these specific design changes to PostHog. The goal is to get buy-in from users who may be initially averse to change, by explaining our bigger vision, and hopefully getting them to buy in.
My plan is to link this from the welcome pane and it can be published once the UI goes live to (some of) our audience.