Aaron Markham created MXNET-1024:
------------------------------------
Summary: Possible refactor to use Jekyll
Key: MXNET-1024
URL: https://issues.apache.org/jira/browse/MXNET-1024
Project: Apache MXNet
Issue Type: Improvement
Reporter: Aaron Markham
The site needs to be refactored anyway and have a new template applied. If this
is the case, why not switch to Jekyll? There are several advantages to using
Jekyll. It has an interactive mode where it will rebuild the website
automatically when changes are detected. This is great for development. It has
a lot of modern publishing features that would be well received.
The drawback at this point is primarily that Sphinx is used for wrangling in
all of the other language bindings' API builds. So it would just be about
applying a new template and website build system, it would also require porting
over all of the other build steps.
That being said, I'm inclined to move these pieces over to CMAKE. This
conversion for the rest of MXNet is already underway. Using CMAKE would be
fantastic as integrates well with Sphinx and Doxygen, and could be used to call
the ScalaDocs, Clojure docs, R docs, and future docs build processes such as
JavaDocs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
