1+ name : 📚 Documentation Issue
2+ description : Report missing, incorrect, or unclear documentation
3+ title : " [Docs]: "
4+ labels : ["documentation", "needs-triage"]
5+ body :
6+ - type : markdown
7+ attributes :
8+ value : |
9+ Thanks for helping improve our documentation!
10+ Clear and accurate documentation is essential for a good developer experience.
11+
12+ - type : checkboxes
13+ id : prerequisites
14+ attributes :
15+ label : Prerequisites
16+ description : Please confirm you have completed the following
17+ options :
18+ - label : I have searched existing issues to ensure this isn't a duplicate
19+ required : true
20+ - label : I have checked the latest documentation on the main branch
21+ required : true
22+
23+ - type : dropdown
24+ id : documentation-type
25+ attributes :
26+ label : Documentation Type
27+ description : What type of documentation issue is this?
28+ options :
29+ - Missing documentation
30+ - Incorrect/outdated information
31+ - Unclear explanation
32+ - Broken links
33+ - Formatting issues
34+ - Code examples not working
35+ - API documentation gaps
36+ - Tutorial improvements
37+ - Installation guide issues
38+ - Other
39+ validations :
40+ required : true
41+
42+ - type : textarea
43+ id : issue-description
44+ attributes :
45+ label : Issue Description
46+ description : Describe the documentation problem
47+ placeholder : |
48+ What's wrong with the current documentation?
49+ What information is missing or unclear?
50+ validations :
51+ required : true
52+
53+ - type : input
54+ id : documentation-location
55+ attributes :
56+ label : Documentation Location
57+ description : Where is the problematic documentation located?
58+ placeholder : |
59+ e.g., docs/guides/mpq-archives.md, README.md, API docs for Archive::open, etc.
60+ validations :
61+ required : true
62+
63+ - type : textarea
64+ id : current-content
65+ attributes :
66+ label : Current Content
67+ description : Quote the current documentation content (if applicable)
68+ render : markdown
69+ placeholder : |
70+ ```markdown
71+ Current documentation that needs improvement...
72+ ```
73+ validations :
74+ required : false
75+
76+ - type : textarea
77+ id : suggested-improvement
78+ attributes :
79+ label : Suggested Improvement
80+ description : How should the documentation be improved?
81+ placeholder : |
82+ - What information should be added?
83+ - How should existing content be clarified?
84+ - What examples would be helpful?
85+ validations :
86+ required : true
87+
88+ - type : textarea
89+ id : user-scenario
90+ attributes :
91+ label : User Scenario
92+ description : When would someone need this documentation?
93+ placeholder : |
94+ Describe the user journey or use case...
95+ - What is the user trying to accomplish?
96+ - What level of experience do they have?
97+ - What context are they coming from?
98+ validations :
99+ required : false
100+
101+ - type : checkboxes
102+ id : affected-sections
103+ attributes :
104+ label : Affected Documentation Sections
105+ description : Which documentation sections are affected? (Check all that apply)
106+ options :
107+ - label : README.md
108+ - label : Getting Started guides
109+ - label : Installation instructions
110+ - label : CLI usage guides
111+ - label : API documentation (rustdoc)
112+ - label : Format-specific guides (MPQ, DBC, etc.)
113+ - label : Architecture documentation
114+ - label : Contributing guidelines
115+ - label : Code examples
116+ - label : Tutorial content
117+ - label : Troubleshooting guides
118+ - label : Performance guides
119+
120+ - type : dropdown
121+ id : audience
122+ attributes :
123+ label : Target Audience
124+ description : Who is the primary audience for this documentation?
125+ options :
126+ - Beginners/new users
127+ - Intermediate developers
128+ - Advanced users
129+ - Contributors/maintainers
130+ - Library users (API consumers)
131+ - CLI users
132+ - All audiences
133+ - Other
134+ validations :
135+ required : false
136+
137+ - type : textarea
138+ id : examples-needed
139+ attributes :
140+ label : Examples Needed
141+ description : What examples would make this clearer?
142+ placeholder : |
143+ - Code examples
144+ - Command-line examples
145+ - Screenshots
146+ - Diagrams
147+ - Step-by-step tutorials
148+ validations :
149+ required : false
150+
151+ - type : textarea
152+ id : related-content
153+ attributes :
154+ label : Related Content
155+ description : Links to related documentation or resources
156+ placeholder : |
157+ - Similar documentation that works well
158+ - External resources that could be referenced
159+ - Related issues or discussions
160+ validations :
161+ required : false
162+
163+ - type : checkboxes
164+ id : contribution-willingness
165+ attributes :
166+ label : Contribution
167+ description : Are you willing to help improve this documentation?
168+ options :
169+ - label : I can write the improved documentation
170+ - label : I can provide examples or code snippets
171+ - label : I can review proposed changes
172+ - label : I can test documentation changes
173+ - label : I'm looking for someone else to fix this
174+
175+ - type : textarea
176+ id : additional-context
177+ attributes :
178+ label : Additional Context
179+ description : Any other information that would help improve the documentation
180+ placeholder : |
181+ - Common misconceptions users have
182+ - Frequently asked questions
183+ - Error messages users encounter
184+ - Related tools or workflows
185+ validations :
186+ required : false
0 commit comments