Make next/previos links work

bkeepers · bkeepers · commit d626ed3eadb8 · 2016-08-09T10:57:28.000-05:00
diff --git a/_config.yml b/_config.yml
@@ -8,14 +8,10 @@ exclude:
   - script
   - test
 
-collections:
-  content:
-    output: true
-    permalink: /:path/
+permalink: /:path/
 
 defaults:
   - scope:
       path: ""
-      type: "content"
     values:
       layout: article
diff --git a/_layouts/article.html b/_layouts/article.html
@@ -0,0 +1,13 @@
+<h1>{{ page.title }}</h1>
+
+{{ content }}
+
+{% assign previous = site.pages | where: "next", page.path | first %}
+{% if previous %}
+  Previous: <a href="{{ previous.url | prepend: site.baseurl }}">{{ previous.title }}</a> |
+{% endif %}
+
+{% if page.next %}
+  {% assign next = site.pages | where: "path", page.next | first %}
+  Next: <a href="{{ next.url | prepend: site.baseurl }}">{{ next.title }}</a>
+{% endif %}
diff --git a/getting-started/branding.md b/getting-started/branding.md
@@ -1,4 +1,7 @@
-# **Branding**
+---
+title: Branding
+next: getting-started/preparing.md
+---
 
 You’ve thought about who your users are, what they need from you, and what you might be able to offer them. Next, we’ll put that research into practice as we consider the brand of your project.
 
@@ -24,7 +27,7 @@ Make sure that your project’s name doesn’t infringe upon any trademarks. A c
 
 
 
