[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user keith-turner commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83218320 --- Diff: _layouts/default.html --- @@ -31,8 +31,10 @@ -Documentation -

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user keith-turner commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83219860 --- Diff: _posts/release-notes/2016-09-27-fluo-1.0.0-incubating.md --- @@ -1,16 +1,19 @@ --- title: Fluo 1.0.0-incubating

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user keith-turner commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83219527 --- Diff: _posts/blog/2016-09-27-1.0.0-incubating-is-released.md --- @@ -0,0 +1,12 @@ +--- +title: "Fluo 1.0.0-incubating is

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user keith-turner commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83222182 --- Diff: docs/fluo/1.0.0-incubating/metrics.md --- @@ -0,0 +1,117 @@ +--- +layout: fluo-doc +title: Fluo Metrics

[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

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user mikewalch commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83278509 --- Diff: _posts/blog/2016-09-27-1.0.0-incubating-is-released.md --- @@ -0,0 +1,12 @@ +--- +title: "Fluo 1.0.0-incubating is

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user mikewalch commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83278587 --- Diff: docs/fluo/1.0.0-incubating/install.md --- @@ -0,0 +1,210 @@ +--- +layout: fluo-doc +title: Fluo Install Instructions

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user mikewalch commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83278537 --- Diff: _posts/release-notes/2016-09-27-fluo-1.0.0-incubating.md --- @@ -1,16 +1,19 @@ --- title: Fluo 1.0.0-incubating Release

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user ctubbsii commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83275841 --- Diff: _layouts/default.html --- @@ -31,8 +31,10 @@ -Documentation -

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user mikewalch commented on a diff in the pull request: https://github.com/apache/incubator-fluo-website/pull/23#discussion_r83278560 --- Diff: docs/fluo/1.0.0-incubating/metrics.md --- @@ -0,0 +1,117 @@ +--- +layout: fluo-doc +title: Fluo Metrics +version:

[GitHub] incubator-fluo-website issue #25: Add link to 'Latest Release' on main page

GitHub user mikewalch opened an issue: https://github.com/apache/incubator-fluo-website/issues/25 Add link to 'Latest Release' on main page From discussion in https://github.com/apache/incubator-fluo-website/pull/23 --- If your project is set up for it, you can reply

[GitHub] incubator-fluo-website issue #26: Add linkchecker to readme

GitHub user keith-turner opened an issue: https://github.com/apache/incubator-fluo-website/issues/26 Add linkchecker to readme I used following command to check website... could add this to the readme ``` linkchecker --no-follow-url=".*apidocs.*" --check-extern

[GitHub] incubator-fluo-website pull request #23: Fluo 1.0.0

Github user asfgit closed the pull request at: https://github.com/apache/incubator-fluo-website/pull/23 --- 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

Jenkins build became unstable: Fluo #91

See