diff --git a/.gitea/issue_template/feature_request.yaml b/.gitea/issue_template/feature_request.yaml new file mode 100644 index 0000000..3c89634 --- /dev/null +++ b/.gitea/issue_template/feature_request.yaml @@ -0,0 +1,38 @@ +name: Feature Request +about: Suggest something for Outpost +labels: + - "type: feature" +body: + - type: markdown + attributes: + value: | + Outpost is early alpha and tracking Outline's own web app for parity (see [`CLAUDE.md`](../../CLAUDE.md) for the phased build order) — a request that's "just do what web Outline does" is easier to act on than a net-new idea. + - type: input + id: summary + attributes: + label: Summary + placeholder: What do you want Outpost to do? + validations: + required: true + - type: textarea + id: motivation + attributes: + label: Motivation + description: What's the use case? What can't you do today without this? + validations: + required: true + - type: textarea + id: proposal + attributes: + label: Proposed Behavior + description: How should it work? Point at how Outline's web app does it, if relevant. + - type: dropdown + id: platform + attributes: + label: Platform + options: + - macOS + - iOS / iPadOS + - Both / platform-agnostic + validations: + required: true diff --git a/.gitea/issue_template/question.yaml b/.gitea/issue_template/question.yaml new file mode 100644 index 0000000..3d21924 --- /dev/null +++ b/.gitea/issue_template/question.yaml @@ -0,0 +1,20 @@ +name: Question +about: Ask something about setup, usage, or how Outpost works +labels: + - "type: question" +body: + - type: markdown + attributes: + value: | + Check [`SETUP.md`](../../SETUP.md) first — most "how do I get this running" questions are answered there. + - type: textarea + id: question + attributes: + label: Question + validations: + required: true + - type: textarea + id: context + attributes: + label: Context + description: What are you trying to do? Anything you've already tried?