You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can provide a pre-made template for how one's .md file should look like.
---title: loremdescription: description about loremlink: to the projects source code and deployment(if available)tech_stack: [array, of, tags] github_profile_link: url to the github profile---
Moreover, constraint the data to Yaml front matter format.
This way people can simply duplicate the file and make changes into it. This will ensure uniformity across md files and make it easier to check for bad PRs.
Step involved:
Create template.md file
update README.md accordingly
Additional bifurcation:
We can even divide the projects I to three folders respectively like you mentioned in the README.
I would love to make the changes and contribute to the project. If you like the proposal, consider assigning me to the issue.
The text was updated successfully, but these errors were encountered:
@ashishk1331 Sure, Instead of creating a seperate template.md file, display the structure in readme file itself. and Regarding additional bifurcation, We will perform a structure refactor once we get enough projects.
Thank you
We can provide a pre-made template for how one's .md file should look like.
Moreover, constraint the data to Yaml front matter format.
This way people can simply duplicate the file and make changes into it. This will ensure uniformity across md files and make it easier to check for bad PRs.
Step involved:
Additional bifurcation:
We can even divide the projects I to three folders respectively like you mentioned in the README.
I would love to make the changes and contribute to the project. If you like the proposal, consider assigning me to the issue.
The text was updated successfully, but these errors were encountered: