-
Notifications
You must be signed in to change notification settings - Fork 7
Add more 'how to contribute' documentation #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR expands the README to provide comprehensive contribution guidelines for the LASP developer guide project. The update transforms a minimal README into a detailed contributor guide that explains project structure, formatting standards, and workflow procedures.
- Added detailed sections on Markdown usage, project organization, and formatting consistency
- Included information about content scope limitations and security considerations
- Added instructions for local documentation building and git workflow
README.md
Outdated
| * Avoid sharing opinions about topics without supporting facts | ||
| * Stick to third-person language and avoid using first-person | ||
| * Avoid jargon, acronyms, or abbreviations unless they are defined | ||
| * Keep sentences and paragraphs concise—break up long blocks of text |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is concise-break intended to be hyphenated as a compound word or should there be spaces around the hyphen to break up the two statements?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
README.md
Outdated
| * Stick to third-person language and avoid using first-person | ||
| * Avoid jargon, acronyms, or abbreviations unless they are defined | ||
| * Keep sentences and paragraphs concise—break up long blocks of text | ||
| * Follow a consistent capitalization style for headings, code terms, proper nouns, etc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a period after etc
vmartinez-cu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just had a couple minor comments, but otherwise it looks great! Thanks for adding these updates
This PR expands the README to include more details on how to contribute to this project.
Closes #19