First off, thank you for considering contributing to the CodeCampus User Guide! It's people like you that make CodeCampus a great resource for students worldwide.
We aim to provide the best possible documentation for beginner software engineers. We don't just want to list commands; we want to teach the "Why" and the "How" of professional development.
- Use the GitHub Issue Tracker.
- Describe the bug and, if possible, suggest a fix.
- If you think a tool or workflow is missing, open an issue to discuss it.
This is the most impactful way to contribute! However, we have strict quality standards. All new tool documentation MUST follow the Antigravity.md Specification.
- What is it?: Conceptual, beginner-friendly explanation.
- Installation: Proper tabs for Ubuntu, Arch, Fedora, and openSUSE.
- Why this tool matters (In Depth): The most important part—explain the "Why."
- How students will actually use it: Practical, concrete examples.
- Professional Insight: Senior-level tips and pitfalls to avoid.
- Professional Tone: Avoid slang and emojis in the documentation body.
- Direct Language: Be concise and avoid filler words.
- Markdown Headers: Use only
#,##, and###appropriately. - No Marketing: We are here to teach, not to sell.
- Fork the repo and create your branch from
main. - If you've added code or documentation that should be tested, add tests or verify with
mkdocs serve. - Ensure your documentation adheres to the
Antigravity.mdspec. - Open a Pull Request with a clear description of your changes.
By contributing, you agree that your contributions will be licensed under the project's CodeCompass Personal Use License.
Happy coding! 🚀