migrate urls to /overviews/contribute

fix broken links

Author: bishabosha

_contribute_resources/1-documentation.md

@@ -1,6 +1,6 @@
 ---
 title: Documentation
-link: /contribute/documentation.html
+link: /overviews/contribute/documentation.html
 icon: fa fa-book
 ---
-[Scaladoc (API)](/contribute/scala-standard-library-api-documentation.html), [docs.scala-lang.org](https://docs.scala-lang.org/contribute.html) and [scala-lang.org](https://github.com/scala/scala-lang).
+[Scaladoc (API)](/overviews/contribute/scala-standard-library-api-documentation.html), [docs.scala-lang.org](/contribute.html) and [scala-lang.org](https://github.com/scala/scala-lang).

_contribute_resources/2-bug-fixes.md

@@ -1,6 +1,6 @@
 ---
 title: Bug fixes
-link: /contribute/guide.html
+link: /overviews/contribute/guide.html
 icon: fa fa-bug
 ---
-Issues with the tools, core libraries and compiler. Also you can help us by [reporting bugs](/contribute/bug-reporting-guide.html).
+Issues with the tools, core libraries and compiler. Also you can help us by [reporting bugs](/overviews/contribute/bug-reporting-guide.html).

_contribute_resources/3-code-reviews.md

@@ -1,8 +1,8 @@
 ---
 title: Code Reviews
-link: /contribute/codereviews.html
+link: /overviews/contribute/codereviews.html
 icon: fa fa-eye
 ---
-Review pull requests against [scala/scala](https://github.com/scala/scala/pulls), 
-[scala/scala-lang](https://github.com/scala/scala-lang/pulls), 
+Review pull requests against [scala/scala](https://github.com/scala/scala/pulls),
+[scala/scala-lang](https://github.com/scala/scala-lang/pulls),
 [scala/docs.scala-lang](https://github.com/scala/docs.scala-lang/pulls) and others.

_contribute_resources/4-core-libraries.md

@@ -1,6 +1,6 @@
 ---
 title: Core Libraries
-link: /contribute/corelibs.html
+link: /overviews/contribute/corelibs.html
 icon: fa fa-clipboard
 ---
 Update and expand the capabilities of the core (and associated) Scala libraries.

_contribute_resources/5-ide-and-build-tools.md

@@ -1,6 +1,6 @@
 ---
 title: IDE and Build Tools
-link: /contribute/tools.html
+link: /overviews/contribute/tools.html
 icon: fa fa-terminal
 ---
 Enhance the Scala tools with features for build tools, IDE plug-ins and other related projects.

_contribute_resources/6-compiler-language.md

@@ -1,6 +1,6 @@
 ---
 title: Compiler/Language
-link: /contribute/guide.html#larger-changes-new-features
+link: /overviews/contribute/guide.html#larger-changes-new-features
 icon: fa fa-cogs
 ---
 Larger language features and compiler enhancements including language specification and SIPs.

_overviews/contribute/bug-reporting-guide.md

@@ -4,7 +4,6 @@ layout: multipage-overview
 num: 7
 partof: scala-contribution
 overview-name: Contributing to Scala
-permalink: /contribute/bug-reporting-guide.html
 ---
 
 The Scala compiler and standard library bug tracker is located at [https://github.com/scala/bug](https://github.com/scala/bug). Before you submit a bug make sure that it is certainly a bug by following instructions in *Is it a Bug?*.

_overviews/contribute/codereviews.md

@@ -4,11 +4,10 @@ layout: multipage-overview
 num: 3
 partof: scala-contribution
 overview-name: Contributing to Scala
-permalink: /contribute/codereviews.html
 ---
 ## Code Review Contributions
 
-In addition to [bug fixing](/contribute/guide.html), you can help us review
+In addition to [bug fixing](/overviews/contribute/guide.html), 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
@@ -17,7 +16,7 @@ own pull requests.
 
 ### Review Guidelines
 
-[Code of Conduct reminder]({{ site.baseurl }}/conduct.html)
+[Code of Conduct reminder](https://scala-lang.org/conduct.html)
 
 * Keep comments on-topic, concise and precise.
 * Attach comments to particular lines or regions they pertain to whenever possible.
@@ -53,4 +52,4 @@ own pull requests.
 </div>
 </div>
 
-Also note that the [Tools contributions](/contribute/tools.html) page has more projects that will generate pull requests.
+Also note that the [Tools contributions](/overviews/contribute/tools.html) page has more projects that will generate pull requests.

_overviews/contribute/corelibs.md

@@ -4,15 +4,14 @@ layout: multipage-overview
 num: 4
 partof: scala-contribution
 overview-name: Contributing to Scala
-permalink: /contribute/corelibs.html
 ---
 ## Core Library Contributions
 
 There are several options for contributing to Scala's core libraries. You can:
 
-* Help with [Documentation](/contribute/documentation.html).
-* [Report Bugs or Issues](/contribute/bug-reporting-guide.html) against the core libraries.
-* [Fix Bugs or Issues](/contribute/guide.html) against the
+* Help with [Documentation](/overviews/contribute/documentation.html).
+* [Report Bugs or Issues](/overviews/contribute/bug-reporting-guide.html) against the core libraries.
+* [Fix Bugs or Issues](/overviews/contribute/guide.html) against the
   [reported library bugs/issues](https://github.com/scala/bug).
 
 ### Significant changes

_overviews/contribute/documentation.md

@@ -4,7 +4,6 @@ layout: multipage-overview
 num: 5
 partof: scala-contribution
 overview-name: Contributing to Scala
-permalink: /contribute/documentation.html
 ---
 ## Contributing Documentation to the Scala project
 
@@ -24,11 +23,11 @@ Thanks
 
 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.html#contribute-api-documentation-bug-reports) -
+* [Log issues for missing scaladoc documentation](/overviews/contribute/scala-standard-library-api-documentation.html#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.html) - 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.
+* [Claim Scaladoc Issues and Provide Documentation](/overviews/contribute/scala-standard-library-api-documentation.html) - 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.html)
+[submit new Scaladoc](/overviews/contribute/scala-standard-library-api-documentation.html)
 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 Contributors](https://contributors.scala-lang.org/) so that people know what you are doing.
 
 ### The Main Scala Documentation Site
@@ -45,7 +44,7 @@ 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](https://docs.scala-lang.org/contribute.html) through before embarking on changes. The site uses
+Please read [contributing to the docs.scala-lang.org site](/contribute.html) through before embarking on changes. The site uses
 the [Jekyll](https://jekyllrb.com/) markdown engine so you will need to follow the instructions to get that running as well.
 
 ### Updating scala-lang.org
@@ -56,4 +55,4 @@ to Scala and related projects) is provided on the main
 [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](https://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.
+[docs.scala-lang.org contribution](/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.

_overviews/contribute/guide.md

@@ -4,7 +4,6 @@ layout: multipage-overview
 num: 9
 partof: scala-contribution
 overview-name: Contributing to Scala
-permalink: /contribute/guide.html
 ---
 
 <div class="container">
@@ -14,18 +13,18 @@ permalink: /contribute/guide.html
       <p>Get a peek into the inners of the Scala compiler.</p>
     </div>
     <div class="span4 doc-block">
-      <h3><a href="{{ site.baseurl }}/contribute/bug-reporting-guide.html">Report an issue</a></h3>
+      <h3><a href="/overviews/contribute/bug-reporting-guide.html">Report an issue</a></h3>
       <p>File a bug report or a feature request.</p>
     </div>
   </div>
 
   <div class="row">
     <div class="span4 doc-block">
-      <h3><a href="{{ site.baseurl }}/contribute/#community-tickets">Community issues</a></h3>
+      <h3><a href="/overviews/contribute/index.html#community-tickets">Community issues</a></h3>
       <p>Get cracking on some easy to approach issues.</p>
     </div>
     <div class="span4 doc-block">
-      <h3><a href="{{ site.baseurl }}/contribute/hacker-guide.html">Hacker guide</a></h3>
+      <h3><a href="/overviews/contribute/hacker-guide.html">Hacker guide</a></h3>
       <p>Learn to write good code and improve your chances of contributing to the Scala galaxy.</p>
     </div>
   </div>
@@ -56,22 +55,22 @@ 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 GitHub](/contribute/#community-tickets), or if you found the bug yourself and want to fix it, [create a GitHub issue](/contribute/bug-reporting-guide.html) (but please
-[make sure it's not a duplicate](/contribute/bug-reporting-guide.html#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 Contributors](https://contributors.scala-lang.org/). After all, don't you want to work on a team with
-[these friendly people](/contribute/hacker-guide.html#1-connect) - it's one of the perks of contributing.
-3. [Fork the Scala repository](/contribute/hacker-guide.html#fork) and clone your fork (if you haven't already).
-4. [Create a feature branch](/contribute/hacker-guide.html#branch) to work on: use the branch name `issue/NNNN` where NNNN is the GitHub issue number.
-5. [Fix the bug, or implement the new small feature](/contribute/hacker-guide.html#implement), include new tests (yes, for bug fixes too).
-6. [Test, rinse](/contribute/hacker-guide.html#test) and [test some more](/contribute/partest-guide.html) until [all the tests pass](/contribute/hacker-guide.html#verify).
-7. [Commit your changes](/contribute/hacker-guide.html#commit) to your feature branch in your fork. Please choose your commit message based on the [Git Hygiene](https://github.com/scala/scala#user-content-git-hygiene) section of the Scala project README.
+1. [Select a bug to fix from GitHub](/overviews/contribute/index.html#community-tickets), or if you found the bug yourself and want to fix it, [create a GitHub issue](/overviews/contribute/bug-reporting-guide.html) (but please
+[make sure it's not a duplicate](/overviews/contribute/bug-reporting-guide.html#reporting-confirmed-bugs-is-a-sin)).
+2. Optional ([but recommended](/overviews/contribute/scala-internals.html/#why-its-a-good-idea)), announce your intention to work on the bug on [Scala Contributors](https://contributors.scala-lang.org/). After all, don't you want to work on a team with
+[these friendly people](/overviews/contribute/hacker-guide.html#1-connect) - it's one of the perks of contributing.
+3. [Fork the Scala repository](/overviews/contribute/hacker-guide.html#fork) and clone your fork (if you haven't already).
+4. [Create a feature branch](/overviews/contribute/hacker-guide.html#branch) to work on: use the branch name `issue/NNNN` where NNNN is the GitHub issue number.
+5. [Fix the bug, or implement the new small feature](/overviews/contribute/hacker-guide.html#implement), include new tests (yes, for bug fixes too).
+6. [Test, rinse](/overviews/contribute/hacker-guide.html#test) and [test some more](/overviews/contribute/partest-guide.html) until [all the tests pass](/overviews/contribute/hacker-guide.html#verify).
+7. [Commit your changes](/overviews/contribute/hacker-guide.html#commit) to your feature branch in your fork. Please choose your commit message based on the [Git Hygiene](https://github.com/scala/scala#user-content-git-hygiene) section of the Scala project README.
 8. If necessary [re-write git history](https://git-scm.com/book/en/Git-Branching-Rebasing) so that [commits are organized by major steps to the fix/feature](
 https://github.com/scala/scala#git-hygiene). For bug fixes, a single commit is requested, for features several commits may be desirable (but each separate commit must compile and pass all tests)
-9. [Submit a pull request](./hacker-guide.html#submit).
-10. [Work with a reviewer](https://github.com/scala/scala#reviewing) to [get your pull request merged in](/contribute/hacker-guide.html#review).
+9. [Submit a pull request](/overviews/contribute/hacker-guide.html#submit).
+10. [Work with a reviewer](https://github.com/scala/scala#reviewing) to [get your pull request merged in](/overviews/contribute/hacker-guide.html#review).
 11. Celebrate!
 
-Need more information or a little more hand-holding for the first one? We got you covered: take a read through the entire [Hacker Guide](./hacker-guide.html) for an example of implementing a new feature (some of the steps can be skipped for bug fixes, this will be obvious from reading it, but many of the steps here will help with bug fixes too).
+Need more information or a little more hand-holding for the first one? We got you covered: take a read through the entire [Hacker Guide](/overviews/contribute/hacker-guide.html) for an example of implementing a new feature (some of the steps can be skipped for bug fixes, this will be obvious from reading it, but many of the steps here will help with bug fixes too).
 
 ### Larger Changes, New Features
 
@@ -80,4 +79,4 @@ and on the implementation plan. Announce the change
 on the [Scala Contributors](https://contributors.scala-lang.org/) mailing list and get developer feedback. For really complex changes, a [Scala Improvement Process (SIP)](https://docs.scala-lang.org/sips/) document might be required, but the first step is always to discuss it on the mailing list and if a SIP is required, that will be discussed on the mailing list.
 
 Contributions, big or small, simple or complex, controversial or undisputed, need to materialize as patches against
-the Scala project source tree. The [hacker guide](/contribute/hacker-guide.html) will explain how to materialize your idea into a full-fledged pull request against the Scala code base.
+the Scala project source tree. The [hacker guide](/overviews/contribute/hacker-guide.html) will explain how to materialize your idea into a full-fledged pull request against the Scala code base.