Contributing to Documentation
You Don’t Need to Be Tech-Savvy
Another important point to mention is that you don’t need to be tech-savvy at all to contribute to docs.
Open any text editor, start your research, and note down everything that could be useful.
The Process
Most of the time these notes are just links to posts, repos, or configurations that worked for me. The whole writing is done at the end.
At the current state, it does not matter that much how you write the documentation, as long as everything is somewhat logical, easy to reproduce, and actually works lmao.
What to Document
Valuable documentation includes:
- Installation steps that worked for you
- Package configurations
- Troubleshooting common errors
- Use cases and workflows
- Hidden features you discovered
Where to Contribute
Contributions can be made to:
- The official BerryCore repository
- This documentation (Cyberbridge)
- Community forums and discussion groups
- Your own blog or notes shared with others
Why It Matters
Contributing to documentation for a project in such a state is really essential. Even I, who literally spends his whole time in this area, had to wrap my head many times to find the right information.