Page History

6.3.4.

Publish technical documentation

Publish the technical documentation on the website: How to Document - Publishing to the website

6.3.5. Update

references to API docs

on the website, SEO updates

Update the latest APIs doc reference on ignite.apache.org:

1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/2.9.0/$1 [L]
2. Add the following tag to all .html files: <link rel="canonical" href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html" />
3. Use the script that automates the update or contact Mauricio Stekl (mauricio@gridgain.com) who can assist with this step.
4. Commit changes to the SVN. A patch will update all documents may have huge size, so console SVN client is recommended.

This script do some Search engine optimization (SEO) updates to new/old .html files, like adding NOINDEX metatag to older version; add canonical URL to latest docs; and add GA code.  

6.3.6. Prepare HTML release notes from text release notes

Checkout SVN repository for Apache Ignite site: https://svn.apache.org/repos/asf/ignite/site/trunk

For speed up this operation make sure to limit branches in checkout operation.

Just copy-paste latest release notes from previous release, replace text formatting with headers, lists items.

Place these notes to corresponding release folder, for example releases/2.7.5. If folder is absent, check results of step 6.2.3.

Commit changes. File should be available on the site automatically.