Improve onboarding docs with focus-group entry points#32
Open
Shivampal157 wants to merge 1 commit into
Open
Conversation
Add a README start-here section and create standardized focus-group onboarding pages with consistent sections for scope, meeting details, leads, joining steps, and first tasks. Signed-off-by: Shivampal157 <shivampal60076@gmail.com> Made-with: Cursor
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR improves contributor onboarding documentation by adding a clear entry path in the README and introducing standardized focus-group pages.
What changed
README.md.Files added/updated
README.mdFOCUS GROUPS/developer-group.mdFOCUS GROUPS/designers-group.mdFOCUS GROUPS/communitymanagers-group.mdFOCUS GROUPS/researchers-group.mdFOCUS GROUPS/technicalwriters-group.mdWhy
New contributors need a clear “where to start” path.
These changes reduce onboarding friction and make documentation more consistent across contributor groups.
Validation
Closes #31