[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015000#comment-16015000 ]
Robert Kanter commented on OOZIE-2734: -------------------------------------- Another option we shouldn't overlook is the newer maven-site-plugin. We're currently on some funny version of 2.x, but the latest version is 3.x and was presumably used to generate it's own website, which looks perfectly fine: https://maven.apache.org/plugins/maven-site-plugin/index.html. Looks like it supports a variety of formats: https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Documentation_formats > 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)