Interesting discussion. There at the least seems to be a precedent of having docs externally hosted here: https://anypoint.mulesoft.com/apiplatform/forge-allura/#/portals/organizations/86c00a85-31e6-4302-b36d-049ca5d042fd/apis/32370/versions/33732
These docs are linked to from the Allura project page: https://forge-allura.apache.org/p/allura/wiki/Home/ In fact it seems like it’s a redirect from here: https://forge-allura.apache.org/p/allura/rest-api-docs/ On Apr 14, 2016, at 7:07 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 4/14/16, 8:21 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >> It looks to me that all you need is a gh-pages branch and everything just >> “works”. >> >> http://oli.jp/2011/github-pages-workflow/ >> >> I’m not sure how/where to search the Apache lists. > > Apache mailing lists are mostly public and Google can find a lot of > things. A few are private, but now that you are an ASF Member > (congratulations), you now have access to all the private lists as well. > > I went and found this thread [1]. The main concern is SSL. The secondary > concern seems to be about whether a.o URLs should redirect there. IMO, I > don't think there is a policy that our doc pages must be served from a.o > URLs. The main site probably should be (flex.a.o) but so what if our doc > pages aren't? I think the thread contains concerns about moving the > entire TLP site to github pages, but I don't think we are planning to do > that. Could we live without HTTPS for our doc pages? > > -Alex > > [1] > https://mail-archives.apache.org/mod_mbox/community-dev/201503.mbox/%3cCAL5 > zq9yj14dfwpqdunpmqrh5-zjuwsu82jlgo2qom3+2cvy...@mail.gmail.com%3e > >
