Feat : creating a logo + Adding a favicon #263
Assignees
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
MEDIUM
VSoC'24
contribution under VSOC 24
Comments
|
Thank you for raising this issue! We'll look into it as soon as possible. Please ensure that the issue is not duplicate, and you read CONTRIBUTING.md carefully. Your contributions are highly appreciated! 😊 |
dhairyagothi
added
documentation
|
make a new one on your own @Meetjain1 |
|
Hi @dhairyagothi I have designed some logos let me know which logo suits more for this website .
|
|
1st one @Meetjain1 |
dhairyagothi
added a commit
that referenced
this issue
Jul 15, 2024
## Related Issue [Cite any related issue(s) this pull request addresses. If none, simply state "None”] write issue no. here closes #263 ## Email id used to regsiter for VSoc'24 [email protected] ## Description Designed logo and added as a favicon [Please include a brief description of the changes or features added] ## Type of PR - [ ] Bug fix - [X] Feature enhancement - [ ] Documentation update - [ ] Security enhancement - [ ] Other (specify): _______________ check in issue by entering [X] in boxes ## Screenshots / Videos (if applicable) [Attach any relevant screenshots or videos demonstrating the changes] ## Checklist - [ ] I have performed a self-review of my code. - [ ] I have read and followed the Contribution Guidelines. - [ ] I have tested the changes thoroughly before submitting this pull request. - [ ] I have provided relevant issue numbers, screenshots, and videos after making the changes. - [ ] I have commented my code, particularly in hard-to-understand areas. - [ ] I have followed the code style guidelines of this project. - [ ] I have checked for any existing open issues that my pull request may address. - [ ] I have ensured that my changes do not break any existing functionality. - [ ] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently. - [ ] I have read the resources for guidance listed below. - [ ] I have followed security best practices in my code changes. check in issue by entering [X] in boxes ## Additional Context [Include any additional information or context that might be helpful for reviewers.] ## Contribution Guidelines Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines: ### Issue Creation 1. **Limit on Issues:** - Each contributor is allowed to create a maximum of **4 issues per day**. This helps us manage and address issues efficiently. ### Contribution Levels 2. **Basic Contributions:** - This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests. - For these tasks, issues will be assigned the **Easy** label. 3. **Acknowledging Hard Work:** - If a contributor puts in significant effort on a task, the issue will be upgraded to **Medium**. This is our way of recognizing and appreciating extra effort. 4. **Feature Additions and Component Work:** - Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work. - The more complex and valuable the contribution, the higher the level assigned. ### Level Definitions - **Easy:** - Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates. - **Medium:** - Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements. - **Hard:** - Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components. We look forward to your contributions and appreciate your effort in helping us improve the project!
|
Hello @Meetjain1! Your issue #263 has been closed. Thank you for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currenty our website have no logo and hence no favicon
Describe the solution you'd like
Want to create a logo and hence will add that logo as a favicon also
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
@dhairyagothi assign this issue to me , I am working under VSOC. Thanks
The text was updated successfully, but these errors were encountered: