Feature Request Guidelines

[q-soriarty]

How to Propose a Feature

This category is for discussing new ideas and enhancements before they become formal issues.

Before Posting

1. Check existing milestones — your idea may already be planned: Milestones
2. Search existing discussions — someone may have proposed something similar
3. Review the architecture — understand current design constraints: ARCHITECTURE.md

Proposal Format

A good feature proposal includes:

### Problem
What problem does this solve? Who is affected?

### Proposed Solution
How should it work from the user's perspective?

### Alternatives Considered
What other approaches were evaluated?

### Scope
Which components are affected? (frontend, backend, build-server, monitor-server, infra)

### Acceptance Criteria
How do we know this is done?

What Happens Next

1. Community discusses the proposal
2. If accepted, a GitHub Issue is created and assigned to the appropriate milestone
3. The discussion is linked from the issue for context

Scope Labels

Label	Component
frontend	React visual editor
backend	ASP.NET Core API
build-server	PLC build server
monitor-server	PLC monitoring containers
infra	Docker, Traefik, CI/CD
auth	Keycloak, authentication