1. Start in the GitHub tracker
Use the repository issue tracker as the canonical support intake surface.
Issue tracker:
https://github.com/jortega0033/diwa-design-system/issuesHelp Introduction
Help pages centralize support, FAQ, bug reporting, feature requests, and contribution workflow. This section is GitHub-first so requests stay visible, traceable, and actionable.
Prerequisites
- - Choose the request type first: Support, Bug Report, Feature Request, or Contribution.
- - Capture versions, framework/runtime, and deterministic reproduction steps.
- - Check related docs and open issues before filing to avoid duplicates.
Request Flow (3 Steps)
2. Prepare a deterministic report
Include exact versions and a reproducible sequence.
### Environment
- @diwacopilot/components: x.y.z
- Framework + version:
- Browser + version:
### Reproduction
1. ...
2. ...
3. ...
### Expected
...
### Actual
...3. Open the issue with supporting links
Reference the docs pages you reviewed and explain where behavior diverges.
Create issue:
https://github.com/jortega0033/diwa-design-system/issues/newHelp Topics
Support
Workflow, templates, and next actions for this support channel.
FAQ
Workflow, templates, and next actions for this support channel.
Feature Request
Workflow, templates, and next actions for this support channel.
Bug Report
Workflow, templates, and next actions for this support channel.
Contribution
Workflow, templates, and next actions for this support channel.
Troubleshooting Notes
- - If triage stalls, add a minimal reproduction repository and exact version data.
- - If issue type is unclear, file under Support and route to Bug or Feature Request during triage.
- - If duplicate issues appear often, update FAQ and link a canonical issue.