To coincide with the reframing around "Apps", we need a page for developers that outlines the different ways you can build things on PostHog/with PostHog data.

There are a few reasons why a developer might visit this page:

1. "I want to capture the live event stream and do something with it" (Plugin server)
2. "I want to pull data out of PostHog programmatically" (API)
3. "I want to build an app that works inside PostHog" (future)
4. "I want to instrument features of PostHog in my mobile/native app" (SDKs)

Here's a first pass on what a developers landing page could look like:

Notable things:

• Proposing to rename the "Plugin server" to "PostHog Event Server". (Need clarification on how you run this - whether it's baked into your PostHog instance, or if it's separate, and how you'd leverage Cloud for this.)
• Want to clarify if our standard schema is run pre-ingestion or post-ingestion, meaning, if I'm pulling in realtime data from pipelines, is it already formatted for me, or am I getting the raw, unprocessed stream in which I need to clean it/standardize it myself?

I'm only about 80% confident in what I put down here being accurate, so I'm open to feedback on:

1. If these options make sense at all
2. If the claims are accurate
3. If this is missing any use cases

cc @fuziontech @yakkomajuri @jamesefhawkins