[EPIC] Nail Plugins

[jamesefhawkins]

DESIGN

• [ ] Add filtering to the plugin page (data in/out, official, community)
• [ ] Change "plugin" and “integration” to "app" everywhere in the product
• [ ] Add Squeak! to each plugin page (remove the link to the Slack community)
• [x] add "Free" to each app on /apps
• [x] Ensure beta apps are clearly labeled
• [ ] Ensure every app product page has a nice featured image
• [ ] Ensure the most popular apps are always featured on the homepage
• [x] Create #3281 page
• [ ] Add pricing section
• [x] Change all urls to /app/example-plugin (today: /product/example-plugin)
• [x] Make posthog.com/apps really good and includes both information about what apps are and how to contribute to them.

CONTENT

• [x] Change "plugin" and “integration” to "app" everywhere on the site
• [x] Add a way to capture feature requests via docs content
• [x] Add Posthog version and Cloud/SH requirements to every plugin
• [x] Create a contributors section for each plugin
• [x] Add links to other useful documentation (ie APIs for other systems) to each plugin's page
• [ ] ~Ensure the build your own content includes clear mention of plugin bounties~
• [x] Update build section with where to submit docs etc
• [x] Make sure each subheader in the documentation for apps is parsed as a question
• [x] Create a clear link to how to build your own to Posthog.com/apps
• [x] Add a 'What if my question isn't answered?' question to the documentation. Answer? Slack.

OTHER

• [x] Add links to the source code for every plugin in the plugin page on posthog.com
• [ ] Delete all old plugin readmes in their own repos. Change them to link to the right place on posthog.com

[joethreepwood]

There may be some overlap, but I was working on this concurrently and it's hard to reconcile them on a small screen right now. This is what came to mind.

• [ ] Change all mentions of integrations to apps across the website and in the docs
• [ ] Create contribution guidelines, so that users know how to correctly format, write and submit a new app
• [ ] Ensure documentation for every app explains whether it is data in or data out or both
• [ ] Ensure documentation for every app explains whether it is official or community made
• [ ] Ensure every app product page has a nice featured image
• [ ] Ensure every app has at least one linked tutorial which explores a typical use case
• [ ] Ensure documentation for each app includes a link to the Slack channel so that contributors know about the contribution channel
• [ ] Ensure beta apps are clearly labelled
• [ ] Ensure the most popular apps are always featured on the home page
• [ ] Ensure documentation about how to update the app pages and their documentation is included in the handbook
• [ ] Add any new code snippets from the app pages to Posthog.com Storybook if needed
• [x] Make posthog.com/apps really good and includes both information about what apps are and how to contribute to them.
• [ ] Provide an actionable way for users who want to contribute to get started via either the plugin bounties or the good first issue tag. Include this on /apps
• [ ] Fix sidebars.json. I know.
• [ ] Make the product page design work nicely on mobile

[joethreepwood]

• [ ] Make sure each subheader in the documentation for apps is parsed as a question.

[joethreepwood]

OK, I've consolidated the lists and grouped them loosely. Grouping is just to keep it organized, not to assign to any particular person. Put the current reconciled list into James' top comment.

[joethreepwood]

Docs tracking

• [x] Get every plugin below into the new format on the website
• [x] Give each of the below plugins a basic docs page, with install guide
• [x] Add a source code link and contributors info to docs for each of the below
• [x] Airbyte
• [x] Automatic Cohort Creator
• [x] BigQuery Export
• [x] BitBucket Release Tracker
• [x] Currency Normalization
• [x] Customer.io
• [x] Downsampling
• [x] Email scoring
• [x] Event Sequence Timer Plugin
• [x] First Time Event Tracker
• [x] GCS Export
• [x] GeoIP
• [x] GitHub Release Tracker
• [x] GitHub Star Sync
• [x] GitLab Release Tracker
• [x] Heartbeat
• [x] Hubspot
• [x] Ingestion Alert
• [x] Migrator 3000
• [x] Orbit Stats Sync
• [x] Pagerduty
• [x] PostgreSQL Export
• [x] Property Filter
• [x] Property Flattener
• [x] Pub/Sub Export
• [x] Redshift Export
• [x] Redshift Import Plugin
• [x] Replicator
• [x] RudderStack Export
• [x] S3 export
• [x] Salesforce
• [x] Schema Enforcer
• [x] Segment
• [x] Sendgrid
• [x] Sentry
• [x] Snowflake Export
• [x] Taxonomy Standardizer
• [x] Timestamp Parser
• [x] Twitter Followers
• [x] Useragent Enhancer
• [x] Zapier
• [x] Zendesk
• [x] n8n
• [x] Check for any new apps that may need to be added, add them
• [x] Update the sidebar.json

[joethreepwood]

We currently talk about Plugin Chains in our documentation but, as we change to Apps, that won’t make sense. App Chains won’t make sense either, as it implies that other apps (e.g. Trends, Paths) can shape the data in the same way a Plugin Chain does, which isn’t true.

For the moment I’m calling these dependency chains, but it's really just a placeholder term to unblock me so I can keep writing. Any suggestions for a better name welcome.

[joethreepwood]

FYI that, following guidance from @yakkomajuri, I'm going to list that all apps require 1.30.0 or later, unless there is already information about earlier versions being required.