Puranjay Savar Mattas
b1e8eb958e
Rounds out the issue template set (bug/docs/security already existed) - feature requests point at CLAUDE.md's phased build order since most useful requests here are "match what web Outline does", and questions point at SETUP.md first since blank issues are disabled.
39 lines
1.1 KiB
YAML
39 lines
1.1 KiB
YAML
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
|