Get rid of some of the permalinks that are breaking everything

Author: heathermiller

contribute/bug-reporting-guide.md

@@ -1,7 +1,7 @@
 ---
 title: Bug Reporting
 layout: inner-page-no-masthead
-permalink: /contribute/bug-reporting-guide/
+# permalink: /contribute/bug-reporting-guide/
 includeTOC: true
 ---
 

contribute/codereviews.md

@@ -1,18 +1,18 @@
 ---
 title: Code Review Contributions
 layout: inner-page-no-masthead
-permalink: /contribute/codereviews/
+# permalink: /contribute/codereviews/
 includeTOC: true
 ---
 ## Code Review Contributions
 
-In addition to [bug fixing](/contribute/guide/), you can help us review 
-[waiting pull requests](#pull-requests-awaiting-comment). 
+In addition to [bug fixing](/contribute/guide/), you can help us review
+[waiting pull requests](#pull-requests-awaiting-comment).
 This is also a good (and recommended) way to get to know the feel of
 the bug-fixing and submissions process before jumping in with your
 own pull requests.
 
- 
+
 ### Review Guidelines
 
 [Code of Conduct reminder](/conduct/)

contribute/corelibs.md

@@ -1,7 +1,7 @@
 ---
 title: Core Library Contributions
 layout: inner-page-no-masthead
-permalink: /contribute/corelibs/
+# permalink: /contribute/corelibs/
 includeTOC: true
 ---
 ## Core Library Contributions
@@ -10,14 +10,14 @@ There are several options for contributing to Scala's core libraries. You can:
 
 * Help with [Documentation](/contribute/scala-standard-library-api-documentation/).
 * [Report Bugs or Issues](/contribute/bug-reporting-guide/) against the core libraries.
-* [Fix Bugs or Issues](/contribute/guide/) against the 
+* [Fix Bugs or Issues](/contribute/guide/) against the
   [reported library bugs/issues](https://issues.scala-lang.org/issues/?filter=13001).
 * Contribute significant new functionality or a new API by submitting
   a Scala Library Improvement Process (SLIP) Document.
 
 ### Submitting a SLIP
 
-For significant new functionality or a whole new API to be considered for 
+For significant new functionality or a whole new API to be considered for
 inclusion in the core Scala distribution, you will be asked to submit a SLIP (Scala Library Improvement Process) document.
 
 Please see [instructions for submitting a new SLIP](http://docs.scala-lang.org/sips/slip-submission.html) and familiarize yourself with the [SIP/SLIP](http://docs.scala-lang.org/sips/) section of the Scala documentation site. Also please pay particular attention to the [pre-requisites](http://docs.scala-lang.org/sips/slip-submission.html) before submitting a SLIP.

contribute/documentation.md

@@ -1,7 +1,7 @@
 ---
 title: Documentation Contributions
 layout: inner-page-no-masthead
-permalink: /contribute/documentation/
+# permalink: /contribute/documentation/
 includeTOC: true
 ---
 ## Contributing Documentation to the Scala project
@@ -14,20 +14,20 @@ There are several ways you can help out with the improvement of Scala documentat
 
 Please read this page, and the pages linked from this one, fully before contributing documentation. Many of the questions you have will be answered in these resources. If you have a question that isn't answered, feel free to ask on the [scala-internals Google group](https://groups.google.com/forum/#!forum/scala-internals) and then, please, submit a pull request with updated documentation reflecting that answer.
 
-**General requirements** for documentation submissions include spell-checking all written language, ensuring code samples compile and run correctly, correct grammar, and clean formatting/layout of the documentation. 
+**General requirements** for documentation submissions include spell-checking all written language, ensuring code samples compile and run correctly, correct grammar, and clean formatting/layout of the documentation.
 
 Thanks
 
 ### API Documentation (Scaladoc)
 
 The Scala API documentation lives with the scala project source code. There are many ways you can help with improving Scaladoc, including:
 
-* [Log issues for missing scaladoc documentation](/contribute/scala-standard-library-api-documentation/#contribute-api-documentation-bug-reports) - 
+* [Log issues for missing scaladoc documentation](/contribute/scala-standard-library-api-documentation/#contribute-api-documentation-bug-reports) -
 Please *follow the issue submission process closely* to help prevent duplicate issues being created.
 * [Claim Scaladoc Issues and Provide Documentation](/contribute/scala-standard-library-api-documentation/) - please claim issues prior to working on a specific scaladoc task to prevent duplication of effort. If you sit on an issue for too long without submitting a pull request, it will revert back to unassigned and you will need to re-claim it.
-* You can also just 
-[submit new Scaladoc](/contribute/scala-standard-library-api-documentation/) 
-without creating an issue, but please look to see if there is an issue already submitted for your task and claim it if there is. If not, please post your intention to work on a specific scaladoc task on scala-internals so that people know what you are doing. 
+* You can also just
+[submit new Scaladoc](/contribute/scala-standard-library-api-documentation/)
+without creating an issue, but please look to see if there is an issue already submitted for your task and claim it if there is. If not, please post your intention to work on a specific scaladoc task on scala-internals so that people know what you are doing.
 
 ### The Main Scala Documentation Site
 
@@ -43,15 +43,15 @@ without creating an issue, but please look to see if there is an issue already s
 * SIP (Scala Improvement Process) Proposals
 and more
 
-Please read [contributing to the docs.scala-lang.org site](http://docs.scala-lang.org/contribute.html) through before embarking on changes. The site uses 
+Please read [contributing to the docs.scala-lang.org site](http://docs.scala-lang.org/contribute.html) through before embarking on changes. The site uses
 the [Jekyll](http://jekyllrb.com/) markdown engine so you will need to follow the instructions to get that running as well.
 
 ### Updating scala-lang.org
 
 Additional high-level documentation (including documentation on contributing
-to Scala and related projects) is provided on the main 
-[Scala Language site](http://scala-lang.org), and is also kept in the 
-[scala-lang github project](https://github.com/scala/scala-lang) which may be forked to create pull requests. 
+to Scala and related projects) is provided on the main
+[Scala Language site](http://scala-lang.org), and is also kept in the
+[scala-lang github project](https://github.com/scala/scala-lang) which may be forked to create pull requests.
 
 Please read both the
 [docs.scala-lang.org contribution](http://docs.scala-lang.org/contribute.html) document and the [scala-lang.org github README](https://github.com/scala/scala-lang#scala-langorg) before embarking on any changes to the Scala language site, as it uses the same Jekyll markdown tool and many of the same conventions as the Scala documentation site.

contribute/guide.md

@@ -1,7 +1,7 @@
 ---
 title: Contributing guide
 layout: inner-page-no-masthead
-permalink: /contribute/guide/
+# permalink: /contribute/guide/
 includeTOC: true
 ---
 
@@ -54,9 +54,9 @@ unencumbered by copyrights or patents.
 
 This is the impatient developer's checklist for the steps to submit a bug-fix pull request to the Scala project. For more information, description and justification for the steps, follow the links in that step. Further specific instructions for the release of Scala you are targeting can be found in the `CONTRIBUTING.md` file for that [github branch](https://github.com/scala/scala)
 
-1. [Select a bug to fix from JIRA](/contribute/#community-tickets), or if you found the bug yourself and want to fix it, [create a JIRA issue](/contribute/bug-reporting-guide/) (but please 
+1. [Select a bug to fix from JIRA](/contribute/#community-tickets), or if you found the bug yourself and want to fix it, [create a JIRA issue](/contribute/bug-reporting-guide/) (but please
 [make sure it's not a duplicate](/contribute/bug-reporting-guide/#reporting-confirmed-bugs-is-a-sin)).
-2. Optional ([but recommended](/contribute/scala-internals/#why-its-a-good-idea)), announce your intention to work on the bug on [scala-internals](/contribute/scala-internals/). After all, don't you want to work on a team with 
+2. Optional ([but recommended](/contribute/scala-internals/#why-its-a-good-idea)), announce your intention to work on the bug on [scala-internals](/contribute/scala-internals/). After all, don't you want to work on a team with
 [these friendly people](/contribute/hacker-guide/#connect) - it's one of the perks of contributing.
 3. [Fork the Scala repository](/contribute/hacker-guide/#fork) and clone your fork (if you haven't already).
 4. [Create a feature branch](/contribute/hacker-guide/#branch) to work on: use the branch name `issue/NNNN` where NNNN is the JIRA issue number.

contribute/hacker-guide.md

@@ -2,7 +2,7 @@
 title: Scala hacker guide
 by: Eugene Burmako
 layout: inner-page-no-masthead
-permalink: /contribute/hacker-guide/
+# permalink: /contribute/hacker-guide/
 includeTOC: true
 ---
 <br>
@@ -54,7 +54,7 @@ it probably makes sense to familiarize yourself with Git first. We recommend
 
 * the [Git Pro](http://git-scm.com/book/en/) online book.
 * the help page on [Forking a Git Repository](https://help.github.com/articles/fork-a-repo).
-* this great training tool [LearnGitBranching](http://pcottle.github.io/learnGitBranching/). One hour hands-on training helps more than 1000 hours reading. 
+* this great training tool [LearnGitBranching](http://pcottle.github.io/learnGitBranching/). One hour hands-on training helps more than 1000 hours reading.
 
 ### Fork
 

contribute/index.md

@@ -1,7 +1,7 @@
 ---
 title: Contribute
 layout: inner-page-no-masthead
-permalink: /contribute/
+# permalink: /contribute/
 includeTOC: true
 ---
 
@@ -22,7 +22,7 @@ how to efficiently report a bug.
 
 ### Contribute
 
-Coordination of contribution efforts takes place on the 
+Coordination of contribution efforts takes place on the
 [scala-internals Google group](/contribute/scala-internals/).
 
 {% include column-list-of-items.html collection=site.contribute_resources %}

contribute/partest-guide.md

@@ -1,7 +1,7 @@
 ---
 title: Running the Test Suite
 layout: inner-page-no-masthead
-permalink: /contribute/partest-guide/
+# permalink: /contribute/partest-guide/
 includeTOC: true
 ---
 
@@ -14,11 +14,11 @@ The test suite can be run by using ant from the command line:
 	$ ant test.suite
 
 ## Standalone
-	
-There are launch scripts `partest` and `partest.bat` in the `test` folder of the scala project. To have partest run failing tests only and print details about test failures to the console, you can use 
-	
+
+There are launch scripts `partest` and `partest.bat` in the `test` folder of the scala project. To have partest run failing tests only and print details about test failures to the console, you can use
+
 	./test/partest --show-diff --show-log --failed
-	
+
 You can get a summary of the usage by running partest without arguments.
 
 * Most commonly you want to invoke partest with an option that tells it which part of the tests to run. For example `--all`, `--pos`, `--neg` or `--run`.
@@ -29,13 +29,13 @@ You can get a summary of the usage by running partest without arguments.
 * You can use the `SCALAC_OPTS` environment variable to pass command line options to the compiler.
 * You can use the `JAVA_OPTS` environment variable to pass command line options to the runner (e.g., for `run/jvm` tests).
 * The launch scripts run partest as follows:
-	
+
 		scala -cp <path to partest classes> scala.tools.partest.nest.NestRunner <options>
-	
+
 	Partest classes from a `quick` build, e.g., can be found in `./build/quick/classes/partest/`.
-	
+
 	Partest will tell you where it loads compiler/library classes from by adding the `partest.debug` property:
-	
+
 		scala -Dpartest.debug=true -cp <path to partest classes> scala.tools.partest.nest.NestRunner <options>
 
 
@@ -46,10 +46,10 @@ Tests that depend on [ScalaCheck](https://github.com/rickynils/scalacheck) can b
 
 	import org.scalacheck._
 	import Prop._
-	
+
 	object Test {
 		val prop_ConcatLists = property{ (l1: ListInt, l2: ListInt) =>
-			l1.size + l2.size == (l1 ::: l2).size 
+			l1.size + l2.size == (l1 ::: l2).size
 		}
 
 		val tests = List(("prop_ConcatLists", prop_ConcatLists))
@@ -59,10 +59,10 @@ Tests that depend on [ScalaCheck](https://github.com/rickynils/scalacheck) can b
 
 ### Windows
 
-Some tests might fail because line endings in the `.check` files and the produced results do not match. In that case, set either 
+Some tests might fail because line endings in the `.check` files and the produced results do not match. In that case, set either
 
-	git config core.autocrlf false 
+	git config core.autocrlf false
 
-or 
+or
 
-	git config core.autocrlf input 
+	git config core.autocrlf input

contribute/scala-internals.md

@@ -7,11 +7,11 @@ includeTOC: true
 
 ## scala-internals
 
-The [scala-internals mailing list](https://groups.google.com/d/forum/scala-internals) is where technical and logistical discussions concerning bugs, bug fixes, documentation, improvements, new features and other contributor related topics occur. 
+The [scala-internals mailing list](https://groups.google.com/d/forum/scala-internals) is where technical and logistical discussions concerning bugs, bug fixes, documentation, improvements, new features and other contributor related topics occur.
 
 ### Coordinating on scala-internals
 
-Prior to commencing on contribution work on larger changes to the Scala project, it is recommended (but not required) that you make a post on scala-internals announcing your intention. It's a great time to invite any help, advice or ask any questions you might have. It's also a great place to meet peers, one of whom will probably be reviewing your contribution at some point.  For smaller bug fixes or documentation changes where the risk of effort duplication is minimal, you can skip this post. 
+Prior to commencing on contribution work on larger changes to the Scala project, it is recommended (but not required) that you make a post on scala-internals announcing your intention. It's a great time to invite any help, advice or ask any questions you might have. It's also a great place to meet peers, one of whom will probably be reviewing your contribution at some point.  For smaller bug fixes or documentation changes where the risk of effort duplication is minimal, you can skip this post.
 
 To help subscribers on the scala-internals list to sort through the postings, we request that the following topic labels are applied when you start a new post please:
 
@@ -44,4 +44,3 @@ While it is optional to announce your intentions/work items on scala-internals b
 * There are a lot of nice people waiting to talk to you on scala-internals, you might be surprised how valuable and pleasant you find the experience of talking to them.
 
 If all of this has not convinced you then, please, go ahead and work on contributions anyway. It *is* less important to post to scala-internals first for small, self contained bugs than it is for larger issues or features, and not having posted first will not be a reason for your PR to be rejected, it just might be a rougher review/merge process than if you had posted first. It's your choice.
-

contribute/scala-standard-library-api-documentation.md

@@ -1,7 +1,7 @@
 ---
 title: Contribute to API Documentation
 layout: inner-page-no-masthead
-permalink: /contribute/scala-standard-library-api-documentation/
+# permalink: /contribute/scala-standard-library-api-documentation/
 includeTOC: true
 ---
 

contribute/tools.md

@@ -1,7 +1,7 @@
 ---
 title: IDE and Build Tool Contributions
 layout: inner-page-no-masthead
-permalink: /contribute/tools/
+# permalink: /contribute/tools/
 includeTOC: true
 
 # Projects list:
@@ -45,7 +45,7 @@ projects:
     homeLink: http://docs.scala-lang.org/tutorials/partest-guide.html
     issuesLink: https://github.com/scala/scala-partest/issues
     readmeLink: https://github.com/scala/scala-partest/blob/master/README.md
-    contributingLink: 
+    contributingLink:
   - title: Ensime
     description: Scala Support for Text Editors
     icon: https://avatars0.githubusercontent.com/u/5089042?v=3&s=200
@@ -76,7 +76,7 @@ projectsInNeed:
     description: Scala Decoder (part of scala/scala)
     icon: https://avatars1.githubusercontent.com/u/57059?v=3&s=200
     link: https://github.com/scala/scala
-    homeLink: 
+    homeLink:
     issuesLink: https://issues.scala-lang.org/issues/?jql=status%20%3D%20Open%20AND%20text%20~%20%22scalap%22
     readmeLink: https://github.com/scala/scala#welcome
     contributingLink: https://github.com/sbt/sbt/blob/0.13/CONTRIBUTING.md
@@ -103,7 +103,7 @@ if you would like to help revive them.
 
 ### Broken Links?
 
-Stuff changes. Found a broken link or something that needs updating on this page? Please, consider [submitting a documentation pull request](/contribute/documentation/#updating-scala-langorg) to fix it. 
+Stuff changes. Found a broken link or something that needs updating on this page? Please, consider [submitting a documentation pull request](/contribute/documentation/#updating-scala-langorg) to fix it.
 
 ### Projects
 
@@ -113,4 +113,4 @@ Stuff changes. Found a broken link or something that needs updating on this page
 
 The following projects are important to the Scala community but are particularly in need of contributors to continue their development.
 
-{% include contributions-projects-list.html collection=page.projectsInNeed %}
+{% include contributions-projects-list.html collection=page.projectsInNeed %}