|
| 1 | +name: 📚 Documentation Improvement |
| 2 | +description: Suggest improvements to documentation, examples, or guides |
| 3 | +title: "[Docs]: " |
| 4 | +labels: ["documentation"] |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + Thanks for helping improve ProcTap's documentation! |
| 10 | +
|
| 11 | + - type: dropdown |
| 12 | + id: doc-type |
| 13 | + attributes: |
| 14 | + label: Documentation Type |
| 15 | + description: What type of documentation needs improvement? |
| 16 | + options: |
| 17 | + - README.md |
| 18 | + - API Reference / Docstrings |
| 19 | + - Code Examples |
| 20 | + - Tutorial / Guide |
| 21 | + - Installation Instructions |
| 22 | + - Troubleshooting Guide |
| 23 | + - CLAUDE.md (Developer Guide) |
| 24 | + - Type Stubs (.pyi files) |
| 25 | + - Inline Code Comments |
| 26 | + - Other |
| 27 | + validations: |
| 28 | + required: true |
| 29 | + |
| 30 | + - type: textarea |
| 31 | + id: issue |
| 32 | + attributes: |
| 33 | + label: Documentation Issue |
| 34 | + description: Describe what's missing, unclear, or incorrect in the documentation |
| 35 | + placeholder: | |
| 36 | + The documentation doesn't explain how to... |
| 37 | + The example code is confusing because... |
| 38 | + The installation instructions are missing... |
| 39 | + validations: |
| 40 | + required: true |
| 41 | + |
| 42 | + - type: textarea |
| 43 | + id: location |
| 44 | + attributes: |
| 45 | + label: Location |
| 46 | + description: Where is the documentation issue located? |
| 47 | + placeholder: | |
| 48 | + - File: README.md, section "Basic Usage" |
| 49 | + - Line 42 in src/proctap/core.py docstring |
| 50 | + - examples/record_proc_to_wav.py |
| 51 | + render: markdown |
| 52 | + validations: |
| 53 | + required: true |
| 54 | + |
| 55 | + - type: textarea |
| 56 | + id: current-content |
| 57 | + attributes: |
| 58 | + label: Current Content (If Applicable) |
| 59 | + description: Quote or paste the current documentation that needs improvement |
| 60 | + placeholder: | |
| 61 | + Currently says: |
| 62 | + "Use ProcessAudioTap to capture audio." |
| 63 | + render: markdown |
| 64 | + |
| 65 | + - type: textarea |
| 66 | + id: proposed-content |
| 67 | + attributes: |
| 68 | + label: Proposed Improvement |
| 69 | + description: What should the documentation say instead? |
| 70 | + placeholder: | |
| 71 | + Should say: |
| 72 | + "ProcessAudioTap captures audio from a specific Windows process by PID. |
| 73 | + Example: `tap = ProcessAudioTap(pid=12345)`" |
| 74 | + render: markdown |
| 75 | + validations: |
| 76 | + required: true |
| 77 | + |
| 78 | + - type: dropdown |
| 79 | + id: audience |
| 80 | + attributes: |
| 81 | + label: Target Audience |
| 82 | + description: Who would benefit from this documentation improvement? |
| 83 | + options: |
| 84 | + - Beginners (new to ProcTap) |
| 85 | + - Intermediate Users |
| 86 | + - Advanced Users / Contributors |
| 87 | + - All Users |
| 88 | + validations: |
| 89 | + required: true |
| 90 | + |
| 91 | + - type: checkboxes |
| 92 | + id: doc-scope |
| 93 | + attributes: |
| 94 | + label: Documentation Scope |
| 95 | + description: What aspects should the improved documentation cover? |
| 96 | + options: |
| 97 | + - label: Clear explanation of concepts |
| 98 | + - label: Working code examples |
| 99 | + - label: Common pitfalls / gotchas |
| 100 | + - label: Performance considerations |
| 101 | + - label: Type hints and signatures |
| 102 | + - label: Error handling |
| 103 | + - label: Platform-specific notes (Windows versions) |
| 104 | + - label: Integration examples (Discord, etc.) |
| 105 | + |
| 106 | + - type: textarea |
| 107 | + id: example-code |
| 108 | + attributes: |
| 109 | + label: Example Code (Optional) |
| 110 | + description: If you're suggesting a code example, provide it here |
| 111 | + placeholder: | |
| 112 | + ```python |
| 113 | + from proctap import ProcessAudioTap |
| 114 | +
|
| 115 | + # Example demonstrating the concept |
| 116 | + ``` |
| 117 | + render: python |
| 118 | + |
| 119 | + - type: textarea |
| 120 | + id: related-issues |
| 121 | + attributes: |
| 122 | + label: Related Issues / Questions |
| 123 | + description: Link to related issues, discussions, or questions |
| 124 | + placeholder: | |
| 125 | + - Related to #123 |
| 126 | + - Users asked about this in Discussion #456 |
| 127 | + - Stack Overflow question: https://... |
| 128 | +
|
| 129 | + - type: checkboxes |
| 130 | + id: languages |
| 131 | + attributes: |
| 132 | + label: Language / Translation |
| 133 | + description: Does this involve translation or localization? |
| 134 | + options: |
| 135 | + - label: English documentation improvement |
| 136 | + - label: Add Japanese translation |
| 137 | + - label: Add other language translation |
| 138 | + - label: Fix grammar / spelling |
| 139 | + |
| 140 | + - type: checkboxes |
| 141 | + id: implementation |
| 142 | + attributes: |
| 143 | + label: Implementation Willingness |
| 144 | + description: Can you help improve the documentation? |
| 145 | + options: |
| 146 | + - label: I can submit a PR with the documentation changes |
| 147 | + - label: I can write example code |
| 148 | + - label: I can review/proofread changes |
| 149 | + - label: I can help translate |
| 150 | + |
| 151 | + - type: textarea |
| 152 | + id: additional |
| 153 | + attributes: |
| 154 | + label: Additional Context |
| 155 | + description: Any other information about the documentation improvement |
| 156 | + placeholder: Screenshots, links to good documentation examples from other projects, etc. |
0 commit comments