Files
accounted/.github/ISSUE_TEMPLATE/feature_request.yml
T
Jakob Wennberg 920400cfb5 docs: community health files, ARCHITECTURE.md, and README overhaul (#1072)
* docs: add community health files, ARCHITECTURE.md, and README overhaul

Community layer: CODE_OF_CONDUCT (Contributor Covenant 2.1), issue
templates (bug/feature YAML forms + contact links), PR template
mirroring the Definition of Done, and a visitor-grade ARCHITECTURE.md
distilled from internal docs.

README: fix the clone/cd case mismatch, add CI/docker badges and site
links, add a Why section (compliance-by-construction, agent-native MCP
surface, self-hostable), add missing payroll and MCP feature bullets,
and restructure the documentation/community sections. Hero screenshot
slot left as a comment pending an approved shot.

CONTRIBUTING: fix stale gnubok name, link Code of Conduct and
ARCHITECTURE.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Jakob Wennberg <jakob.wennberg@gmail.com>

* docs: address review feedback on community files

Disable blank issues so security reports stay on the private path,
require npm run build in the PR checklist to match CONTRIBUTING, and
align ARCHITECTURE.md immutability wording with the actual trigger
behavior (controlled posted-to-reversed transition is permitted).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Jakob Wennberg <jakob.wennberg@gmail.com>

---------

Signed-off-by: Jakob Wennberg <jakob.wennberg@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-20 11:22:05 +02:00

31 lines
993 B
YAML

name: Feature request
description: Suggest a new feature or improvement
labels: ["enhancement"]
body:
- type: textarea
id: problem
attributes:
label: What problem does this solve?
description: Describe the problem or friction you are running into, not just the solution.
validations:
required: true
- type: textarea
id: solution
attributes:
label: Proposed solution
description: What would you like to see happen?
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Other approaches you have considered, or how you work around this today.
- type: textarea
id: context
attributes:
label: Additional context
description: |
Anything else that helps us understand the request. For accounting features, a reference
to the relevant Swedish rule or an example from another tool (e.g. Fortnox) is very helpful.