11222 update docs contributor guide #50974
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…information I removed form the general contribution guide last time.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
the
area/documentation
nataliekwong
reviewed
Jan 8, 2025
nataliekwong
reviewed
Jan 8, 2025
nataliekwong
approved these changes
Jan 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Resolves #11222. Updates the documentation contributor guide. This change refreshes the presentation and organization of the content, adds new open source topic templates, adds new guidance for product badges, AI usage, and diagrams, and removes/addresses various statements that ceased to be correct at some point in the past.
How
Updates three existing topics with new information.
Review guide
This probably only needs a cursory review to approve. It's pretty straightforward and doesn't introduce a ton of new information.
User Impact
Airbyte employees and contributors from the community should find it a bit easier to onboard onto writing docs. This is especially important as I try to build a small network of OSS docs contributors.
Can this PR be safely reverted and rolled back?