I think a separate singa-doc repo is good. Is it easier to set up some hooks for CI.
On Tue, Dec 10, 2019 at 7:00 PM Moaz Reyad (Jira) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/SINGA-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992430#comment-16992430 > ] > > Moaz Reyad commented on SINGA-499: > ---------------------------------- > > There is an old project for SINGA on readthedocs [here| > https://readthedocs.org/projects/apache-singa/]. If you want to use it, I > can add new maintainers if you give me their user names in readthedocs. > > May be we can also move all the website folders from the [singa repository| > https://github.com/apache/singa] to [singa-site repository| > https://github.com/apache/singa-site]. Consider also asking INFRA to > create a third repository singa-docs for documentation if needed. Many ASF > projects has docs repository as you can see in [gitbox repositories| > https://gitbox.apache.org/repos/asf]. > > > Improve SINGA website > > --------------------- > > > > Key: SINGA-499 > > URL: https://issues.apache.org/jira/browse/SINGA-499 > > Project: Singa > > Issue Type: Improvement > > Reporter: wangwei > > Priority: Major > > Labels: website > > > > This ticket proposes to improve the SINGA website to separate the > documentation from the API pages. > > The documentation would be built by [https://docusaurus.io/], like [ > https://pulsar.apache.org/. |https://pulsar.apache.org/] > > The framework is widely used for generating websites for open-source > projects. It also provides the translation feature via crowdsourcing. > > The API pages will still be built using Sphinx. One change is to host it > on [https://readthedocs.org/,] which is easier to maintain. > > > > Any comments? > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
