Diwa Design System

Help: Contribution

Contribute with production discipline: scoped changes, passing checks, and docs aligned with shipped behavior.

Prerequisites

  • - A scoped issue or proposal tied to user impact.
  • - Local environment can run workspace tests and storefront build.
  • - Awareness of accessibility and interaction contracts for touched components.

Step 1: Align work with an issue

Start from an existing issue (or open one) before coding to keep intent explicit.

Issue tracker:
https://github.com/jortega0033/diwa-design-system/issues

Step 2: Run quality checks before opening a PR

Validate tests and storefront build from the workspace root.

npm run test
npm run build:storefront

Step 3: Open a focused pull request

Include summary, test evidence, docs impact, and screenshots for UI changes.

Open PR:
https://github.com/jortega0033/diwa-design-system/compare

Implementation Notes

  • - Keep PRs scoped and avoid unrelated refactors.
  • - Update docs routes whenever behavior or workflows change.
  • - Call out accessibility, motion, and responsive implications in PR descriptions.

Troubleshooting

  • - If review feedback repeats, codify it in docs or templates.
  • - If CI fails but local passes, compare Node/browser/environment differences.
  • - If conflicts are frequent, reduce branch lifetime and PR scope.

Next Actions

Open Pull Request

Create a PR with testing and docs-impact notes.

Definition of Done

Use release gates before requesting merge.

Support

Ask for implementation help when blocked.