Good documentation is the foundation of good software and your contributions can help make good documentation great.
If you're an ExpressionEngine user, then you have something to add. There is always room for more examples, clarifications, corrections and updates. Jump in and make a pull request or give us a heads up by reporting an issues.
Table of Contents:
Suggesting a change is easy and there is no way you'll mess up the public repo.
Start by forking the repository, the new branch you create is the one you'll do your work in.
Once you have your new branch, make sure you're actually in it! Then make your changes inside of your feature branch.
Push your changes to your fork of the repository, and when you're done, send us a pull request.
We'll take a look at your pull request, make sure everything looks alright, ask for any needed changes, and then merge it into the main code.
Please refer to style_guide.rst for samples and ReST convention standards used in the ExpressionEngine user guide. Please note that standard ReST renders will not be able to parse all of the directives, as many are specific to Sphinx.
If your contribution adds new pages to the user guide, please use the following attribution at the top of the file:
.. # This source file is part of the open source project
# ExpressionEngine User Guide (https://github.com/ExpressionEngine/ExpressionEngine-User-Guide)
#
# @link https://expressionengine.com/
# @copyright Copyright (c) 2003-2018, EllisLab, Inc. (https://ellislab.com)
# @license https://expressionengine.com/license Licensed under Apache License, Version 2.0Want to help but not a little daunted by the idea of making a pull request? We still want to hear from you. You can report errors in the documentation as issues in the github repo. Just remember, the more detailed the report, the more likely someone will be able to make improvements.