# Contributing > Contribute to ShellUI development Source: https://shellui.dev/docs/v0.4/contributing We welcome contributions to ShellUI! Whether it's bug fixes, new components, documentation improvements, or feature suggestions, your help makes ShellUI better for everyone. ## How to Contribute ### Reporting Bugs Found a bug? Please open an issue on [GitHub](https://github.com/shellui-dev/shellui/issues) with: - A clear description of the bug - Steps to reproduce - Expected vs actual behavior - Your environment (OS, .NET version, etc.) - Screenshots if applicable ### Suggesting Features Have an idea for a new feature or component? Open an issue with: - A clear description of the feature - Use cases and examples - Why this would be valuable ### Contributing Code 1. **Fork the repository** ```bash git clone https://github.com/your-username/shellui.git cd shellui ``` 2. **Create a branch** ```bash git checkout -b feature/your-feature-name ``` 3. **Make your changes** - Follow the existing code style - Add tests if applicable - Update documentation 4. **Test your changes** ```bash dotnet build dotnet test ``` 5. **Commit and push** ```bash git commit -m "Add: your feature description" git push origin feature/your-feature-name ``` 6. **Open a Pull Request** - Provide a clear description - Reference any related issues - Include screenshots for UI changes ## Development Setup ### Prerequisites - .NET 10 SDK - Node.js (for Tailwind CSS development) - Git ### Getting Started 1. Clone the repository 2. Build the solution: ```bash dotnet build ``` 3. Run tests: ```bash dotnet test ``` ## Component Development When adding new components: 1. Follow the existing component structure 2. Use Tailwind CSS for styling 3. Ensure accessibility (WCAG 2.1 AA) 4. Add proper C# types and parameters 5. Include documentation 6. Add examples to the demo app ## Code Style - Follow C# coding conventions - Use meaningful variable names - Add XML documentation comments - Keep components focused and composable ## Documentation When contributing documentation: - Use clear, concise language - Include code examples - Add screenshots for visual components - Keep examples up to date ## Questions? - [GitHub Discussions](https://github.com/shellui-dev/shellui/discussions) - [GitHub Issues](https://github.com/shellui-dev/shellui/issues) Thank you for contributing to ShellUI!