[GitHub] incubator-fluo-website issue #23: Fluo 1.0.0
Github user keith-turner commented on the issue: https://github.com/apache/incubator-fluo-website/pull/23 > Also, this raises the question... do we really need apidocs published on our site Personally, I like having the javadocs on the Fluo website. However I am not opposed to dropping it from our website. I like that it will be less work for us. Also, javadoc.io does not currently have any advertisements. I looked at the source for javadoc.io, they seem to track using google analytics which is ok w/ me. We could put a base javadoc url in _config.yml. Then we can update all javadoc links to use this base. This will allow use to easily switch in the future if the website goes away or starts being sleazy in some way. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-fluo-website issue #23: Fluo 1.0.0
Github user ctubbsii commented on the issue: https://github.com/apache/incubator-fluo-website/pull/23 Diff is far too big to preview/review in GitHub. Can you strip out the commit which adds the javadocs, and just put in a placeholder to be fixed before merging? Also, this raises the question... do we really need apidocs published on our site, when they are already published to Maven Central, and hosted at various sites, such as https://javadoc.io/doc/org.apache.fluo/fluo-api/1.0.0-incubating ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
