[
https://issues.apache.org/jira/browse/IGNITE-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis A. Magda updated IGNITE-13527:
------------------------------------
Description:
Publish the new docs onto the website:
* Add to the navigation menu
* Remove from the APIs page
* Update the documentation references across all the website pages (no any
reference to the readme.io)
* Update documentation contribution section:
https://ignite.apache.org/community/contribute.html
Readme Shutdown:
* Readme - redirect and shut down (or make available for 2.8 and earlier
versions). Add banners to every page announcing the new docs. Keep the readme
docs untouched for several weeks and then decide how to proceed. Google should
detect the news docs. Stop the indexing of the readme.io docs (Project Settings
->Indexing by robots is )
* <META NAME="ROBOTS" CONTENT="NOINDEX" /> add this to Appearance -> Customer
Include tags -> header
* Update the references on the website pointing to the new documentation
instead of the readme.io one.
* copy all readme sources and store them in the Ignite repo. Just in case if
anyone needs a page that was not ported.
was:
Publish the new docs onto the website:
* Add to the navigation menu
* Remove from the APIs page
* Update the documentation references across all the website pages (no any
reference to the readme.io)
Readme Shutdown:
* Readme - redirect and shut down (or make available for 2.8 and earlier
versions). Add banners to every page announcing the new docs. Keep the readme
docs untouched for several weeks and then decide how to proceed. Google should
detect the news docs. Stop the indexing of the readme.io docs (Project Settings
->Indexing by robots is )
* <META NAME="ROBOTS" CONTENT="NOINDEX" /> add this to Appearance -> Customer
Include tags -> header
* Update the references on the website pointing to the new documentation
instead of the readme.io one.
* copy all readme sources and store them in the Ignite repo. Just in case if
anyone needs a page that was not ported.
> Ignite Docs: redirect traffic from readme.io to the new docs
> ------------------------------------------------------------
>
> Key: IGNITE-13527
> URL: https://issues.apache.org/jira/browse/IGNITE-13527
> Project: Ignite
> Issue Type: Task
> Affects Versions: 2.9
> Reporter: Denis A. Magda
> Assignee: Denis A. Magda
> Priority: Critical
> Labels: new-docs
>
> Publish the new docs onto the website:
> * Add to the navigation menu
> * Remove from the APIs page
> * Update the documentation references across all the website pages (no any
> reference to the readme.io)
> * Update documentation contribution section:
> https://ignite.apache.org/community/contribute.html
> Readme Shutdown:
> * Readme - redirect and shut down (or make available for 2.8 and earlier
> versions). Add banners to every page announcing the new docs. Keep the readme
> docs untouched for several weeks and then decide how to proceed. Google
> should detect the news docs. Stop the indexing of the readme.io docs (Project
> Settings ->Indexing by robots is )
> * <META NAME="ROBOTS" CONTENT="NOINDEX" /> add this to Appearance -> Customer
> Include tags -> header
> * Update the references on the website pointing to the new documentation
> instead of the readme.io one.
> * copy all readme sources and store them in the Ignite repo. Just in case if
> anyone needs a page that was not ported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
