https://github.com/airbytehq/write-for-the-community
Contribute and collaborate on educational content for the Airbyte Community.
https://github.com/airbytehq/write-for-the-community
airbyte articles data open-source showcases tutorial videos
Last synced: 8 months ago
JSON representation
Contribute and collaborate on educational content for the Airbyte Community.
- Host: GitHub
- URL: https://github.com/airbytehq/write-for-the-community
- Owner: airbytehq
- License: mit
- Created: 2020-09-09T17:51:39.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2021-07-26T18:09:34.000Z (about 4 years ago)
- Last Synced: 2025-01-07T07:13:53.850Z (10 months ago)
- Topics: airbyte, articles, data, open-source, showcases, tutorial, videos
- Homepage:
- Size: 1000 KB
- Stars: 42
- Watchers: 10
- Forks: 8
- Open Issues: 52
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## Guidelines
Our full guidelines for publishing can be found [here](./GUIDELINES.md). Additionally, our FAQ which includes information on payment and the review process can be found [here](https://www.notion.so/Write-for-Airbyte-FAQ-de5c369a4973489cbad067205537038d).
## Our Philosophy
Airbyte is fully open by design. We share our [roadmap](https://docs.airbyte.io/project-overview/roadmap), [strategy](https://handbook.airbyte.io/strategy/strategy) and everything about our [business model](https://handbook.airbyte.io/strategy/business-model).
In this fashion, this repository is designed to share about our [roadmap](https://github.com/airbytehq/community-content/projects/1) in terms of content publications, so you can vote on the articles, tutorials and videos we plan to work on, and also contribute them!
## Contributing
If you want to help push our content roadmap forward, the first thing to do is to join the #write-for-the-community channel in our Slack by clicking [here](https://airbytehq.slack.com/app_redirect?channel=C024095BAGP).
Here are the different types of contributions you can help with.
* [Request a publication](https://github.com/airbytehq/community-content/issues/new?assignees=&labels=&template=request-a-publication.md&title=)
* [Submit a publication](https://github.com/airbytehq/community-content/issues/new?assignees=&labels=&template=submit-a-publication.md&title=)
* [Update a publication](https://github.com/airbytehq/community-content/issues/new?assignees=&labels=&template=update-a-publication.md&title=)
* [Translate a publication](https://github.com/airbytehq/community-content/issues/new?assignees=&labels=translation&template=translate-a-publication.md&title=)
This is how we differentiate the different types of publications:
* **Articles** are pieces that will go on our blog, which are usually higher level explorations of the data engineering space, but not always.
* **Recipes** are educational use cases to help Airbyte users understand how they can leverage Airbyte in data engineering, marketing, customer success, sales, finance and other use cases. You can see examples [here](https://airbyte.io/recipes)
* **Operator guides** are located in our documentation to help Airbyte users better leverage Airbyte with other tools of the data stack. Some examples are [here](https://docs.airbyte.io/operator-guides).
**Once you're submitted your content**, you can move it down the different steps of the process in the [community project here](https://github.com/airbytehq/write-for-airbyte/projects/1).
We look forward to seeing what the community requests and produces! We value the different ways that people use Airbyte and would love to explore all the possibilities that exist with the technology.
We are not looking for promotional pieces or marketing pitches.