[
https://issues.apache.org/jira/browse/IGNITE-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063251#comment-17063251
]
YuJue Li commented on IGNITE-7595:
----------------------------------
If the development team investigates Docusaurus, it is also recommended to
investigate VuePress. I think it is more powerful than Docusaurus.
At present, Chinese documents use VuePress,for details, see
https://vuepress.vuejs.org/
> Find and switch to alternate documentation engine
> -------------------------------------------------
>
> Key: IGNITE-7595
> URL: https://issues.apache.org/jira/browse/IGNITE-7595
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Denis A. Magda
> Assignee: Denis A. Magda
> Priority: Minor
> Attachments: Docusaurus-GitBook comparison.docx,
> readme-markdown-mapping.xlsx
>
>
> Current readme.io documentation has many drawbacks that make the life of
> Ignite technical writers hard. Some of the problems are:
> * Each "version" is just a copy of the previous one. When fixing something,
> you have to update
> all the versions.
> * No good way to review changes.
> * "Propose edit" functionality is a not suitable for review. You can only
> accept or reject an
> edit, no way to communicate with a contributor, etc
> * There is no way to prevent Google from indexing old documentation
> versions. Thus, it's common to come across old doc version in a google
> search.
> We might consider GitHub based documentation or another approach. The
> discussion is here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Move-documentation-from-readme-io-to-GitHub-pages-td16409.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
