Page History

...

1. Clone the main Ignite repository and get to know our development process. You can fork the repository or have a clone of the main repository on your local machine.
2. Make sure a JIRA ticket is created for the change and the component property is set to documentation.

3. Find documentation sources under the ignite_root/docs/_docs directory and do necessary modifications:

   • Refer to the How to Contribute section of the documentation module to understand the syntax of the AsciiDoc format and the rest of the files located under the _docs directory.
   • Update the ignite_root/docs/_data/toc.yaml file if you add a new documentation page.
   • Every new documentation page must include the Apache 2.0 license header. 

4. Do a grammar check of your changes. Use Grammarly if you don't have a more advanced tool at hand.

5. (optional) Build the docs locally to test that your changes are applied properly and you didn't break anything.

6. If you added a new page or imported any external files, run the license checker: `mvn clean validate -DskipTests=true -P check-licenses`

7. Send a pull-request to the Ignite master, request the review from documentation maintainers.

8. Merge the changes after passing the review and after you confirm that all the automated checks performed by Travis CI are passed.
9. If applicable, cherry-pick the commit to the latest version of the docs (that is already published on the website or to be released).

Contributing Minor Changes

...