Giters

WebXDAO / WebXDAO.github.io

WebX DAO - Website built with Next.js and Tailwind - Community Built. 🛸

Home Page:https://webxdao.xyz

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[FEATURE]: Noticed documentation.yml and styles.yml Files need for ISSUE_TEMPLATES

NarendraKoya999 opened this issue · comments

commented

Detailed description

Purpose of Raising this Issue

documentation.yml (Custom ISSUE_TEMPLATE):

  • The documentation.yml file serves as a custom ISSUE_TEMPLATE for your GitHub repository, specifically focused on documentation-related issues. When contributors or users of your project want to report documentation-related problems, improvements, or requests, they can create a new issue using this template.
  • The contents of documentation.yml could include prompts or guidelines to help users structure their documentation-related issue reports effectively. For example, it might ask them to provide specific details about the section/page of documentation they found confusing, suggest possible improvements, or even ask for clarifications about the issue they are experiencing.

styles.yml (Custom ISSUE_TEMPLATE):

  • The styles.yml file, on the other hand, serves as a custom ISSUE_TEMPLATE for issues related to coding style, code formatting, and linting rules within your GitHub repository. This template helps contributors or users report code style-related concerns or seek guidance on adhering to the project's coding standards.

  • The contents of styles.yml might include specific questions or prompts related to coding style, requesting users to provide examples of code snippets that need formatting adjustments or explanation. Additionally, you might include instructions on how to check code against the project's style guidelines and best practices.

Context

  • These two Files are very useful for Raising Documentation related Modifications and Styling, Enhancement related Requests.

Possible implementation

No response

Additional information

No response

Checklist

  • I have read the Contributing Guidelines
  • I have checked the existing issues
  • I am willing to work on this issue (optional)
  • I am a GSSoC'23 contributor
commented

Hi @mkubdev . Please Review on this Issue as soon as Possible. Thank You !

commented

This issue is marked stale because it has been open for 16 days with no activity.

commented

I'm closing this issue due to inactivity. Please feel free to reopen it if you'd like to contribute or have further discussions.