-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Revise CONTRIBUTING.md for improved clarity #883
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
base: master
Are you sure you want to change the base?
Conversation
Updated contributing guidelines to enhance clarity and engagement.
We’re always happy to help and collaborate! 🤝 | ||
# ⚖️ Code of Conduct |
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 space between these 2 line.
We appreciate your patience — reviews ensure every addition maintains the project’s quality and vision. | ||
## 📜 Contribution Guidelines |
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 space between these 2 line.
--- | ||
### 🧩 Pull Request Review Process |
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 space between these 2 line.
``` | ||
### 5. Push and Create a Pull Request |
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 space between these 2 line.
it’s creativity, passion, and collaboration in motion. | ||
Together, we’re proving that the web can be magical — even without JavaScript. | ||
|
||
</div> |
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.
After this can you add the code of conduct which we had previously.
## Code of Conduct 🤝 | ||
2. Feedback: If suggestions arise, kindly make the requested changes. | ||
|
||
Please be aware that we uphold a [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a positive and respectful environment for all contributors. As a participant in this project, you pledge to abide by the Code of Conduct. | ||
3. Merge: Once approved, your contribution will be merged and credited to you. 🎉 | ||
|
||
We appreciate your patience — reviews ensure every addition maintains the project’s quality and vision. | ||
## 📜 Contribution Guidelines | ||
|
||
| Category | Guideline | | ||
|----------------|------------------------------------------------------------| | ||
| Code Style | Use readable, well-formatted HTML and CSS | | ||
| Design | Keep demos elegant, creative, and responsive | | ||
| Accessibility | Maintain strong contrast and readability | | ||
| Structure | Follow existing folder patterns and naming conventions | | ||
| README Update | Add your demo link and description where relevant | | ||
|
||
Let's embark on this collective journey to create a precious resource for developers. Thank you for adding your spark to "You Don't Need JavaScript!" ⚡🌟 |
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 these code of conduct, i have mentioned the placement.
can you check all the spacing once, and also like can you add one more section, while creating the new pr, in description section add the output images/ demo video if its new feature/project added and if its existing and updated the ui or something than contributor should provide the before and after outputs in description. Did you get it? If not please kindly ping me. |
Updated contributing guidelines to enhance clarity and engagement. Closes issue #877.