Docs Navigation Open
Contributing to Documentation
Turn repeated support knowledge and real project experience into clearer documentation.
Useful documentation usually begins with a real confusion point. If you had to search old forum threads, read code, or test several failed options, that is probably documentation debt.
Good Documentation Work
- replace vague wording with tested instructions
- keep classic component knowledge, but rewrite it in clear English
- update old 1.4-era guidance for Evo 3 runtime and package flows
- add examples that reflect current code and current extras
What Not to Do
- do not write long generic intros
- do not describe features that were not verified in code or real projects
- do not hide important classic behavior behind marketing wording
Previous
How to Get Help
Good support requests include versions, the failing flow, expected behavior, actual behavior, and reproduction steps.
Next
Contributing to Evolution CMS
Contributions include code, testing, docs, issues, reviews, and maintenance across the ecosystem.