-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add import and export overview to 'Start here' #10045
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@oliverb123 had an additional request of this page to include stuff about third party integrations we do not maintain; I'll give it a day to gather more context there upon his return before merging here. Any specific pointers you can offer me on what you were thinking on third party stuff, Olly? |
Hey @daniloc, I don't really have a great answer here, sorry - I'm thinking of things like: I don't know perfectly how to document these (or even in all cases if we should), but there's a whole world of "things that can write to posthog" that exist outside our codebase, and mentioning some of the big ones might make sense? Feel free to punt on this for now, and circle back later |
All good @oliverb123! Yeah, let's do this: I'll create a docs backlog item for a roundup page on these things. It would be easy enough to write up what we currently know about, but I'm slightly anxious about making our ecosystem look smaller than it is so by not knowing what we don't know about, if that makes sense. |
Co-authored-by: Ian Vanagas <[email protected]>
Changes
Per #9869, add an overview to the docs 'Start here' section.
We've got so many ways to get data in and out of PostHog, scattered across a few different products' docs. This offers some way finding for the new user/team just getting started.
Checklist
vercel.json