PostHog
DRAFT - getting your first 10, 50, 100, 1,000, 100,000 users
Changes
Super rough draft
Checklist
- [ ] Words are spelled using American English
- [ ] Titles are in sentence case
- [ ] Feature names are in sentence case too
- [ ] Use relative URLs for internal links
- [ ] If I moved a page, I added a redirect in
vercel.json - [ ] Remove this template if you're not going to fill it out!
Article checklist
- [ ] I've added (at least) 3-5 internal links to this new article
- [ ] I've added keywords for this page to the rank tracker in Ahrefs
- [ ] I've checked the preview build of the article
- [ ] The date on the article is today's date
- [ ] I've added this to the relevant "Tutorials and guides" docs page (if applicable)
Useful resources
- The PostHog style guide
- Full list of tags and categories
- List of content components
- PostHog SEO best practices
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated (UTC) |
|---|---|---|---|
| posthog | 🛑 Canceled (Inspect) | Apr 22, 2024 8:48pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
@andyvan-ph art requested, also had a stab at writing summaries for each section. voila: https://docs.google.com/document/d/1dtm9FS1U3W21h_bVTBmN05fjnSpJD-4YadLrVt5nbUM/edit?usp=sharing
happy to start building all this in substack tomorrow if you're all good with the changes/etc. be good to get it wrapped up well ahead of thursday.
@andyvan-ph Tided up the GitHub version and moved over to Substack where I've done another read and light edit: https://newsletter.posthog.com/publish/post/143866439
I've cut pre-requisites to save space. Agree we need to do something visual/rethink the list in the 'How we got to 100 users' section. Also thinking on visual elements for elsewhere to break things up.
I think the 'How we got to 10 users, then 50' section could be quite a bit shorter. Ditto we could speed up the intro. There's one TKTK in there, and a few places where I think we still need to tidy up the way things are written so they're easier to follow.
Also does it need 'recommended reads' at the bottom? I'd vote yes as it's a nice way to round out the newsletter.
Also does it need 'recommended reads' at the bottom? I'd vote yes as it's a nice way to round out the newsletter.
Yeah, I can sort that. I have a library of stuff to pull from.
