docs: convert markdown templates to issue forms #1234
Labels
📄 Documentation
Internal or public documentation
🆘 Help wanted
Open to participation from the community
📈 Improvement
Improvement of a feature.
🟨 Priority: Medium
Not blocking but should be addressed
I'm opening a blank issue because these refer to docs and don't change the existing functionality.
Proposed Changes
Convert the issue templates to YML form to simplify the process for contributors and remove the markdown templates (.yml).
Issue forms are more user-friendly than Markdown templates, especially for contributors unfamiliar with Markdown syntax. They can fill out the fields and provide the requested information easily.
Issue forms standardize the information provided by contributors, reducing the need for follow-up questions and clarifications.
With issue forms, all issues are created in a consistent format, making it easier for maintainers to review and respond quickly.
You can refer to this example to see how an issue form looks.
Add more issue templates.
Currently, there are only 3 issue templates, but there can be more templates for documentation, refactoring the codebase, or discussion. Let me know if you want me to add any of these or something specific.
I'd love to contribute to this. Please assign me, and I'll make a PR.
The text was updated successfully, but these errors were encountered: