[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997397#comment-15997397
]
Robert Kanter commented on OOZIE-2734:
--------------------------------------
The Apache Ignite docs look really nice, but it looks like they're actually
hosted by http://readme.io, so I don't think that would work for us.
I was also talking with [~gezapeti], and he tried out a few autoconverting
tools and they weren't very good. It's probably best to just start from
scratch. That would also allow whoever does it to reorganize things as they go
through it, but they can still copy-paste large portions of the existing docs
contents.
> Switch docs from twiki to markdown
> ----------------------------------
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
> Issue Type: Improvement
> Components: docs
> Affects Versions: trunk
> Reporter: Robert Kanter
>
> This won't be a fun JIRA, but it would be great if we could switch to
> something easier to work with and better supported like markdown, and get rid
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
> it's better to convert from the rendered html instead of the twiki. But who
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs
> in better shape, as they could really use some reorganizing. Though we can
> keep that for a separate task.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
