beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@apache.org
Subject [1/4] incubator-beam-site git commit: Add missing site.baseurls
Date Sat, 05 Nov 2016 00:52:25 GMT
Repository: incubator-beam-site
Updated Branches:
  refs/heads/asf-site e96b07f54 -> 228a6c91d


Add missing site.baseurls


Project: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/commit/a7c71d23
Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/tree/a7c71d23
Diff: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/diff/a7c71d23

Branch: refs/heads/asf-site
Commit: a7c71d23932162c87774ffbfcff81260c3ffaedb
Parents: e96b07f
Author: Dan Halperin <dhalperi@google.com>
Authored: Fri Nov 4 12:34:04 2016 -0700
Committer: Dan Halperin <dhalperi@google.com>
Committed: Fri Nov 4 17:46:00 2016 -0700

----------------------------------------------------------------------
 _includes/footer.html                           |  2 +-
 _includes/head.html                             |  2 +-
 _includes/header.html                           |  2 +-
 _posts/2016-08-03-six-months.md                 |  2 +-
 .../2016-10-12-strata-hadoop-world-and-beam.md  |  2 +-
 _posts/2016-10-20-test-stream.md                |  6 ++---
 blog/index.md                                   |  2 +-
 coming-soon.md                                  |  2 +-
 contribute/contribution-guide.md                |  8 +++----
 contribute/index.md                             |  2 +-
 contribute/logos.md                             |  9 ++++----
 contribute/release-guide.md                     | 14 ++++++------
 contribute/team.md                              |  5 ++--
 contribute/work-in-progress.md                  |  6 ++---
 documentation/index.md                          |  7 +++---
 documentation/pipelines/create-your-pipeline.md |  2 +-
 documentation/pipelines/design-your-pipeline.md |  2 +-
 documentation/pipelines/test-your-pipeline.md   |  2 +-
 documentation/programming-guide.md              |  5 ++--
 documentation/resources.md                      |  4 ++--
 documentation/runners/capability-materix.md     |  5 ++--
 documentation/runners/dataflow.md               |  2 +-
 documentation/runners/direct.md                 |  2 +-
 documentation/runners/flink.md                  |  2 +-
 documentation/runners/index.md                  |  2 +-
 documentation/runners/spark.md                  |  2 +-
 documentation/sdks/index.md                     |  2 +-
 documentation/sdks/java.md                      |  6 ++---
 documentation/sdks/javadoc/index.md             |  2 +-
 get-started/beam-overview.md                    |  7 +++---
 get-started/downloads.md                        |  2 +-
 get-started/index.md                            |  9 ++++----
 get-started/mobile-gaming-example.md            | 24 ++++++++++----------
 get-started/quickstart.md                       |  5 ++--
 get-started/releases.md                         |  5 ++--
 get-started/support.md                          |  3 +++
 get-started/wordcount-example.md                |  2 +-
 index.md                                        |  6 ++---
 38 files changed, 93 insertions(+), 81 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/_includes/footer.html
----------------------------------------------------------------------
diff --git a/_includes/footer.html b/_includes/footer.html
index 922c68e..85830ef 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -4,7 +4,7 @@
           <footer>
               <p class="text-center">&copy; Copyright 2016
                 <a href="http://www.apache.org">The Apache Software Foundation.</a> All Rights Reserved.</p>
-                <p class="text-center"><a href="/privacy_policy">Privacy Policy</a> |
+                <p class="text-center"><a href="{{ site.baseurl }}/privacy_policy">Privacy Policy</a> |
                 <a href="{{ "/feed.xml" | prepend: site.baseurl }}">RSS Feed</a></p>
           </footer>
       </div>

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/_includes/head.html
----------------------------------------------------------------------
diff --git a/_includes/head.html b/_includes/head.html
index 02c7727..80f1f20 100644
--- a/_includes/head.html
+++ b/_includes/head.html
@@ -23,5 +23,5 @@
     ga('send', 'pageview');
 
   </script>
-  <link rel="shortcut icon" type="image/x-icon" href="/images/favicon.ico">
+  <link rel="shortcut icon" type="image/x-icon" href="{{ site.baseurl }}/images/favicon.ico">
 </head>

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/_includes/header.html
----------------------------------------------------------------------
diff --git a/_includes/header.html b/_includes/header.html
index 97d9399..f70bcee 100644
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -1,7 +1,7 @@
 <nav class="navbar navbar-default navbar-fixed-top">
   <div class="container">
     <div class="navbar-header">
-      <a href="/" class="navbar-brand" >
+      <a href="{{ site.baseurl }}/" class="navbar-brand" >
         <img alt="Brand" style="height: 25px" src="{{ "/images/beam_logo_navbar.png" | prepend: site.baseurl }}">
       </a>
       <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/_posts/2016-08-03-six-months.md
----------------------------------------------------------------------
diff --git a/_posts/2016-08-03-six-months.md b/_posts/2016-08-03-six-months.md
index 1141eaf..73305e4 100644
--- a/_posts/2016-08-03-six-months.md
+++ b/_posts/2016-08-03-six-months.md
@@ -39,5 +39,5 @@ But perhaps most importantly, we’re committed to building an involved, welcomi
 * Had multiple talks on Beam at venues including ApacheCon, Hadoop Summit, Kafka Summit, JBCN Barcelona, and Strata.
 * Presented at multiple existing meetups and are starting to organize some of our own.
 
