Include contributions folder

Author: keveleigh

Pipelines/Scripts/prepare-pages.ps1

@@ -45,6 +45,24 @@ parent: Home
 "@
 Add-Content -Path $destination -Value (Get-Content -Path (Join-Path $ProjectRoot "CONTRIBUTING.md"))
 
+$fileFolder = Join-Path $docs "contributions"
+New-Item -Path $fileFolder -ItemType Directory -Force
+
+Get-ChildItem -Path (Join-Path $ProjectRoot "contributions") -File | ForEach-Object {
+    # Create file, add front matter, and copy content
+    $destination = Join-Path $fileFolder $_.Name
+    $fileTitle = Select-String -Pattern "# (.+)" -Path $_ | Select-Object -First 1
+    New-Item -Path $destination -ItemType File -Force -Value @"
+---
+title: $($fileTitle.Matches ? $fileTitle.Matches[0].Groups[1] : $_.BaseName)
+parent: Contributing
+---
+
+
+"@
+    Add-Content -Path $destination -Value (Get-Content -Path $_)
+}
+
 $destination = Join-Path $docs "LICENSE.md"
 # Create page, add front matter, and copy content
 New-Item -Path $destination -ItemType File -Force -Value @"

contributions/code-contributions.md

@@ -1,4 +1,4 @@
-# Code Contributions
+# Code contributions
 
 This project is an open source project under the BSD 3-Clause license. Community contributions are welcome and appreciated, both for new features and bug fixes.
 

contributions/code-owners.md

@@ -1,4 +1,4 @@
-# Code Owners
+# Code owners
 
 Code owners are Contributors that a maintain particular parts of the Project, and are defined in [CODEOWNERS](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) file.
 

contributions/merging-pull-requests.md

@@ -1,4 +1,4 @@
-# Approving Pull Requests
+# Approving pull requests
 
 All merges into the `main` branch must be done through a pull request process to ensure changes are reviewed and approved by code owners.
 

contributions/opening-and-assessing-issues.md

@@ -1,4 +1,4 @@
-# Opening and Assessing Issues
+# Opening and assessing issues
 
 All Contributors can open issues using the templates available for a [bug](https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/issues/new?assignees=&labels=Bug&template=bug-report.md&title=), [document issue](https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/issues/new?assignees=&labels=Documentation&template=documentation-issue.md&title=), [feature request](https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/issues/new?assignees=&labels=Documentation&template=documentation-issue.md&title=), and [security vulnerability](https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/security/advisories/new). Consider the following when opening a new Project issue:
 
@@ -11,7 +11,7 @@ All Contributors can open issues using the templates available for a [bug](https
 
 ## The role
 
-Contributors with the **triage** role can assist with issue assessment. 
+Contributors with the **triage** role can assist with issue assessment.
 
 ## Assessing issues
 

contributions/project-tenets.md

@@ -1,4 +1,4 @@
-# MRTK3 Tenets
+# Project tenets
 
 The following are the guiding principles by which the MRTK3 project abides. This is a living document and the list may be modified over time.
 

contributions/versioning-and-releases.md

@@ -1,4 +1,4 @@
-# Versioning and Releases
+# Versioning and releases
 
 ## Semantic versioning