|
| 1 | +name: 📚 Documentation Issue |
| 2 | +description: Report issues with documentation or request documentation improvements |
| 3 | +title: "[Docs]: " |
| 4 | +labels: ["documentation", "needs-triage"] |
| 5 | +assignees: [] |
| 6 | +body: |
| 7 | + - type: markdown |
| 8 | + attributes: |
| 9 | + value: | |
| 10 | + Thanks for helping improve our documentation! Please provide details about the documentation issue or improvement. |
| 11 | +
|
| 12 | + - type: checkboxes |
| 13 | + id: checklist |
| 14 | + attributes: |
| 15 | + label: Pre-submission checklist |
| 16 | + description: Please verify these items before submitting |
| 17 | + options: |
| 18 | + - label: I have searched existing issues to ensure this is not a duplicate |
| 19 | + required: true |
| 20 | + - label: I have checked multiple documentation sources (README, docs/, articles/) |
| 21 | + required: true |
| 22 | + |
| 23 | + - type: dropdown |
| 24 | + id: doc_type |
| 25 | + attributes: |
| 26 | + label: Documentation Type |
| 27 | + description: What type of documentation issue is this? |
| 28 | + options: |
| 29 | + - Missing Documentation (feature/command not documented) |
| 30 | + - Incorrect Information (documentation is wrong or outdated) |
| 31 | + - Unclear Instructions (confusing or hard to follow) |
| 32 | + - Broken Links (links don't work or go to wrong place) |
| 33 | + - Typos/Grammar (spelling, grammar, or formatting issues) |
| 34 | + - Missing Examples (need more examples or use cases) |
| 35 | + - Installation/Setup (issues with setup instructions) |
| 36 | + - API/Command Reference (missing or incorrect command documentation) |
| 37 | + - Other |
| 38 | + validations: |
| 39 | + required: true |
| 40 | + |
| 41 | + - type: input |
| 42 | + id: doc_location |
| 43 | + attributes: |
| 44 | + label: Documentation Location |
| 45 | + description: Where is the documentation issue located? |
| 46 | + placeholder: | |
| 47 | + e.g., README.md, docs/articles/users/chat_commands.md, |
| 48 | + docs/articles/users/tutorials/Installation/docker-ollama-setup.md |
| 49 | + validations: |
| 50 | + required: true |
| 51 | + |
| 52 | + - type: textarea |
| 53 | + id: issue_description |
| 54 | + attributes: |
| 55 | + label: Issue Description |
| 56 | + description: Describe the documentation issue in detail |
| 57 | + placeholder: | |
| 58 | + Clearly describe what's wrong, missing, or confusing about the documentation. |
| 59 | + Be specific about what you were trying to accomplish. |
| 60 | + validations: |
| 61 | + required: true |
| 62 | + |
| 63 | + - type: textarea |
| 64 | + id: current_content |
| 65 | + attributes: |
| 66 | + label: Current Content |
| 67 | + description: | |
| 68 | + If applicable, quote the current documentation content that has issues |
| 69 | + placeholder: | |
| 70 | + Copy and paste the current documentation text that needs to be fixed. |
| 71 | + Use quotes or code blocks to clearly identify the content. |
| 72 | + render: markdown |
| 73 | + |
| 74 | + - type: textarea |
| 75 | + id: suggested_improvement |
| 76 | + attributes: |
| 77 | + label: Suggested Improvement |
| 78 | + description: How should the documentation be improved? |
| 79 | + placeholder: | |
| 80 | + Provide your suggestion for how to fix or improve the documentation. |
| 81 | + Include specific text changes, additional examples, or structural improvements. |
| 82 | + validations: |
| 83 | + required: true |
| 84 | + |
| 85 | + - type: textarea |
| 86 | + id: context |
| 87 | + attributes: |
| 88 | + label: Context |
| 89 | + description: What were you trying to accomplish when you found this issue? |
| 90 | + placeholder: | |
| 91 | + Describe your use case or what you were trying to learn/do: |
| 92 | + - Setting up Hatchling for the first time |
| 93 | + - Trying to use a specific command |
| 94 | + - Integrating with a new LLM provider |
| 95 | + - Creating a custom MCP server |
| 96 | + - etc. |
| 97 | + validations: |
| 98 | + required: true |
| 99 | + |
| 100 | + - type: dropdown |
| 101 | + id: user_level |
| 102 | + attributes: |
| 103 | + label: User Experience Level |
| 104 | + description: What's your experience level with Hatchling? |
| 105 | + options: |
| 106 | + - New User (first time using Hatchling) |
| 107 | + - Beginner (basic usage, following tutorials) |
| 108 | + - Intermediate (comfortable with most features) |
| 109 | + - Advanced (power user, custom configurations) |
| 110 | + - Developer (contributing to the project) |
| 111 | + validations: |
| 112 | + required: true |
| 113 | + |
| 114 | + - type: textarea |
| 115 | + id: additional_examples |
| 116 | + attributes: |
| 117 | + label: Additional Examples Needed |
| 118 | + description: | |
| 119 | + If requesting examples, what specific scenarios should be covered? |
| 120 | + placeholder: | |
| 121 | + Describe what examples would be helpful: |
| 122 | + - Step-by-step tutorials |
| 123 | + - Common use cases |
| 124 | + - Configuration examples |
| 125 | + - Troubleshooting scenarios |
| 126 | + - Code samples |
| 127 | +
|
| 128 | + - type: checkboxes |
| 129 | + id: contribution |
| 130 | + attributes: |
| 131 | + label: Contribution |
| 132 | + description: Would you be interested in helping improve this documentation? |
| 133 | + options: |
| 134 | + - label: I would be willing to contribute to fixing this documentation |
| 135 | + - label: I would be willing to review proposed documentation changes |
| 136 | + - label: I can provide additional examples or use cases |
| 137 | + |
| 138 | + - type: textarea |
| 139 | + id: additional_context |
| 140 | + attributes: |
| 141 | + label: Additional Context |
| 142 | + description: Any other context about this documentation issue |
| 143 | + placeholder: | |
| 144 | + Include any additional information: |
| 145 | + - Screenshots of confusing interfaces |
| 146 | + - Links to related documentation |
| 147 | + - Similar issues in other projects |
| 148 | + - Urgency or impact of this issue |
0 commit comments