Skip to content

Conversation

DivaQueen-dev
Copy link

Updated contributing guidelines to enhance clarity and engagement. Closes issue #877.

Updated contributing guidelines to enhance clarity and engagement.
Comment on lines +112 to +113
We’re always happy to help and collaborate! 🤝
# ⚖️ Code of Conduct
Copy link
Member

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.

Comment on lines +81 to +82
We appreciate your patience — reviews ensure every addition maintains the project’s quality and vision.
## 📜 Contribution Guidelines
Copy link
Member

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.

Comment on lines +72 to +73
---
### 🧩 Pull Request Review Process
Copy link
Member

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.

Comment on lines +62 to +63
```
### 5. Push and Create a Pull Request
Copy link
Member

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>
Copy link
Member

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.

Comment on lines -66 to -72
## 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!" ⚡🌟
Copy link
Member

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.

@aayush105
Copy link
Member

@DivaQueen-dev

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants