Contributing to quot.is

Welcome to quot.is! We appreciate your interest in contributing to our project. By contributing, you become part of>

Reporting Issues

If you encounter any issues or bugs while using quot.is, please help us improve by reporting them. Before submittin>

We encourage you to contribute new features, improvements, or bug fixes to quot.is. Here's how you can do it:

Fork the quot.is repository to your GitHub account.
Create a new branch for your changes: git checkout -b feature/your-feature-name or bugfix/your-bugfix-name.
Make your changes, ensuring you follow our coding conventions and best practices.
Commit your changes with clear commit messages: git commit -m "Add feature/fix for XYZ".
Push your changes to your forked repository: git push origin feature/your-feature-name.
Create a pull request from your branch to our main branch.
Provide a descriptive title and detailed description of your changes in the pull request.

We'll review your pull request and work with you to address any feedback before merging it into the main project.

We maintain a consistent code style in quot.is to ensure readability and maintainability. Please adhere to the foll>

Indentation: Use 2 spaces for indentation.
Naming Conventions: Follow descriptive and meaningful naming for variables, functions, and classes.
Comments: Include comments to explain complex or critical parts of your code.
Testing: Add unit tests for new features or changes to ensure code reliability.

Thank you for your valuable contributions to quot.is. Together, we can make this platform even more inspiring and e>