Add community governance and improve documentation (#197)

* Add community governance and improve documentation

- Add CODE_OF_CONDUCT.md with community behavior guidelines
- Add CONTRIBUTING.md with contribution guidelines and development workflow
- Add LICENSE with project license information
- Improve README workflow monitoring section with detailed bullet points

* Standardize headings and bullet points in README

Updated formatting and capitalization for consistency.

Author: igorpecovnik

CODE_OF_CONDUCT.md

@@ -0,0 +1,15 @@
+## Code of Conduct
+
+We strive to create a welcoming and inclusive environment for everyone. To ensure this, please follow these guidelines:
+
+- **Be Respectful and Considerate**: Remember that our community is global, and language and cultural differences may exist. Avoid using offensive or inappropriate language. Understand that what may be acceptable in one culture could be considered offensive in another.
+
+- **Seek Clarification When Needed**: If you don't understand something, don't hesitate to ask questions. Similarly, if someone asks a question, be patient and provide a clear and helpful response. Avoid being offended by questions or requests for clarification.
+
+- **Communication Challenges**: Recognize that not everyone finds communication easy. If you have difficulty expressing yourself, that's okay. We ask everyone to be patient and understanding, and to focus on the message rather than the way it is conveyed.
+
+- **Be Patient and Understanding**: Recognize that contributors come from various backgrounds and levels of experience. If someone makes a mistake, offer constructive feedback rather than criticism.
+
+- **Encourage Inclusivity**: Make an effort to include everyone in discussions, especially those who might be new or less experienced. Avoid jargon or acronyms without explanations, as these can be confusing for newcomers.
+
+By following these guidelines, we can ensure a positive and productive environment for all contributors. If you encounter any issues or have concerns, please reach out to the project maintainers on GitHub, the Armbian forums, or Discord.

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing to Armbian Infrastructure
+
+We welcome contributions!
+
+- **Bug reports** — [Open an issue](https://github.com/armbian/armbian.github.io/issues)
+- **Feature requests** — Let's discuss it
+- **Pull requests** — Code improvements are always welcome
+- **Documentation** — Help others get started
+- **Infrastructure improvements** — CI/CD workflows, automation scripts, and data pipelines
+
+### Development Workflow
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+
+## Other ways to contribute
+
+* [Become a new board maintainer](https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/)
+* [Apply for one of the positions](https://forum.armbian.com/staffapplications/)
+* [Help us covering costs](https://forum.armbian.com/subscriptions/)
+* [Help community members in the Forum](https://forum.armbian.com/)
+* [Check forum announcements section for any requests for help from the community](https://forum.armbian.com/forum/37-announcements/)