Merge pull request scala#679 from scala/pr/667

Scala-lang redesign

Author: heathermiller

_contribute_resources/1-documentation.md

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

_contribute_resources/2-bug-fixes.md

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

_contribute_resources/3-code-reviews.md

@@ -0,0 +1,8 @@
+---
+title: Code Reviews
+link: /contribute/codereviews/
+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), 
+[scala/scala.github.com](https://github.com/scala/scala.github.com/pulls)and others.

_contribute_resources/4-core-libraries.md

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

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

@@ -0,0 +1,6 @@
+---
+title: IDE and Build Tools
+link: /contribute/tools/
+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

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

contribute/bug-reporting-guide.md

@@ -1,6 +1,8 @@
 ---
-layout: page
 title: Bug Reporting
+layout: inner-page-no-masthead
+permalink: /contribute/bug-reporting-guide/
+includeTOC: true
 ---
 
 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?*.

contribute/codereviews.md

@@ -1,10 +1,12 @@
 ---
-layout: page
 title: Code Review Contributions
+layout: inner-page-no-masthead
+permalink: /contribute/codereviews/
+includeTOC: true
 ---
 ## Code Review Contributions
 
-In addition to [bug fixing](./guide.html), you can help us review 
+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
@@ -13,7 +15,7 @@ own pull requests.
 
 ### Review Guidelines
 
-[Code of Conduct reminder](../conduct.html)
+[Code of Conduct reminder](/conduct/)
 
 * Keep comments on-topic, concise and precise.
 * Attach comments to particular lines or regions they pertain to whenever possible.
@@ -49,4 +51,4 @@ own pull requests.
 </div>
 </div>
 
-Also note that the [Tools contributions](./tools.html) page has more projects that will generate pull requests.
+Also note that the [Tools contributions](/contribute/tools/) page has more projects that will generate pull requests.

contribute/corelibs.md

@@ -1,14 +1,16 @@
 ---
-layout: page
 title: Core Library Contributions
+layout: inner-page-no-masthead
+permalink: /contribute/corelibs/
+includeTOC: true
 ---
 ## Core Library Contributions
 
 There are several options for contributing to Scala's core libraries. You can:
 
-* Help with [Documentation](./scala-standard-library-api-documentation.html).
-* [Report Bugs or Issues](./bug-reporting-guide.html) against the core libraries.
-* [Fix Bugs or Issues](./guide.html) against the 
+* 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 
   [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.

contribute/documentation.md

@@ -1,6 +1,8 @@
 ---
-layout: page
 title: Documentation Contributions
+layout: inner-page-no-masthead
+permalink: /contribute/documentation/
+includeTOC: true
 ---
 ## Contributing Documentation to the Scala project
 
@@ -20,11 +22,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](./scala-standard-library-api-documentation.html#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](./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](/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](./scala-standard-library-api-documentation.html) 
+[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