Thank you for your interest in contributing to the QCloud Systems documentation site. To maintain consistency and quality, please follow the guidelines below.

---

Branching Strategy

• main — Production-ready documentation.
• feature/<name> — New documentation sections or layout enhancements.
• fix/<name> — Bug fixes, typos, or minor improvements.

---

Commit Message Format

Use clear, descriptive commit messages:

• docs: add new architecture diagram
• style: improve sidebar spacing
• fix: correct DNS instructions
• feat: add dark mode toggle

---

Documentation Standards

• Keep content concise, technical, and accurate.
• Use consistent heading levels (h1, h2, h3).
• Prefer lists and code blocks for clarity.
• Avoid unnecessary dependencies — keep the site static and lightweight.

---

Pull Request Process

1. Fork the repository.
2. Create a feature or fix branch.
3. Commit changes with clear messages.
4. Submit a pull request describing:
   • What changed
   • Why it changed
   • Any relevant context or screenshots

---

Code Style

• Use semantic HTML.
• Keep CSS modular and readable.
• Avoid inline styles unless necessary.
• Maintain accessibility (contrast, readable font sizes, ARIA labels when needed).

---

Licensing

By contributing, you agree that your contributions will be licensed under the MIT License of this repository.