move site to docs folder

Rakefile

@@ -28,7 +28,7 @@ def docs_name
 end
 
 def docs_folder
-  "site"
+  "docs"
 end
 
 def gemspec_file

docs/_data/docs.yml

@@ -46,5 +46,6 @@
 - title: Meta
   docs:
   - contributing
+  - development
   - conduct
   - history

docs/_docs/development/affinity-team-captain.md

@@ -1,6 +1,11 @@
-# Affinity Team Captains
+---
+title: Affinity Team Captains
+layout: docs
+permalink: /docs/development/affinity-team-captain/
+---
 
 **This guide is for affinity team captains.** These special people are **team maintainers** of one of our [affinity teams][] and help triage and evaluate the issues and contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 ## Affinity teams & their captains
 

docs/_docs/development/avoiding-burnout.md

@@ -1,6 +1,11 @@
-# Maintainers: Avoiding Burnout
+---
+title: "Avoiding Burnout"
+layout: docs
+permalink: /docs/development/avoiding-burnout/
+---
 
 **This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 # 1. Use Jekyll
 

docs/_docs/development/becoming-a-maintainer.md

@@ -1,6 +1,11 @@
-# Contributors: Becoming a Maintainer
+---
+title: "Becoming a Maintainer"
+layout: docs
+permalink: /docs/development/becoming-a-maintainer/
+---
 
 **This guide is for contributors.** These special people have contributed to one or more of Jekyll's repositories, but do not yet have write access to any. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 So you want to become a maintainer of a Jekyll project? We'd love to have you! Here are some things we like to see from community members before we promote them to maintainers.
 

docs/_docs/development/index.md

@@ -0,0 +1,20 @@
+---
+layout: docs
+title: Maintaining Jekyll
+permalink: /docs/development/
+---
+
+**This guide is for Jekyll contributors and maintainers.** These special people contribute to one or more of Jekyll's repositories or help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
+
+Hello! This is where we document various processes for maintaining Jekyll. Being a maintainer for any Jekyll project is a big responsibility, so we put together some helpful documentation for various tasks you might do as a maintainer.
+
+1. [Triaging and issue](triaging-an-issue/)
+2. [Reviewing a pull request](reviewing-a-pull-request/)
+3. [Merging a pull request](merging-a-pull-request/)
+4. [Avoiding burnout](avoiding-burnout/)
+5. [Special Labels](special-labels/)
+
+Interested in becoming a maintainer? Here is some documentation for **contributors**:
+
+1. [Becoming a maintainer](becoming-a-maintainer/)

docs/_docs/development/merging-a-pull-request.md

@@ -1,6 +1,11 @@
-# Maintainers: Merging a Pull Request
+---
+title: "Merging a Pull Request"
+layout: docs
+permalink: /docs/development/merging-a-pull-request/
+---
 
 **This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 ## Code Review
 

docs/_docs/development/reviewing-a-pull-request.md

@@ -1,6 +1,11 @@
-# Maintainers: Reviewing a Pull Request
+---
+title: "Reviewing a Pull Request"
+layout: docs
+permalink: /docs/development/reviewing-a-pull-request/
+---
 
 **This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 ## Respond Kindly
 
@@ -41,4 +46,3 @@ A pull request may be merged once two maintainers have reviewed the pull request
 ## Think Security
 
 We owe it to our users to ensure that using a theme from the community or building someone else's site doesn't come with built-in security vulnerabilities. Things like where files may be read from and written to are important to keep secure. Jekyll is also the basis for hosted services such as [GitHub Pages](https://pages.github.com), which cannot upgrade when security issues are introduced.
-

docs/_docs/development/special-labels.md

@@ -1,6 +1,11 @@
-# Maintainers: Special Labels
+---
+title: "Special Labels"
+layout: docs
+permalink: /docs/development/special-labels/
+---
 
 **This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 We use a series of "special labels" on GitHub.com to automate handling of some parts of the pull request and issue process. @jekyllbot may automatically apply or remove certain labels based on actions taken by users or maintainers. Below are the labels and how they work:
 

docs/_docs/development/triaging-an-issue.md

@@ -1,6 +1,11 @@
-# Maintainers: Triaging an Issue
+---
+title: "Triaging an Issue"
+layout: docs
+permalink: /docs/development/triaging-an-issue/
+---
 
 **This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
+{: .note .info }
 
 Before evaluating an issue, it is important to identify if it is a feature
 request or a bug. For the Jekyll project the following definitions are used