feat: streamline feature request template to focus on problem reporting

[hannesrudolph]

Description

Streamlines the GitHub feature request template to better separate problem reporting from solution contribution, making it more accessible for users who just want to report issues while maintaining comprehensive requirements for contributors.

Changes Made

Template Structure Overhaul

• Main form focus: Shifted from complete proposals to problem identification
• Clear workflow separation: Problem reporting vs solution contribution paths
• Streamlined user experience: Clear exit point for non-contributors

Main Form Simplification

• Problem-focused intro: Emphasizes describing problems; team will design solutions unless user wants to contribute
• Streamlined guidance: Removed solution-specific advice from common mistakes section
• Simplified checklist: Focus on problem quality rather than complete proposals
• Core requirements: Only problem description + basic context needed for submission

Contributing Section Enhancement

• Clear decision point: "🎯 Just reporting a problem? You can click 'Submit new issue' right now!"
• Explicit continuation criteria: Only continue if proposing solutions or contributing implementation
• Moved solution design: "How should this be solved?" now in contributing section (required if contributing)
• Moved acceptance criteria: Now in contributing section (required if contributing)
• Consolidated contributor guidance: All implementation-related info in one section

Content Migration

• Moved implementation guidance: Review process and approval requirements to contributing section
• Relocated Discord guidance: Implementation-specific Discord contact moved to contributor section
• Transferred roadmap reference: Moved implementation-focused roadmap link to contributing section

User Experience Impact

For Problem Reporters (majority use case):

• Fill out problem description
• See clear "you can submit now" message
• Submit without technical complexity

For Contributors:

• Clear guidance on when to continue past problem description
• Comprehensive solution design requirements
• All technical analysis and implementation guidance in one place

This creates a much cleaner user experience where most users naturally stop after describing their problem, while contributors get all the detailed requirements they need for quality implementation.

---

Important

Streamlines feature request template to separate problem reporting from solution contribution, enhancing user experience and contributor guidance.

• Template Structure Overhaul:
  • Shifted focus from complete proposals to problem identification in feature_request.yml.
  • Separated workflow for problem reporting and solution contribution.
  • Clear exit point for non-contributors.
• Main Form Simplification:
  • Emphasizes problem description; team designs solutions unless user contributes.
  • Removed solution-specific advice from common mistakes.
  • Simplified checklist to focus on problem quality.
• Contributing Section Enhancement:
  • Added decision point for contributors: "Submit new issue" for problem reporters.
  • Moved solution design and acceptance criteria to contributing section.
  • Consolidated implementation guidance in one section.
• Content Migration:
  • Moved implementation guidance, Discord contact, and roadmap reference to contributing section.

^{This description was created by for 280ef56. You can customize this summary. It will automatically update as commits are pushed.}