Skip to content
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

Merged
merged 6 commits into from
Dec 9, 2024
Merged

Conversation

daniloc
Copy link
Contributor

@daniloc daniloc commented Dec 3, 2024

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.

Screenshot 2024-12-03 at 12 43 17 PM

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

Copy link

vercel bot commented Dec 3, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Dec 9, 2024 6:49pm

@daniloc daniloc requested a review from oliverb123 December 3, 2024 17:45
@daniloc
Copy link
Contributor Author

daniloc commented Dec 3, 2024

@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?

@oliverb123
Copy link

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

@daniloc
Copy link
Contributor Author

daniloc commented Dec 4, 2024

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.

@daniloc daniloc merged commit 5ffba78 into master Dec 9, 2024
3 checks passed
@daniloc daniloc deleted the add-io-overview branch December 9, 2024 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants