Table of Contents |
---|
Ignite documentation sources are stored in the main Ignite repository together with the rest of the Ignite source code. The docs are written in the AsciiDoc format and transformed into the HTML form with the Jekyll toolchain. The published HTML version of the docs, that is accessible under the URL https://ignite.apache.org/docs/, is stored in the Ignite Website repository. The picture below explicates on how the things are tethered together:
Info | ||||||
---|---|---|---|---|---|---|
| ||||||
Download the archive below if you're looking for a documentation page that existed on the legacy documentation portal - https://apacheignite.readme.io
|
The sections below cover the code contribution and publication processes in detail.
...
Find documentation sources under the ignite_root/docs/_docs directory and do necessary modifications:
Do a grammar check of your changes. Use Grammarly if you don't have a more advanced tool at hand.
If you added a new page or imported any external files, run the license checker: `mvn clean validate -DskipTests=true -P check-licenses`
Send a pull-request to the Ignite master, request the review from documentation maintainers.
...
Once an Ignite version is released, the release branch gets frozen and you won't be able to commit to it any changes (including documentation updates). This section explains how to update the docs in such conditions:
...
a documentation update is merged to the master branch, cherry-pick it to the latest published version on the website or to a version that is to be released
...
...
...
...
If you rename an already published page or change the page's path in the ignite_root/docs/_docsdata/toc.yaml file, you must configure a proper redirect from the old to the new URL in the following files of the Ignite website:
...
./build.sh --version=2.9.0
1 --github-branch=IGNITE
ignite-2.9.1 --latest
./build.sh --version=2.9.0 --github-branch=ignite-2.9-docs
RewriteRule ^docs/latest/(.*)$ /docs/2.9.1/$1 [L]
NOTE: The docs for Ignite 3.x can be published on the same way, the script will detect it and pull the content from the respective repo. For example:
./build.sh --version=3.0.0-alpha1 --github-branch=ignite-3.0.0-alpha1
The GitHub Action is used to automatically update documentation for released versions. (Supports 2.x versions since 2.10)
The push event to a released branch triggers script to publish changes to the site.
Commit changes to the Ignite repository and make sure that the site updated.
Use the same command to generate an updated version of already released docs but do NOT specify the "–latest" flag:
./build.sh --version=2.89.0 --github-branch=IGNITEignite-2.89-docs
As for the rest, follow the procedure described in the Publishing New Version section above, except for step #5.
If you are rebuilding the docs for the latest Ignite version, remember to use '--latest' flag
There is a "Docs Feedback" button in the bottom right corner of all documentation pages, which allows anyone to leave comments.
Those comments go to https://app.bugyard.io/. Credentials are at https://svn.apache.org/repos/private/pmc/ignite/credentials/bugyard.io (PMC only area, use Apache ID to access).
Docs Scope | Maintainers |
---|---|
All docs | Denis Magda (dmagda@apache.orgNikita Safonov (nsafonov@gridgain.com), Igor Gusev (igusev@gridgain.com) |
.NET-specific docs maintainers | Pavel Tupitsyn (ptupitsyn@apache.org) |
C++, Python, Node.JS, PHP-specific docs | Igor Sapego (isapego@gridgain.com) |
...