Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Readme.md Updation] Created Table for all Projects Listings in READM…
…E.md file (#609) ## Related Issue Fixes #608 ## Description ### What I have changed? 😄 - Added `Relative Link` to the Particular folders of Each project (that goes to code of the folder, **not it's deployment**) - (For **visiting/exploring** to deployments, [https://100-days-100-web-project.vercel.app/)](https://100-days-100-web-project.vercel.app/) website is great) - Instead of direct text based day-project-listings, **Relative link attached to the _CODE FOLDER_ + Description attached for day-project-listings is _Actually Useful!_** ### Screenshots > After  > Before  ## Type of PR - [ ] Bug fix - [ ] Feature enhancement - [X] 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 - [X] I have performed a self-review of my code. - [X] I have read and followed the Contribution Guidelines. - [X] I have tested the changes thoroughly before submitting this pull request. - [X] I have provided relevant issue numbers, screenshots, and videos after making the changes. - [X] I have commented my code, particularly in hard-to-understand areas. - [X] I have followed the code style guidelines of this project. - [X] I have checked for any existing open issues that my pull request may address. - [X] I have ensured that my changes do not break any existing functionality. - [X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently. - [X] I have read the resources for guidance listed below. - [X] I have followed security best practices in my code changes. ## Additional Context Readme.md is a very important and crucial for a project. Most seen code file of a repo :) * Commented useless text * <!--- ## 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!
- Loading branch information