-You’ll also want to look for open source projects with a similar name, especially if you share the same language or ecosystem. If your name overlaps with a popular existing project, you will confuse your audience and make it less likely that anyone will use what you’ve created. You can check for similar project names here: [http://ivantomic.com/projects/ospnc/](http://ivantomic.com/projects/ospnc/) 
+You’ll also want to look for open source projects with a similar name, especially if you share the same language or ecosystem. If your name overlaps with a popular existing project, you will confuse your audience and make it less likely that anyone will use what you’ve created. You can check for similar project names here: [http://ivantomic.com/projects/ospnc/](http://ivantomic.com/projects/ospnc/)
 
 
 
@@ -69,5 +72,3 @@ We’re almost there! Next, we’ll walk you through a few components that every
 ### Further reading
 
 * [http://producingoss.com/en/getting-started.html#choosing-a-name](http://producingoss.com/en/getting-started.html#choosing-a-name)
-
-[Previous](setting-expecations.md) | [Next](preparing.md)
diff --git a/getting-started/index.md b/getting-started/index.md
@@ -1,4 +1,7 @@
-# Before You Get Started
+---
+title: Before you Get Started
+next: getting-started/setting-expectations.md
+---
 
 ## What does it mean to open source a project?
 
@@ -31,5 +34,3 @@ Remember: open source isn’t just for software! You can open source everything
 When you open source a project, you open yourself to feedback and suggestions from other people who are engaged with your work. It might feel intimidating to open source a project for the first time, but remember that you’re not alone.
 
 In the next section, we’ll help you figure out your goals around open sourcing your project. Understanding these goals beforehand will make it easier to manage your and others’ expectations later on.
-
-[Previous](../index.md) | [Next](setting-expectations.md)
diff --git a/getting-started/legal.md b/getting-started/legal.md
@@ -1,4 +1,6 @@
-# **The legal side of open source**
+---
+title: The legal side of open source
+---
 
 Sharing your creative work with the world can be an exciting and rewarding experience. It can also mean a bunch of legal things you didn’t know you had to worry about.
 
@@ -100,14 +102,14 @@ If you use others’ open source code to create anything that could be considere
 
 
 
-To learn more about the implications of different open source licenses, check out: [https://tldrlegal.com/](https://tldrlegal.com/) 
+To learn more about the implications of different open source licenses, check out: [https://tldrlegal.com/](https://tldrlegal.com/)
 
 
 
 ### Related content
 
 * [http://choosealicense.com](http://choosealicense.com)
 * [https://tldrlegal.com/](https://tldrlegal.com/)
-* [https://processmechanics.com/2015/07/23/a-model-ip-and-open-source-contribution-policy/](https://processmechanics.com/2015/07/23/a-model-ip-and-open-source-contribution-policy/) 
+* [https://processmechanics.com/2015/07/23/a-model-ip-and-open-source-contribution-policy/](https://processmechanics.com/2015/07/23/a-model-ip-and-open-source-contribution-policy/)
 * [https://blog.docker.com/2014/01/docker-code-contributions-require-developer-certificate-of-origin/](https://blog.docker.com/2014/01/docker-code-contributions-require-developer-certificate-of-origin/)
-* [https://www.joyent.com/blog/broadening-node-js-contributions](https://www.joyent.com/blog/broadening-node-js-contributions) 
+* [https://www.joyent.com/blog/broadening-node-js-contributions](https://www.joyent.com/blog/broadening-node-js-contributions)
diff --git a/getting-started/preparing.md b/getting-started/preparing.md
@@ -1,4 +1,8 @@
-# **Preparing for launch**
+---
+title: Preparing for launch
+previous: getting-started/branding.md
+next: marketing/index.md
+---
 
 You’re almost ready to launch your project! In this section, we’ll talk about what to include in an open source project before releasing it to the world.
 
@@ -87,25 +91,20 @@ Sometimes, it will take a long time before people notice your open source projec
 
 * Licenses
   * [https://github.com/blog/1530-choosing-an-open-source-license](https://github.com/blog/1530-choosing-an-open-source-license)
-  * [http://choosealicense.com](http://choosealicense.com) 
+  * [http://choosealicense.com](http://choosealicense.com)
 * READMEs
   * [http://tom.preston-werner.com/2010/08/23/readme-driven-development.html](http://tom.preston-werner.com/2010/08/23/readme-driven-development.html)
   * [https://github.com/matiassingers/awesome-readme](https://github.com/matiassingers/awesome-readme)
   * [https://pages.18f.gov/open-source-guide/making-readmes-readable/](https://pages.18f.gov/open-source-guide/making-readmes-readable/)
   * [https://changelog.com/a-beginners-guide-to-creating-a-readme/](https://changelog.com/a-beginners-guide-to-creating-a-readme/)
-  * [https://gist.github.com/jxson/1784669](https://gist.github.com/jxson/1784669) 
+  * [https://gist.github.com/jxson/1784669](https://gist.github.com/jxson/1784669)
 * Contributing guides
   * [https://github.com/blog/1184-contributing-guidelines](https://github.com/blog/1184-contributing-guidelines)
-  * [http://www.contribution-guide.org/](http://www.contribution-guide.org/) 
-  * [https://github.com/nayafia/contributing-template](https://github.com/nayafia/contributing-template) 
+  * [http://www.contribution-guide.org/](http://www.contribution-guide.org/)
+  * [https://github.com/nayafia/contributing-template](https://github.com/nayafia/contributing-template)
   * [http://mozillascience.github.io/working-open-workshop/contributing/](http://mozillascience.github.io/working-open-workshop/contributing/)
 * Codes of conduct
-  * [http://contributor-covenant.org/](http://contributor-covenant.org/) 
-  * [https://github.com/django/code-of-conduct](https://github.com/django/code-of-conduct) 
-  * [https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/](https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/) 
+  * [http://contributor-covenant.org/](http://contributor-covenant.org/)
+  * [https://github.com/django/code-of-conduct](https://github.com/django/code-of-conduct)
+  * [https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/](https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/)
   * [https://github.com/docker/docker/blob/master/CONTRIBUTING.md#docker-community-guidelines/](https://github.com/docker/docker/blob/master/CONTRIBUTING.md#docker-community-guidelines/)
-
-
-[Previous](branding.md) | [Next](../marketing/index.md)
-
-
diff --git a/getting-started/setting-expectations.md b/getting-started/setting-expectations.md
@@ -1,4 +1,7 @@
-# Setting expectations
+---
+title: Setting expectations
+next: getting-started/branding.md
+---
 
 There are many reasons to open source a project. It’s a good idea to figure out yours before going public with your project. What you want to get out of the experience will guide how you manage your project and help you figure out where to say yes (and no!).
 
@@ -36,7 +39,7 @@ If you’re hoping to get feedback on something you’ve created, consider askin
 
 ## Figure out what others need from you
 
-Finally, open sourcing a project is a two-way street. People who use your project will probably ask you for things, too. 
+Finally, open sourcing a project is a two-way street. People who use your project will probably ask you for things, too.
 
 Try to anticipate these needs beforehand so you can add them to your project from the beginning. Successful open source projects try to document as much as they can in public. Much like reusable pieces of code, reusable information means less people need to ask you the same questions over and over again. (That means less work for you!)
 
@@ -60,5 +63,3 @@ We’ll also use these answers in the next section, as you consider the brand of
 
 * http://mozillascience.github.io/working-open-workshop/personas_pathways/
 * http://tom.preston-werner.com/2010/08/23/readme-driven-development.html
-
-[Previous](index.md) | [Next](branding.md)
diff --git a/index.md b/index.md
@@ -1,4 +1,7 @@
-# Welcome
+---
+title: Welcome
+next: getting-started/index.md
+---
 
 Welcome to the Open Source Handbook! We created this handbook to help creators like you successfully release and grow your projects.
 
diff --git a/marketing/building-community.md b/marketing/building-community.md
@@ -1,4 +1,7 @@
-# **Building a Community**
+---
+title: Building a community
+next: marketing/measuring.md
+---
 
 You’ve launched your project, you’re spreading the word, and people are checking out your project. Awesome! Now, how do you get them to stick around? In this section, we’ll discuss ways to encourage people to use, contribute to, and evangelize your project.
 
@@ -54,13 +57,10 @@ You’re doing great so far! Now that you’re promoting your project and growin
 
 ### Further reading
 
-* [http://radek.io/2015/10/12/marketing-for-open-source-projects-5/](http://radek.io/2015/10/12/marketing-for-open-source-projects-5/) 
+* [http://radek.io/2015/10/12/marketing-for-open-source-projects-5/](http://radek.io/2015/10/12/marketing-for-open-source-projects-5/)
 
-* [http://hood.ie/blog/welcoming-communities.html](http://hood.ie/blog/welcoming-communities.html) 
+* [http://hood.ie/blog/welcoming-communities.html](http://hood.ie/blog/welcoming-communities.html)
 
 * [https://ashfurrow.com/blog/building-popular-projects/](https://ashfurrow.com/blog/building-popular-projects/)
 
-* [http://sarah.thesharps.us/2015/10/06/what-makes-a-good-community/](http://sarah.thesharps.us/2015/10/06/what-makes-a-good-community/) 
-
-
-[Previous](spreading-word.md) | [Next](measuring.md)
+* [http://sarah.thesharps.us/2015/10/06/what-makes-a-good-community/](http://sarah.thesharps.us/2015/10/06/what-makes-a-good-community/)
diff --git a/marketing/index.md b/marketing/index.md
@@ -1,7 +1,8 @@
-# **Marketing your project**
+---
+title: Marketing your project
+next: marketing/spreading-word.md
+---
 
 This section of the handbook will help you spread the word about your project and grow your initial community of users and contributors. If you’re looking for feedback on your project, or want people to use and share your work, this part is for you.
 
 Remember, reaching your audience takes time. It may take months or years for you to grow a community around your project. Don’t give up! It’s all part of the process.
-
-[Previous](../getting-started/preparing.md) | [Next](spreading-word.md)
diff --git a/marketing/measuring.md b/marketing/measuring.md
@@ -1,4 +1,6 @@
-# **Measuring Success**
+---
+title: Measuring Success
+---
 
 Your project is starting to grow.🌱 Well, you think it’s growing. Is it growing? In this section, we’ll talk about how to measure and track the success of your open source project.
 
@@ -54,11 +56,11 @@ Here are a few types of contributor metrics you may want to regularly keep track
 
 ### Further reading
 
-* [http://blog.smartbear.com/news/measuring-success-in-an-open-source-project/](http://blog.smartbear.com/news/measuring-success-in-an-open-source-project/) 
+* [http://blog.smartbear.com/news/measuring-success-in-an-open-source-project/](http://blog.smartbear.com/news/measuring-success-in-an-open-source-project/)
 
-* [https://opensource.com/business/16/6/pirate-metrics](https://opensource.com/business/16/6/pirate-metrics) 
+* [https://opensource.com/business/16/6/pirate-metrics](https://opensource.com/business/16/6/pirate-metrics)
 
-* [https://speakerdeck.com/mikemcquaid/the-open-source-contributor-funnel](https://speakerdeck.com/mikemcquaid/the-open-source-contributor-funnel) 
+* [https://speakerdeck.com/mikemcquaid/the-open-source-contributor-funnel](https://speakerdeck.com/mikemcquaid/the-open-source-contributor-funnel)
 
 * [https://github.com/blog/2195-the-shape-of-open-source](https://github.com/blog/2195-the-shape-of-open-source)
 
diff --git a/marketing/spreading-word.md b/marketing/spreading-word.md
@@ -1,4 +1,7 @@
-# **Spreading the word**
+---
+title: Spreading the word
+next: marketing/building-community.md
+---
 
 You’ve just published your project–what’s next? It’s time to tell everybody about your hard work!
 
@@ -44,19 +47,17 @@ Spreading the word is an important step in growing the popularity of your projec
 
 In the next section, we’ll talk about how to retain those early enthusiasts and grow an engaged community around your project.
 
-[Previous](index.md) | [Next](building-community.md)
-
 ### Footnotes
 
-[1] [https://news.ycombinator.com/item?id=7531689](https://news.ycombinator.com/item?id=7531689) 
+[1] [https://news.ycombinator.com/item?id=7531689](https://news.ycombinator.com/item?id=7531689)
 
 [2] [https://github.com/swinton/codeconf/blob/master/the-hashicorp-formula-to-open-source.md](https://github.com/swinton/codeconf/blob/master/the-hashicorp-formula-to-open-source.md)
 
 ### Further reading
 
-* [https://hacks.mozilla.org/2013/05/how-to-spread-the-word-about-your-code/](https://hacks.mozilla.org/2013/05/how-to-spread-the-word-about-your-code/) 
+* [https://hacks.mozilla.org/2013/05/how-to-spread-the-word-about-your-code/](https://hacks.mozilla.org/2013/05/how-to-spread-the-word-about-your-code/)
 
-* [https://zachholman.com/posts/open-source-marketing/](https://zachholman.com/posts/open-source-marketing/) 
+* [https://zachholman.com/posts/open-source-marketing/](https://zachholman.com/posts/open-source-marketing/)
 
 * [http://readwrite.com/2014/10/10/open-source-marketing-apache-storm-nathan-merz/](http://readwrite.com/2014/10/10/open-source-marketing-apache-storm-nathan-merz/)
 
diff --git a/test/helper.rb b/test/helper.rb
@@ -15,8 +15,8 @@ def config
   Helper.config ||= Jekyll.configuration("source" => source)
 end
 
-def content
-  site.collections['content'].docs.map { |doc| doc.to_liquid }
+def pages
+  site.pages.map { |doc| doc.to_liquid }
 end
 
 def site
diff --git a/test/lint_test.rb b/test/lint_test.rb
@@ -2,7 +2,7 @@
 
 describe "lint test" do
 
-  content.each do |page|
+  pages.each do |page|
 
     describe page["path"] do
 
@@ -26,10 +26,12 @@
           it "#{name} should be of type #{attrs["type"]}" do
             assert_kind_of Kernel.const_get(attrs["type"]), @data[name] if @data[name]
           end if attrs["type"]
-
-          it "#{name} has valid attributes" do
-          end
         end
+
+        it "`next` points to a page that exists" do
+          assert pages.detect {|p| p["path"] == page["next"] },
+            "Could not find page with path #{page["next"]}"
+        end if page["next"]
       end
     end
   end
