Community feedback

Discuss the Core 1.0 beta

Start with the dedicated Nerio Core 1.0 beta feedback discussion. It is the canonical public intake for release feedback, including integration problems, missing guidance, browser or device behavior, and accessibility results.

Use the broader Nerio Community to browse existing conversations. Use Ideas for product suggestions and Q&A for questions that should have a durable answer.

What to include

• The exact Nerio version or commit, and whether you installed packages or editable source through the Registry and CLI.
• Your framework, Node.js version, browser, operating system, device, and assistive technology when relevant.
• What you expected, what happened, and the smallest safe reproduction or sequence of steps that demonstrates the behavior.
• Screenshots, recordings, or code excerpts only when they contain no credentials, personal data, or private product information.

How feedback becomes work

Maintainers triage release feedback in the discussion first. Confirmed, reproducible bugs and bounded release blockers become focused GitHub Issues; broader proposals stay in Ideas until their scope and product value are clear. Existing answers remain in Q&A so other consumers can find them.

A public comment informs the external-feedback gate, but does not by itself satisfy release evidence. Stable readiness still requires the recorded independent-consumer evaluations and manual accessibility and physical-device results defined by the release plan.

Security and private reports

Do not post suspected vulnerabilities, credentials, or sensitive consumer data publicly. Follow the repository's security policy and use its private reporting path instead.