-While it’s nice to reflect back on all we’ve done, we’re working full _stream_ ahead towards a stable release and graduation from incubator. And we’d love your help -- join the [mailing lists](http://beam.incubator.apache.org/use/mailing-lists/), check out the [contribution guide](http://beam.incubator.apache.org/contribute/contribution-guide/), and grab a [starter task](https://issues.apache.org/jira/browse/BEAM-520?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20in%20(newbie%2C%20starter)) from Jira!
+While it’s nice to reflect back on all we’ve done, we’re working full _stream_ ahead towards a stable release and graduation from incubator. And we’d love your help -- join the [mailing lists]({{ site.baseurl }}/use/mailing-lists/), check out the [contribution guide]({{ site.baseurl }}/contribute/contribution-guide/), and grab a [starter task](https://issues.apache.org/jira/browse/BEAM-520?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20in%20(newbie%2C%20starter)) from Jira!
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/_posts/2016-10-12-strata-hadoop-world-and-beam.md
----------------------------------------------------------------------
diff --git a/_posts/2016-10-12-strata-hadoop-world-and-beam.md b/_posts/2016-10-12-strata-hadoop-world-and-beam.md
index acd48d7..f190762 100644
--- a/_posts/2016-10-12-strata-hadoop-world-and-beam.md
+++ b/_posts/2016-10-12-strata-hadoop-world-and-beam.md
@@ -28,5 +28,5 @@ On management and thought leader side, Beam went from “what’s Beam?” at pr
 
 We rounded out the tutorial with live demonstrations of Beam running on Apache Spark, Apache Flink, the local runner, and DataFlow runner. Then, we brought in the big brainpower and had a Q and A session.
 
-If you’re attending a conference, we encourage you to look for a Beam session. If you want to use these materials to give your own Beam talk or tutorial, we’re happy to help you. In addition to this tutorial, we have [other presentation materials](/learn/presentation-materials/). You can reach out to us on the [user mailing list](http://beam.incubator.apache.org/use/mailing-lists/).
+If you’re attending a conference, we encourage you to look for a Beam session. If you want to use these materials to give your own Beam talk or tutorial, we’re happy to help you. In addition to this tutorial, we have [other presentation materials]({{ site.baseurl }}/learn/presentation-materials/). You can reach out to us on the [user mailing list]({{ site.baseurl }}/use/mailing-lists/).
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/_posts/2016-10-20-test-stream.md
----------------------------------------------------------------------
diff --git a/_posts/2016-10-20-test-stream.md b/_posts/2016-10-20-test-stream.md
index 8b7eee7..e2e52de 100644
--- a/_posts/2016-10-20-test-stream.md
+++ b/_posts/2016-10-20-test-stream.md
@@ -47,7 +47,7 @@ from the Mobile Gaming example series.
 
 [LeaderBoard](https://github.com/apache/incubator-beam/blob/master/examples/java8/src/main/java/org/apache/beam/examples/complete/game/LeaderBoard.java#L177)
 is part of the [Beam mobile gaming examples](https://github.com/apache/incubator-beam/tree/master/examples/java8/src/main/java/org/apache/beam/examples/complete/game)
-(and [walkthroughs](http://beam.incubator.apache.org/use/walkthroughs/))
+(and [walkthroughs]({{ site.baseurl }}/get-started/mobile-gaming-example/))
 which produces a continuous accounting of user and team scores. User scores are
 calculated over the lifetime of the program, while team scores are calculated
 within fixed windows with a default duration of one hour. The LeaderBoard
@@ -60,7 +60,7 @@ be controlled within a test.
 ## Writing Deterministic Tests to Emulate Nondeterminism
 
 The Beam testing infrastructure provides the
-[PAssert](http://beam.incubator.apache.org/learn/sdks/javadoc/0.2.0-incubating/)
+[PAssert]({{ site.baseurl }}/documentation/sdks/javadoc/0.2.0-incubating/)
 methods, which assert properties about the contents of a PCollection from within
 a pipeline. We have expanded this infrastructure to include
 [TestStream](https://github.com/apache/incubator-beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/testing/TestStream.java),
@@ -306,4 +306,4 @@ The addition of TestStream alongside window and pane-specific matchers in PAsser
 has enabled the testing of Pipelines which produce speculative and late panes.
 This permits tests for all styles of pipeline to be expressed directly within the
 Java SDK. If you have questions or comments, we’d love to hear them on the
-[mailing lists](http://beam.incubator.apache.org/use/mailing-lists/).
+[mailing lists]({{ site.baseurl }}/use/mailing-lists/).

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/blog/index.md
----------------------------------------------------------------------
diff --git a/blog/index.md b/blog/index.md
index 0334a17..cda0cdd 100644
--- a/blog/index.md
+++ b/blog/index.md
@@ -26,7 +26,7 @@ for the project.
 {% endcapture %}
 {% if excerpt_words != content_words %}
 <p>
-<a class="btn btn-default btn-sm" href="{{ post.url }}" role="button">
+<a class="btn btn-default btn-sm" href="{{ post.url | prepend: site.baseurl }}" role="button">
 Read more&nbsp;<span class="glyphicon glyphicon-menu-right" aria-hidden="true"></span>
 </a>
 </p>

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/coming-soon.md
----------------------------------------------------------------------
diff --git a/coming-soon.md b/coming-soon.md
index 6054d3a..e77c753 100644
--- a/coming-soon.md
+++ b/coming-soon.md
@@ -6,4 +6,4 @@ layout: default
 
 You've reached a page that's still in draft, or otherwise being developed! Please bear with us as we improve the documentation for Apache Beam.
 
-[Go Back](/) to the main Beam site.
+[Go Back]({{ site.baseurl }}/) to the main Beam site.

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/contribute/contribution-guide.md
----------------------------------------------------------------------
diff --git a/contribute/contribution-guide.md b/contribute/contribution-guide.md
index a7c82b1..4635e91 100644
--- a/contribute/contribution-guide.md
+++ b/contribute/contribution-guide.md
@@ -18,7 +18,7 @@ We use a review-then-commit workflow in Beam for all contributions.
 
 **For larger contributions or those that affect multiple components:**
 
-1. **Engage**: We encourage you to work with the Beam community on the [Apache JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM) and [developer’s mailing list](http://beam.incubator.apache.org/use/mailing-lists/) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the Beam community on the [Apache JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM) and [developer’s mailing list]({{ site.baseurl }}/use/mailing-lists/) to identify good areas for contribution.
 1. **Design:** More complicated contributions will likely benefit from some early discussion in order to scope and design them well.
 
 **For all contributions:**
@@ -34,7 +34,7 @@ We look forward to working with you!
 ### Mailing list(s)
 We discuss design and implementation issues on dev@beam.incubator.apache.org mailing list, which is archived [here](https://lists.apache.org/list.html?dev@beam.apache.org). Join by emailing [`dev-subscribe@beam.incubator.apache.org`](mailto:dev-subscribe@beam.incubator.apache.org).
 
-If interested, you can also join the other [mailing lists](http://beam.incubator.apache.org/use/mailing-lists/) too.
+If interested, you can also join the other [mailing lists]({{ site.baseurl }}/use/mailing-lists/) too.
 
 ### Apache JIRA
 We use [Apache JIRA](https://issues.apache.org/jira/browse/BEAM) as an issue tracking and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all Beam-related work should be tracked there.
@@ -314,10 +314,10 @@ Some larger features are developed on a feature branch before being merged into
 
 #### Developing
 
-To contribute code on a feature branch, use the same process as above, but replace `master` with the [name of the branch](/contribute/work-in-progress/#feature-branches).
+To contribute code on a feature branch, use the same process as above, but replace `master` with the [name of the branch]({{ site.baseurl }}/contribute/work-in-progress/#feature-branches).
 
 Since feature branches are often used for new components, you may find that
-there is no [committer](/project/team/) familiar with all the details of the
+there is no [committer]({{ site.baseurl }}/project/team/) familiar with all the details of the
 new language or runner. In that case, consider asking someone else familiar
 with the technology to do an initial review before looping in a committer for a
 final review and merge.

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/contribute/index.md
----------------------------------------------------------------------
diff --git a/contribute/index.md b/contribute/index.md
index 6d8f99c..9bfda4a 100644
--- a/contribute/index.md
+++ b/contribute/index.md
@@ -20,4 +20,4 @@ Resources for contributing to Beam, including mailing lists, the main GitHub rep
 
 * [Mailing Lists]({{ site.baseurl }}/use/mailing-lists/)
 * [Source Repository]({{ site.baseurl }}/contribute/source-repository)
-* [Issue Tracking]({{ site.baseurl }}/use/issue-tracking/)
\ No newline at end of file
+* [Issue Tracking]({{ site.baseurl }}/use/issue-tracking/)

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/contribute/logos.md
----------------------------------------------------------------------
diff --git a/contribute/logos.md b/contribute/logos.md
index fa42c57..0aeccdd 100644
--- a/contribute/logos.md
+++ b/contribute/logos.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Beam Logos"
 permalink: /contribute/logos/
-redirect-from: /project/logos/
-redirect_from: /material/
+redirect_from:
+  - /project/logos/
+  - /material/
 ---
 
 # Apache Beam Logos
@@ -47,11 +48,11 @@ available in a number of fixed sizes and are optimized for web use.
 {% for type in site.data.logos.types %}
 <div class="col-md-2">
 <div class="row">
-<img style="height: 60px" src="{{ site.data.logos.logo-location }}/{{ color[0] }}/{{ type }}/beam-logo-{{ color[0] }}-{{ type }}.svg" alt="beam-logo-{{ color[0] }}-{{ type }}">
+<img style="height: 60px" src="{{ site.baseurl }}{{ site.data.logos.logo-location }}/{{ color[0] }}/{{ type }}/beam-logo-{{ color[0] }}-{{ type }}.svg" alt="beam-logo-{{ color[0] }}-{{ type }}">
 </div><br>
 <div class="row">
 {% for size in site.data.logos.sizes %}
-<a href="{{ site.data.logos.logo-location }}/{{ color[0] }}/{{ type }}/beam-logo-{{ color[0] }}-{{ type }}-{{ size }}.png">{{ size }}x{{ size }}</a>
+<a href="{{ site.baseurl }}{{ site.data.logos.logo-location }}/{{ color[0] }}/{{ type }}/beam-logo-{{ color[0] }}-{{ type }}-{{ size }}.png">{{ size }}x{{ size }}</a>
 {% unless forloop.last %},{% endunless %}
 {% endfor %}
 </div>

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/contribute/release-guide.md
----------------------------------------------------------------------
diff --git a/contribute/release-guide.md b/contribute/release-guide.md
index fd98ca3..b0d4dca 100644
--- a/contribute/release-guide.md
+++ b/contribute/release-guide.md
@@ -15,7 +15,7 @@ The Apache Beam project periodically declares and publishes releases. A release
 
 The Beam community treats releases with great importance. They are a public face of the project and most users interact with the project only through the releases. Releases are signed off by the entire Beam community in a public vote.
 
-Each release is executed by a *Release Manager*, who is selected among the [Beam committers](/project/team). This document describes the process that the Release Manager follows to perform a release. Any changes to this process should be discussed and adopted on the [dev@ mailing list](/use/mailing-lists).
+Each release is executed by a *Release Manager*, who is selected among the [Beam committers]({{ site.baseurl }}/project/team). This document describes the process that the Release Manager follows to perform a release. Any changes to this process should be discussed and adopted on the [dev@ mailing list]({{ site.baseurl }}/use/mailing-lists).
 
 Please remember that publishing software has legal consequences. This guide complements the foundation-wide [Product Release Policy](http://www.apache.org/dev/release.html) and [Release Distribution Policy](http://www.apache.org/dev/release-distribution).
 
@@ -110,7 +110,7 @@ Configure access to the [Apache Nexus repository](http://repository.apache.org/)
 
 #### Website development setup
 
-Get ready for updating the Beam website by following the [website development instructions](/contribute/contribution-guide/#website).
+Get ready for updating the Beam website by following the [website development instructions]({{ site.baseurl }}/contribute/contribution-guide/#website).
 
 ### Create a new version in JIRA
 
@@ -273,12 +273,12 @@ Please carefully review the generated Javadoc. Check for completeness and presen
 
 The final step of building the candidate is to propose a website pull request.
 
-Add the new release to the [Apache Beam Releases](/use/releases/) page, as follows:
+Add the new release to the [Apache Beam Releases]({{ site.baseurl }}/use/releases/) page, as follows:
 
 * Update the `<version>` tags in the sample `pom.xml` snippet to the new release.
 * Add the new version to the `Release Notes` section below, along with links to the source code download and the Release Notes in JIRA.
 
-Add the new Javadoc to [SDK API Reference page](/learn/sdks/javadoc/) page, as follows:
+Add the new Javadoc to [SDK API Reference page]({{ site.baseurl }}/learn/sdks/javadoc/) page, as follows:
 
 * Copy the generated Javadoc into the website repository: `cp -r ${JAVADOC_ROOT} learn/sdks/javadoc/${VERSION}`.
 * Update the Javadoc link on this page to point to the new version.
@@ -289,7 +289,7 @@ Finally, propose a pull request with these changes. (Don’t merge before finali
 
 1. Maven artifacts deployed to the staging repository of [repository.apache.org](https://repository.apache.org/content/repositories/)
 1. Source distribution deployed to the dev repository of [dist.apache.org](https://dist.apache.org/repos/dist/dev/incubator/beam/)
-1. Website pull request proposed to list the [release](/use/releases/) and publish the [API reference manual](/learn/sdks/javadoc/)
+1. Website pull request proposed to list the [release]({{ site.baseurl }}/use/releases/) and publish the [API reference manual]({{ site.baseurl }}/learn/sdks/javadoc/)
 
 **********
 
@@ -442,7 +442,7 @@ Create a new Git tag for the released version by copying the tag for the final r
 
 ### Merge website pull request
 
-Merge the website pull request to [list the release](/use/releases/) and publish the [API reference manual](/learn/sdks/javadoc/) created earlier.
+Merge the website pull request to [list the release]({{ site.baseurl }}/use/releases/) and publish the [API reference manual]({{ site.baseurl }}/learn/sdks/javadoc/) created earlier.
 
 ### Mark the version as released in JIRA
 
@@ -452,7 +452,7 @@ In JIRA, inside [version management](https://issues.apache.org/jira/plugins/serv
 
 * Maven artifacts released and indexed in the [Maven Central Repository](https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22)
 * Source distribution available in the release repository of [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/beam/)
-* Website pull request to [list the release](/use/releases/) and publish the [API reference manual](/learn/sdks/javadoc/) merged
+* Website pull request to [list the release]({{ site.baseurl }}/use/releases/) and publish the [API reference manual]({{ site.baseurl }}/learn/sdks/javadoc/) merged
 * Release tagged in the source code repository
 * Release version finalized in JIRA
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/contribute/team.md
----------------------------------------------------------------------
diff --git a/contribute/team.md b/contribute/team.md
index 835cd75..311a30a 100644
--- a/contribute/team.md
+++ b/contribute/team.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Beam Team"
 permalink: /contribute/team/
-redirect_from: /project/team/
-redirect_from: /team/
+redirect_from:
+  - /project/team/
+  - /team/
 ---
 
 # Apache Beam Team

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/contribute/work-in-progress.md
----------------------------------------------------------------------
diff --git a/contribute/work-in-progress.md b/contribute/work-in-progress.md
index d1b6361..2017d57 100644
--- a/contribute/work-in-progress.md
+++ b/contribute/work-in-progress.md
@@ -6,7 +6,7 @@ permalink: /contribute/work-in-progress/
 
 # Work In Progress in the Apache Beam Project
 
-As mentioned in the [Contribution Guide](/contribute/contribution-guide/), all work in Beam is tracked in our [Apache JIRA](https://issues.apache.org/jira/browse/BEAM). In addition, the following types of work may be of particular interest to the Beam community.
+As mentioned in the [Contribution Guide]({{ site.baseurl }}/contribute/contribution-guide/), all work in Beam is tracked in our [Apache JIRA](https://issues.apache.org/jira/browse/BEAM). In addition, the following types of work may be of particular interest to the Beam community.
 
 * TOC
 {:toc}
@@ -14,11 +14,11 @@ As mentioned in the [Contribution Guide](/contribute/contribution-guide/), all w
 
 ## Starter Tasks
 
-The community regular tags good getting started tasks with the label `starter`. Use a quick [JIRA search](https://issues.apache.org/jira/issues?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20starter) to identify ways you can get started [contributing](/contribute/contribution-guide/) to Beam.
+The community regular tags good getting started tasks with the label `starter`. Use a quick [JIRA search](https://issues.apache.org/jira/issues?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20starter) to identify ways you can get started [contributing]({{ site.baseurl }}/contribute/contribution-guide/) to Beam.
 
 ## Feature Branches
 
-Larger features with multiple active developers may be developed on a [feature branch](/contribute/contribution-guide/#feature-branches) before being merged in the master branch. In particular, this is often used for initial development of new components like SDKs or runners.
+Larger features with multiple active developers may be developed on a [feature branch]({{ site.baseurl }}/contribute/contribution-guide/#feature-branches) before being merged in the master branch. In particular, this is often used for initial development of new components like SDKs or runners.
 
 Current branches include:
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/index.md
----------------------------------------------------------------------
diff --git a/documentation/index.md b/documentation/index.md
index fc5ef42..6bd6be8 100644
--- a/documentation/index.md
+++ b/documentation/index.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Learn about Beam"
 permalink: /documentation/
-redirect-from: /learn/
-redirect_from: /docs/learn/
+redirect_from:
+  - /learn/
+  - /docs/learn/
 ---
 
 # Learn about the Apache Beam Model
@@ -26,4 +27,4 @@ Learn about the [Capability Matrix]({{ site.baseurl }}/learn/runners/capability-
 * [Apache Spark]({{ site.baseurl }}/learn/runners/spark/)
 * [Cloud Dataflow]({{ site.baseurl }}/learn/runners/dataflow/)
 
-#### [Additional Resources]({{ site.baseurl }}/learn/resources/)
\ No newline at end of file
+#### [Additional Resources]({{ site.baseurl }}/learn/resources/)

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/pipelines/create-your-pipeline.md
----------------------------------------------------------------------
diff --git a/documentation/pipelines/create-your-pipeline.md b/documentation/pipelines/create-your-pipeline.md
index e2c9ed0..b99628f 100644
--- a/documentation/pipelines/create-your-pipeline.md
+++ b/documentation/pipelines/create-your-pipeline.md
@@ -5,4 +5,4 @@ permalink: /documentation/pipelines/create-your-pipeline/
 ---
 # Create Your Pipeline
 
-> **Note:** There is an open JIRA issue to create this guide ([BEAM-901](https://issues.apache.org/jira/browse/BEAM-901)).
\ No newline at end of file
+> **Note:** There is an open JIRA issue to create this guide ([BEAM-901](https://issues.apache.org/jira/browse/BEAM-901)).

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/pipelines/design-your-pipeline.md
----------------------------------------------------------------------
diff --git a/documentation/pipelines/design-your-pipeline.md b/documentation/pipelines/design-your-pipeline.md
index fca6912..8a76704 100644
--- a/documentation/pipelines/design-your-pipeline.md
+++ b/documentation/pipelines/design-your-pipeline.md
@@ -5,4 +5,4 @@ permalink: /documentation/pipelines/design-your-pipeline/
 ---
 # Design Your Pipeline
 
-> **Note:** There is an open JIRA issue to create this guide ([BEAM-901](https://issues.apache.org/jira/browse/BEAM-901)).
\ No newline at end of file
+> **Note:** There is an open JIRA issue to create this guide ([BEAM-901](https://issues.apache.org/jira/browse/BEAM-901)).

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/pipelines/test-your-pipeline.md
----------------------------------------------------------------------
diff --git a/documentation/pipelines/test-your-pipeline.md b/documentation/pipelines/test-your-pipeline.md
index 82044c2..0a75bb5 100644
--- a/documentation/pipelines/test-your-pipeline.md
+++ b/documentation/pipelines/test-your-pipeline.md
@@ -5,4 +5,4 @@ permalink: /documentation/pipelines/test-your-pipeline/
 ---
 # Test Your Pipeline
 
-> **Note:** There is an open JIRA issue to create this guide ([BEAM-901](https://issues.apache.org/jira/browse/BEAM-901)).
\ No newline at end of file
+> **Note:** There is an open JIRA issue to create this guide ([BEAM-901](https://issues.apache.org/jira/browse/BEAM-901)).

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/programming-guide.md
----------------------------------------------------------------------
diff --git a/documentation/programming-guide.md b/documentation/programming-guide.md
index 1094644..648962a 100644
--- a/documentation/programming-guide.md
+++ b/documentation/programming-guide.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Beam Programming Guide"
 permalink: /documentation/programming-guide/
-redirect-from: /learn/programming-guide/
-redirect_from: /docs/learn/programming-guide/
+redirect_from:
+  - /learn/programming-guide/
+  - /docs/learn/programming-guide/
 ---
 
 # Apache Beam Programming Guide

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/resources.md
----------------------------------------------------------------------
diff --git a/documentation/resources.md b/documentation/resources.md
index cd7c6a7..5accec0 100644
--- a/documentation/resources.md
+++ b/documentation/resources.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Beam Learning Resources"
 permalink: /documentation/resources/
-redirect-from: /learn/resources/
+redirect_from: /learn/resources/
 ---
 # Additional Resources for Learning about Apache Beam
 
@@ -13,4 +13,4 @@ Here's some links to some of our favorite articles and videos get you started.
 * [The world beyond batch: Streaming 101](https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-101)
 * [The world beyong batch: Streaming 102](https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-102)
 * [Dataflow/Beam & Spark: A Programming Model Comparison](https://cloud.google.com/dataflow/blog/dataflow-beam-and-spark-comparison)
-* [Dataflow and open source - proposal to join the Apache Incubator](http://googlecloudplatform.blogspot.com/2016/01/Dataflow-and-open-source-proposal-to-join-the-Apache-Incubator.html)
\ No newline at end of file
+* [Dataflow and open source - proposal to join the Apache Incubator](http://googlecloudplatform.blogspot.com/2016/01/Dataflow-and-open-source-proposal-to-join-the-Apache-Incubator.html)

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/runners/capability-materix.md
----------------------------------------------------------------------
diff --git a/documentation/runners/capability-materix.md b/documentation/runners/capability-materix.md
index 89ce555..d7af766 100644
--- a/documentation/runners/capability-materix.md
+++ b/documentation/runners/capability-materix.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Apache Beam Capability Matrix"
 permalink: /documentation/runners/capability-matrix/
-redirect-from: /learn/runners/capability-matrix/
-redirect-from: /capability-matrix/
+redirect_from:
+  - /learn/runners/capability-matrix/
+  - /capability-matrix/
 ---
 
 # Beam Capability Matrix

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/runners/dataflow.md
----------------------------------------------------------------------
diff --git a/documentation/runners/dataflow.md b/documentation/runners/dataflow.md
index 375d289..c49223b 100644
--- a/documentation/runners/dataflow.md
+++ b/documentation/runners/dataflow.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Cloud Dataflow Runner"
 permalink: /documentation/runners/dataflow/
-redirect-from: /learn/runners/dataflow/
+redirect_from: /learn/runners/dataflow/
 ---
 # Using the Cloud Dataflow Runner
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/runners/direct.md
----------------------------------------------------------------------
diff --git a/documentation/runners/direct.md b/documentation/runners/direct.md
index ef31f04..094d44e 100644
--- a/documentation/runners/direct.md
+++ b/documentation/runners/direct.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Apache Direct Runner"
 permalink: /documentation/runners/direct/
-redirect-from: /learn/runners/direct/
+redirect_from: /learn/runners/direct/
 ---
 # Using the Direct Runner
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/runners/flink.md
----------------------------------------------------------------------
diff --git a/documentation/runners/flink.md b/documentation/runners/flink.md
index 8554b98..4145be6 100644
--- a/documentation/runners/flink.md
+++ b/documentation/runners/flink.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Apache Flink Runner"
 permalink: /documentation/runners/flink/
-redirect-from: /learn/runners/flink/
+redirect_from: /learn/runners/flink/
 ---
 # Using the Apache Flink Runner
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/runners/index.md
----------------------------------------------------------------------
diff --git a/documentation/runners/index.md b/documentation/runners/index.md
index d36a6ab..d6d2211 100644
--- a/documentation/runners/index.md
+++ b/documentation/runners/index.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Beam Runners"
 permalink: /documentation/runners/
-redirect-from: /learn/runners/
+redirect_from: /learn/runners/
 ---
 # Apache Beam Runners
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/runners/spark.md
----------------------------------------------------------------------
diff --git a/documentation/runners/spark.md b/documentation/runners/spark.md
index 2650f8f..66d01db 100644
--- a/documentation/runners/spark.md
+++ b/documentation/runners/spark.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Apache Spark Runner"
 permalink: /documentation/runners/spark/
-redirect-from: /learn/runners/spark/
+redirect_from: /learn/runners/spark/
 ---
 # Using the Apache Spark Runner
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/sdks/index.md
----------------------------------------------------------------------
diff --git a/documentation/sdks/index.md b/documentation/sdks/index.md
index 0cabb5a..1a5a08e 100644
--- a/documentation/sdks/index.md
+++ b/documentation/sdks/index.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Beam SDKs"
 permalink: /documentation/sdks/
-redirect-from: /learn/sdks/
+redirect_from: /learn/sdks/
 ---
 # Apache Beam SDKs
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/sdks/java.md
----------------------------------------------------------------------
diff --git a/documentation/sdks/java.md b/documentation/sdks/java.md
index 5968d59..91ba7b8 100644
--- a/documentation/sdks/java.md
+++ b/documentation/sdks/java.md
@@ -2,12 +2,12 @@
 layout: default
 title: "Beam Java SDK"
 permalink: /documentation/sdks/java/
-redirect-from: /learn/sdks/java/
+redirect_from: /learn/sdks/java/
 ---
 # Apache Beam Java SDK
 
 This page is under construction ([BEAM-504](https://issues.apache.org/jira/browse/BEAM-504)).
 
-Get started with the [Beam Programming Guide](/learn/programming-guide) to learn the basic concepts that hold for all SDKs in the Beam Model.
+Get started with the [Beam Programming Guide]({{ site.baseurl }}/learn/programming-guide) to learn the basic concepts that hold for all SDKs in the Beam Model.
 
-See the [Java API Reference](/learn/sdks/javadoc/).
+See the [Java API Reference]({{ site.baseurl }}/learn/sdks/javadoc/).

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/documentation/sdks/javadoc/index.md
----------------------------------------------------------------------
diff --git a/documentation/sdks/javadoc/index.md b/documentation/sdks/javadoc/index.md
index 17872c0..cfaa022 100644
--- a/documentation/sdks/javadoc/index.md
+++ b/documentation/sdks/javadoc/index.md
@@ -2,7 +2,7 @@
 layout: default
 title: "Beam Javadoc"
 permalink: /documentation/sdks/javadoc/
-redirect-from: /learn/sdks/javadoc/
+redirect_from: /learn/sdks/javadoc/
 ---
 # Apache Beam Java SDK API Reference
 

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/beam-overview.md
----------------------------------------------------------------------
diff --git a/get-started/beam-overview.md b/get-started/beam-overview.md
index 7ca9709..1b43ca8 100644
--- a/get-started/beam-overview.md
+++ b/get-started/beam-overview.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Beam Overview"
 permalink: /get-started/beam-overview/
-redirect_from: /use/beam-overview/
-redirect_from: /docs/use/beam-overview/
+redirect_from:
+  - /use/beam-overview/
+  - /docs/use/beam-overview/
 ---
 # Apache Beam Overview
 
@@ -61,4 +62,4 @@ Beam currently supports Runners that work with the following distributed process
 </tr>
 </table>
 
-**Note:** You can always execute your pipeline locally for testing and debugging purposes.
\ No newline at end of file
+**Note:** You can always execute your pipeline locally for testing and debugging purposes.

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/downloads.md
----------------------------------------------------------------------
diff --git a/get-started/downloads.md b/get-started/downloads.md
index 3f1927b..95bbffc 100644
--- a/get-started/downloads.md
+++ b/get-started/downloads.md
@@ -6,4 +6,4 @@ permalink: /get-started/downloads/
 
 # Downloads
 
-> **Note:** There is an open JIRA issue to fill in this page ([BEAM-906](https://issues.apache.org/jira/browse/BEAM-906)).
\ No newline at end of file
+> **Note:** There is an open JIRA issue to fill in this page ([BEAM-906](https://issues.apache.org/jira/browse/BEAM-906)).

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/index.md
----------------------------------------------------------------------
diff --git a/get-started/index.md b/get-started/index.md
index 72d68b4..4ab55af 100644
--- a/get-started/index.md
+++ b/get-started/index.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Use Beam"
 permalink: /get-started/
-redirect_from: /use/
-redirect_from: /docs/use/
+redirect_from:
+  - /use/
+  - /docs/use/
 ---
 
 # Using Apache Beam
@@ -22,7 +23,7 @@ Find information on the latest Beam releases, including versioning and release n
 See detailed walkthroughs of complete Beam pipelines.
 
 * [WordCount]({{ site.baseurl }}/use/wordcount-example): Simple example pipelines that demonstrate basic Beam programming, including debugging and testing
-* [Mobile Gaming]({{ site.baseurl }}/use/walkthroughs): A series of more advanced pipelines that demonstrate use cases in the mobile gaming domain
+* [Mobile Gaming]({{ site.baseurl }}/use/mobile-gaming-example): A series of more advanced pipelines that demonstrate use cases in the mobile gaming domain
 
 #### Support
 Find resources to help you use Beam.
@@ -30,4 +31,4 @@ Find resources to help you use Beam.
 * [Mailing Lists]({{ site.baseurl }}/use/mailing-lists/)
 * [Issue Tracking]({{ site.baseurl }}/use/issue-tracking/)
 * [Beam on Stack Overflow](http://stackoverflow.com/questions/tagged/apache-beam)
-* [Slack Channel](http://apachebeam.slack.com)
\ No newline at end of file
+* [Slack Channel](http://apachebeam.slack.com)

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/mobile-gaming-example.md
----------------------------------------------------------------------
diff --git a/get-started/mobile-gaming-example.md b/get-started/mobile-gaming-example.md
index 1a5b2ca..b51f81a 100644
--- a/get-started/mobile-gaming-example.md
+++ b/get-started/mobile-gaming-example.md
@@ -10,7 +10,7 @@ redirect_from: /use/mobile-gaming-example/
 * TOC
 {:toc}
 
-This section provides a walkthrough of a series of example Apache Beam pipelines that demonstrate more complex functionality than the basic [WordCount](/use/wordcount-example) examples. The pipelines in this section process data from a hypothetical game that users play on their mobile phones. The pipelines demonstrate processing at increasing levels of complexity; the first pipeline, for example, shows how to run a batch analysis job to obtain relatively simple score data, while the later pipelines use Beam's windowing and triggers features to provide low-latency data analysis and more complex intelligence about user's play patterns.
+This section provides a walkthrough of a series of example Apache Beam pipelines that demonstrate more complex functionality than the basic [WordCount]({{ site.baseurl }}/use/wordcount-example) examples. The pipelines in this section process data from a hypothetical game that users play on their mobile phones. The pipelines demonstrate processing at increasing levels of complexity; the first pipeline, for example, shows how to run a batch analysis job to obtain relatively simple score data, while the later pipelines use Beam's windowing and triggers features to provide low-latency data analysis and more complex intelligence about user's play patterns.
 
 > **Note**: These examples assume some familiarity with the Beam programming model. If you haven't already, we recommend familiarizing yourself with the programming model documentation and running a basic example pipeline before continuing. Note also that these examples use the Java 8 lambda syntax, and thus require Java 8. However, you can create pipelines with equivalent functionality using Java 7.
 
@@ -27,7 +27,7 @@ This means that some data events might be received by the game server significan
 
 Because some of our example pipelines use data files (like logs from the game server) as input, the event timestamp for each game might be embedded in the data--that is, it's a field in each data record. Those pipelines need to parse the event timestamp from each data record after reading it from the input file.
 
-For pipelines that read unbounded game data from an unbounded source, the data source sets the intrinsic [timestamp](/learn/programming-guide/#pctimestamps) for each PCollection element to the appropriate event time.
+For pipelines that read unbounded game data from an unbounded source, the data source sets the intrinsic [timestamp]({{ site.baseurl }}/documentation/programming-guide/#pctimestamps) for each PCollection element to the appropriate event time.
 
 The Mobile Game example pipelines vary in complexity, from simple batch analysis to more complex pipelines that can perform real-time analysis and abuse detection. This section walks you through each example and demonstrates how to use Beam features like windowing and triggers to expand your pipeline's capabilites.
 
@@ -56,7 +56,7 @@ As the pipeline processes each event, the event score gets added to the sum tota
 The following diagram shows score data for a several users over the pipeline analysis period. In the diagram, each data point is an event that results in one user/score pair:
 
 <figure id="fig1">
-    <img src="/images/gaming-example.gif"
+    <img src="{{ site.baseurl }}/images/gaming-example.gif"
          width="900" height="263"
          alt="Score data for three users.">
 </figure>
@@ -64,7 +64,7 @@ Figure 1: Score data for three users.
 
 This example uses batch processing, and the diagram's Y axis represents processing time: the pipeline processes events lower on the Y-axis first, and events higher up the axis later. The diagram's X axis represents the event time for each game event, as denoted by that event's timestamp. Note that the individual events in the diagram are not processed by the pipeline in the same order as they occurred (according to their timestamps).
 
-After reading the score events from the input file, the pipeline groups all of those user/score pairs together and sums the score values into one total value per unique user. `UserScore` encapsulates the core logic for that step as the [user-defined composite transform](/learn/programming-guide/#transforms-composite) `ExtractAndSumScore`:
+After reading the score events from the input file, the pipeline groups all of those user/score pairs together and sums the score values into one total value per unique user. `UserScore` encapsulates the core logic for that step as the [user-defined composite transform]({{ site.baseurl }}/documentation/programming-guide/#transforms-composite) `ExtractAndSumScore`:
 
 ```java
 public static class ExtractAndSumScore
@@ -163,7 +163,7 @@ Using fixed-time windowing lets the pipeline provide better information on how e
 The following diagram shows how the pipeline processes a day's worth of a single team's scoring data after applying fixed-time windowing:
 
 <figure id="fig2">
-    <img src="/images/gaming-example-team-scores-narrow.gif"
+    <img src="{{ site.baseurl }}/images/gaming-example-team-scores-narrow.gif"
          width="900" height="390"
          alt="Score data for two teams.">
 </figure>
@@ -173,7 +173,7 @@ Notice that as processing time advances, the sums are now _per window_; each win
 
 > **Note:** As is shown in the diagram above, using windowing produces an _independent total for every interval_ (in this case, each hour). `HourlyTeamScore` doesn't provide a running total for the entire data set at each hour--it provides the total score for all the events that occurred _only within that hour_.
 
-Beam's windowing feature uses the [intrinsic timestamp information](/learn/programming-guide/#pctimestamps) attached to each element of a `PCollection`. Because we want our pipeline to window based on _event time_, we **must first extract the timestamp** that's embedded in each data record apply it to the corresponding element in the `PCollection` of score data. Then, the pipeline can **apply the windowing function** to divide the `PCollection` into logical windows.
+Beam's windowing feature uses the [intrinsic timestamp information]({{ site.baseurl }}/documentation/programming-guide/#pctimestamps) attached to each element of a `PCollection`. Because we want our pipeline to window based on _event time_, we **must first extract the timestamp** that's embedded in each data record apply it to the corresponding element in the `PCollection` of score data. Then, the pipeline can **apply the windowing function** to divide the `PCollection` into logical windows.
 
 Here's the code, which shows how `HourlyTeamScore` uses the [WithTimestamps](https://github.com/apache/incubator-beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/WithTimestamps.java) and [Window](https://github.com/apache/incubator-beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/windowing/Window.java) transforms to perform these operations:
 
@@ -290,12 +290,12 @@ Below, we'll look at both of these tasks in detail.
 
 We want our pipeline to output a running total score for each user for every ten minutes that the pipeline runs. This calculation doesn't consider _when_ the actual score was generated by the user's play instance; it simply outputs the sum of all the scores for that user that have arrived in the pipeline to date. Late data gets included in the calculation whenever it happens to arrive in the pipeline as it's running.
 
-Because we want all the data that has arrived in the pipeline every time we update our calculation, we have the pipeline consider all of the user score data in a **single global window**. The single global window is unbounded, but we can specify a kind of temporary cut-off point for each ten-minute calculation by using a processing time [trigger](/learn/programming-guide/#triggers).
+Because we want all the data that has arrived in the pipeline every time we update our calculation, we have the pipeline consider all of the user score data in a **single global window**. The single global window is unbounded, but we can specify a kind of temporary cut-off point for each ten-minute calculation by using a processing time [trigger]({{ site.baseurl }}/documentation/programming-guide/#triggers).
 
 When we specify a ten-minute processing time trigger for the single global window, the effect is that the pipeline effectively takes a "snapshot" of the contents of the window every time the trigger fires (which it does at ten-minute intervals). Since we're using a single global window, each snapshot contains all the data collected _to that point in time_. The following diagram shows the effects of using a processing time trigger on the single global window:
 
 <figure id="fig3">
-    <img src="/images/gaming-example-proc-time-narrow.gif"
+    <img src="{{ site.baseurl }}/images/gaming-example-proc-time-narrow.gif"
          width="900" height="263"
          alt="Score data for for three users.">
 </figure>
@@ -342,14 +342,14 @@ We want our pipeline to also output the total score for each team during each ho
 
 Because we consider each hour individually, we can apply fixed-time windowing to our input data, just like in `HourlyTeamScore`. To provide the speculative updates and updates on late data, we'll specify additional trigger parameters. The trigger will cause each window to calculate and emit results at an interval we specify (in this case, every five minutes), and also to keep triggering after the window is considered "complete" to account for late data. Just like the user score calculation, we'll set the trigger to accumulating mode to ensure that we get a running sum for each hour-long window.
 
-The triggers for speculative updates and late data help with the problem of [time skew](/learn/programming-guide/#windowing). Events in the pipeline aren't necessarily processed in the order in which they actually occurred according to their timestamps; they may arrive in the pipeline out of order, or late (in our case, because they were generated while the user's phone was out of contact with a network). Beam needs a way to determine when it can reasonably assume that it has "all" of the data in a given window: this is called the _watermark_.
+The triggers for speculative updates and late data help with the problem of [time skew]({{ site.baseurl }}/documentation/programming-guide/#windowing). Events in the pipeline aren't necessarily processed in the order in which they actually occurred according to their timestamps; they may arrive in the pipeline out of order, or late (in our case, because they were generated while the user's phone was out of contact with a network). Beam needs a way to determine when it can reasonably assume that it has "all" of the data in a given window: this is called the _watermark_.
 
 In an ideal world, all data would be processed immediately when it occurs, so the processing time would be equal to (or at least have a linear relationship to) the event time. However, because distributed systems contain some inherent inaccuracy (like our late-reporting phones), Beam often uses a heuristic watermark.
 
 The following diagram shows the relationship between ongoing processing time and each score's event time for two teams:
 
 <figure id="fig4">
-    <img src="/images/gaming-example-event-time-narrow.gif"
+    <img src="{{ site.baseurl }}/images/gaming-example-event-time-narrow.gif"
          width="900" height="390"
          alt="Score data by team, windowed by event time.">
 </figure>
@@ -417,7 +417,7 @@ Let's suppose scoring in our game depends on the speed at which a user can "clic
 
 To determine whether or not a score is "abnormally" high, `GameStats` calculates the average of every score in that fixed-time window, and then checks each score individual score against the average score multiplied by an arbitrary weight factor (in our case, 2.5). Thus, any score more than 2.5 times the average is deemed to be the product of spam. The `GameStats` pipeline tracks a list of "spam" users and filters those users out of the team score calculations for the team leader board.
 
-Since the average depends on the pipeline data, we need to calculate it, and then use that calculated data in a subsequent `ParDo` transform that filters scores that exceed the weighted value. To do this, we can pass the calculated average to as a [side input](/learn/programming-guide/#transforms-sideio) to the filtering `ParDo`.
+Since the average depends on the pipeline data, we need to calculate it, and then use that calculated data in a subsequent `ParDo` transform that filters scores that exceed the weighted value. To do this, we can pass the calculated average to as a [side input]({{ site.baseurl }}/documentation/programming-guide/#transforms-sideio) to the filtering `ParDo`.
 
 The following code example shows the composite transform that handles abuse detection. The transform uses the `Sum.integersPerKey` transform to sum all scores per user, and then the `Mean.globally` transform to determine the average score for all users. Once that's been calculated (as a `PCollectionView` singleton), we can pass it to the filtering `ParDo` using `.withSideInputs`:
 
@@ -498,7 +498,7 @@ When you set session windowing, you specify a _minimum gap duration_ between eve
 The following diagram shows how data might look when grouped into session windows. Unlike fixed windows, session windows are _different for each user_ and is dependent on each individual user's play pattern:
 
 <figure id="fig5">
-    <img src="/images/gaming-example-session-windows.png"
+    <img src="{{ site.baseurl }}/images/gaming-example-session-windows.png"
          width="662" height="521"
          alt="A diagram representing session windowing."
          alt="User sessions, with a minimum gap duration.">

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/quickstart.md
----------------------------------------------------------------------
diff --git a/get-started/quickstart.md b/get-started/quickstart.md
index a1fee07..f0cd5c3 100644
--- a/get-started/quickstart.md
+++ b/get-started/quickstart.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Beam Quickstart"
 permalink: /get-started/quickstart/
-redirect_from: /use/quickstart/
-redirect_from: /getting-started/
+redirect_from:
+  - /use/quickstart/
+  - /getting-started/
 ---
 
 # Apache Beam Quickstart

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/releases.md
----------------------------------------------------------------------
diff --git a/get-started/releases.md b/get-started/releases.md
index a04a666..4241b0d 100644
--- a/get-started/releases.md
+++ b/get-started/releases.md
@@ -2,8 +2,9 @@
 layout: default
 title: "Beam Releases"
 permalink: get-started/releases/
-redirect_from: /use/releases/
-redirect_from: /releases/
+redirect_from:
+  - /use/releases/
+  - /releases/
 ---
 
 # Apache Beam Releases

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/support.md
----------------------------------------------------------------------
diff --git a/get-started/support.md b/get-started/support.md
index ea5e41d..cfb5212 100644
--- a/get-started/support.md
+++ b/get-started/support.md
@@ -2,6 +2,9 @@
 layout: default
 title: "Support"
 permalink: /get-started/support/
+redirect_from:
+  - /use/issue-tracking/
+  - /use/mailing-lists/
 ---
 
 # Support

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/get-started/wordcount-example.md
----------------------------------------------------------------------
diff --git a/get-started/wordcount-example.md b/get-started/wordcount-example.md
index 851bdbf..4df1cd1 100644
--- a/get-started/wordcount-example.md
+++ b/get-started/wordcount-example.md
@@ -85,7 +85,7 @@ The Minimal WordCount pipeline contains five transforms:
 	        p.apply(TextIO.Read.from("gs://apache-beam-samples/shakespeare/*"))
 	```
 
-2.  A [ParDo](/learn/programming-guide/#transforms-pardo) transform that invokes a `DoFn` (defined in-line as an anonymous class) on each element that tokenizes the text lines into individual words. The input for this transform is the `PCollection` of text lines generated by the previous `TextIO.Read` transform. The `ParDo` transform outputs a new `PCollection`, where each element represents an individual word in the text.
+2.  A [ParDo]({{ site.baseurl }}/documentation/programming-guide/#transforms-pardo) transform that invokes a `DoFn` (defined in-line as an anonymous class) on each element that tokenizes the text lines into individual words. The input for this transform is the `PCollection` of text lines generated by the previous `TextIO.Read` transform. The `ParDo` transform outputs a new `PCollection`, where each element represents an individual word in the text.
 
 	```java
 	        .apply("ExtractWords", ParDo.of(new DoFn<String, String>() {

http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/a7c71d23/index.md
----------------------------------------------------------------------
diff --git a/index.md b/index.md
index 5a736b4..31a8a09 100644
--- a/index.md
+++ b/index.md
@@ -4,7 +4,7 @@ layout: default
 <div class="alert alert-info alert-dismissible" role="alert">
 <span class="glyphicon glyphicon-flag" aria-hidden="true"></span>
 <button type="button" class="close" data-dismiss="alert" aria-label="Close"><span aria-hidden="true">&times;</span></button>
-The Apache Beam project is in the process of bootstrapping. This includes the website -- so please file issues you find in <a href="/use/issue-tracking/">Jira</a>. Thanks!
+The Apache Beam project is in the process of bootstrapping. This includes the website -- so please file issues you find in <a href="{{ site.baseurl }}/use/issue-tracking/">Jira</a>. Thanks!
 </div>
 
 # Apache Beam (incubating)
@@ -69,8 +69,8 @@ Beam currently supports Runners that work with the following distributed process
 
 Interested in working with Apache Beam? Great! Here's how to get started:
 
-* If you are interested in using Beam for your data processing tasks, use the [Get Started](/get-started/) section for an overview, quickstart, and examples. Then dive into the [Documentation](/documentatiion/) section to get up to speed on the details.
-* If you're interested in contributing to the Beam SDKs or Runners, start with the [Contribute](/contribute/) section.
+* If you are interested in using Beam for your data processing tasks, use the [Get Started]({{ site.baseurl }}/get-started/) section for an overview, quickstart, and examples. Then dive into the [Documentation]({{ site.baseurl }}/documentation/) section to get up to speed on the details.
+* If you're interested in contributing to the Beam SDKs or Runners, start with the [Contribute]({{ site.baseurl }}/contribute/) section.
 
 <hr>
 <div class="row">


Mime
View raw message