Thanks for your interest in contributing to ngCorex All contributions are welcome - from bug reports to documentation fixes.
ngCorex is still in early development, so we value:
- Clear problem descriptions
- Small, focused changes
- Thoughtful discussion before large refactors
If you find a bug:
- Describe what you expected to happen
- Describe what actually happened
- Include minimal reproduction steps if possible
Please search existing issues before opening a new one.
Feature requests are welcome, especially if they:
- Improve developer experience
- Reduce confusion
- Align with design-token workflows
For larger ideas, open an issue first to discuss direction.
Before submitting a PR:
- Fork the repository
- Create a feature branch
- Keep changes focused and incremental
- Ensure the project builds successfully
- Add or update documentation if needed
ngCorex prioritizes:
- Clarity over cleverness
- Backward compatibility
- Beginner-friendly behavior
- ngCorex is a build-time tool, not a runtime framework
- Breaking changes are avoided unless clearly justified
- Features are added deliberately, not reactively
If you're unsure about an approach, open an issue first - discussion is encouraged.
Be respectful, constructive, and kind.
Harassment or abusive behavior will not be tolerated.
Thank you for helping make ngCorex better