sonarqube-issues-exporter
Version:
Enterprise-level SonarQube issues exporter with TypeScript support for generating comprehensive HTML reports with dark theme
97 lines (67 loc) ⢠4.1 kB
Markdown
# š Documentation
Welcome to the SonarQube Issues Exporter documentation! This directory contains comprehensive guides and references organized by audience and purpose.
## š Quick Navigation
### šÆ For Users
- **[NPM Guide](./user-guide/npm-guide.md)** - Complete installation and usage guide
- **[Migration Guide](./user-guide/migration.md)** - Upgrading from previous versions
- **[Security Guide](./user-guide/security.md)** - Security best practices and considerations
### šØāš» For Developers & Contributors
- **[Contributing Guide](./development/contributing.md)** - How to contribute to the project
- **[Commit Guidelines](./development/commit-guidelines.md)** - Conventional commit standards
- **[Publishing Guide](./development/publishing.md)** - Release and publishing process
- **[Versioning Guide](./development/versioning.md)** - Semantic versioning strategy
### š Project Information
- **[Enhancement Plan](./project/enhancement-plan.md)** - Current development roadmap and phases
- **[Documentation Updates](./project/documentation-updates.md)** - Recent documentation changes
## š Getting Started
### New Users
1. Start with the **[NPM Guide](./user-guide/npm-guide.md)** for installation and basic usage
2. Check the **[Security Guide](./user-guide/security.md)** for best practices
3. Visit the main **[README](../README.md)** for feature overview and examples
### Contributors
1. Read the **[Contributing Guide](./development/contributing.md)** for development setup
2. Follow **[Commit Guidelines](./development/commit-guidelines.md)** for your contributions
3. Check the **[Enhancement Plan](./project/enhancement-plan.md)** for current development priorities
### Maintainers
1. Review **[Publishing Guide](./development/publishing.md)** for release process
2. Understand **[Versioning Guide](./development/versioning.md)** for version management
3. Monitor **[Documentation Updates](./project/documentation-updates.md)** for recent changes
## š Directory Structure
```
docs/
āāā README.md # This file - documentation overview
āāā user-guide/ # End-user documentation
ā āāā npm-guide.md # Installation & usage
ā āāā migration.md # Version migration
ā āāā security.md # Security considerations
āāā development/ # Developer documentation
ā āāā contributing.md # Contribution guidelines
ā āāā commit-guidelines.md # Commit conventions
ā āāā publishing.md # Release process
ā āāā versioning.md # Version management
āāā project/ # Project management docs
āāā enhancement-plan.md # Development roadmap
āāā documentation-updates.md # Doc change history
```
## š Root Level Files
Some documentation remains at the project root for immediate visibility:
- **[README.md](../README.md)** - Main project overview and quick start
- **[CHANGELOG.md](../CHANGELOG.md)** - Auto-generated release history
- **[LICENSE](../LICENSE)** - MIT license information
## š¤ Contributing to Documentation
Found an issue or want to improve the documentation?
1. **Quick fixes**: Edit the relevant file and submit a pull request
2. **Major changes**: Open an issue first to discuss the changes
3. **New sections**: Follow the existing structure and update this README
### Documentation Standards
- Use clear, concise language
- Include code examples where helpful
- Keep navigation links updated
- Follow the established directory structure
- Test all links and examples before submitting
## š Support
- **Issues**: [GitHub Issues](https://github.com/The-Lone-Druid/sonarqube-issues-exporter/issues)
- **Discussions**: [GitHub Discussions](https://github.com/The-Lone-Druid/sonarqube-issues-exporter/discussions)
- **Security**: See [Security Guide](./user-guide/security.md)
---
**Happy coding!** š