Introduce Prettier for formatting Markdown, YAML, and JSON configuration files

.circleci/config.yml

@@ -11,7 +11,7 @@ jobs:
         type: string
         default: 2.3.11
     executor:
-      name: 'samvera/ruby'
+      name: "samvera/ruby"
       ruby_version: << parameters.ruby_version >>
     environment:
       WAIT_FOR_JEKYLL: 10
@@ -27,14 +27,22 @@ jobs:
               echo "$(git branch --all --list master */master)"
             fi
             [[ -z "$(git branch --all --list master */master)" ]]
+      - run:
+          name: Install the NPM dependencies using Yarn
+          command: |
+            yarn install -D
+      - run:
+          name: Lint the formatting of source code files using Prettier
+          command: |
+            yarn run prettier --check .
       - samvera/bundle:
           ruby_version: << parameters.ruby_version >>
           bundler_version: << parameters.bundler_version >>
       - persist_to_workspace:
           root: ~/
           paths:
-          - project/*
-          - project/**/*
+            - project/*
+            - project/**/*
       - samvera/parallel_rspec
 
 workflows:

.prettierignore

@@ -0,0 +1,5 @@
+browse_pages.html
+search.json
+pages/*.html
+_layouts/*.html
+_includes/**/*.html

CONTRIBUTING.md

@@ -24,18 +24,18 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 
 ## Language
 
-The language we use matters.  Today, tomorrow, and for years to come
-people will read the code we write.  They will judge us for our
+The language we use matters. Today, tomorrow, and for years to come
+people will read the code we write. They will judge us for our
 design, logic, and the words we use to describe the system.
 
-Our words should be accessible.  Favor descriptive words that give
-meaning while avoiding reinforcing systemic inequities.  For example,
-in the Samvera community, we should favor using allowed\_list instead
-of whitelist, denied\_list instead of blacklist, or source/copy
+Our words should be accessible. Favor descriptive words that give
+meaning while avoiding reinforcing systemic inequities. For example,
+in the Samvera community, we should favor using allowed_list instead
+of whitelist, denied_list instead of blacklist, or source/copy
 instead of master/slave.
 
 We're going to get it wrong, but this is a call to keep working to
-make it right.  View our code and the words we choose as a chance to
+make it right. View our code and the words we choose as a chance to
 have a conversation. A chance to grow an understanding of the systems
 we develop as well as the systems in which we live.
 
@@ -46,60 +46,60 @@ further details.
 
 ## Contribution Tasks
 
-* Reporting Issues
-* Making Changes
-* Documenting Code
-* Committing Changes
-* Submitting Changes
-* Reviewing and Merging Changes
+- Reporting Issues
+- Making Changes
+- Documenting Code
+- Committing Changes
+- Submitting Changes
+- Reviewing and Merging Changes
 
 ### Reporting Issues
 
-* Make sure you have a [GitHub account](https://github.com/signup/free)
-* Submit a [Github issue](./issues) by:
-  * Clearly describing the issue
-    * Provide a descriptive summary
-    * Explain the expected behavior
-    * Explain the actual behavior
-    * Provide steps to reproduce the actual behavior
+- Make sure you have a [GitHub account](https://github.com/signup/free)
+- Submit a [Github issue](./issues) by:
+  - Clearly describing the issue
+    - Provide a descriptive summary
+    - Explain the expected behavior
+    - Explain the actual behavior
+    - Provide steps to reproduce the actual behavior
 
 ### Making Changes
 
-* Fork the repository on GitHub
-* Create a topic branch from where you want to base your work.
-  * This is usually the `main` branch.
-  * To quickly create a topic branch based on `main`; `git branch fix/main/my_contribution main`
-  * Then checkout the new branch with `git checkout fix/main/my_contribution`.
-  * Please avoid working directly on the `main` branch.
-  * Please do not create a branch called `master`. (See note below.)
-  * You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
-* Make sure you have added sufficient tests and documentation for your changes.
-  * Test functionality with RSpec; Test features / UI with Capybara.
-* Run _all_ the tests to assure nothing else was accidentally broken.
+- Fork the repository on GitHub
+- Create a topic branch from where you want to base your work.
+  - This is usually the `main` branch.
+  - To quickly create a topic branch based on `main`; `git branch fix/main/my_contribution main`
+  - Then checkout the new branch with `git checkout fix/main/my_contribution`.
+  - Please avoid working directly on the `main` branch.
+  - Please do not create a branch called `master`. (See note below.)
+  - You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
+- Make sure you have added sufficient tests and documentation for your changes.
+  - Test functionality with RSpec; Test features / UI with Capybara.
+- Run _all_ the tests to assure nothing else was accidentally broken.
 
 NOTE: This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct)
 and [language recommendations](#language).
-Please ***do not*** create a branch called `master` for this repository or as part of
+Please **_do not_** create a branch called `master` for this repository or as part of
 your pull request; the branch will either need to be removed or renamed before it can
 be considered for inclusion in the code base and history of this repository.
 
 ### Documenting Code
 
-* All new public methods, modules, and classes should include inline documentation in [YARD](http://yardoc.org/).
-  * Documentation should seek to answer the question "why does this code exist?"
-* Document private / protected methods as desired.
-* If you are working in a file with no prior documentation, do try to document as you gain understanding of the code.
-  * If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your pull request. You can use the 'blame' button on GitHub to identify the original developer of the code and @mention them in your comment.
-  * This work greatly increases the usability of the code base and supports the on-ramping of new committers.
-  * We will all be understanding of one another's time constraints in this area.
-* [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)
+- All new public methods, modules, and classes should include inline documentation in [YARD](http://yardoc.org/).
+  - Documentation should seek to answer the question "why does this code exist?"
+- Document private / protected methods as desired.
+- If you are working in a file with no prior documentation, do try to document as you gain understanding of the code.
+  - If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your pull request. You can use the 'blame' button on GitHub to identify the original developer of the code and @mention them in your comment.
+  - This work greatly increases the usability of the code base and supports the on-ramping of new committers.
+  - We will all be understanding of one another's time constraints in this area.
+- [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)
 
 ### Committing changes
 
-* Make commits of logical units.
-* Check for unnecessary whitespace with `git diff --check` before committing.
-* Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
-* If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
+- Make commits of logical units.
+- Check for unnecessary whitespace with `git diff --check` before committing.
+- Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+- If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
 
 ```
     Present tense short summary (50 characters or less)
@@ -131,25 +131,25 @@ be considered for inclusion in the code base and history of this repository.
       long to fit in 72 characters
 ```
 
-* Make sure you have added the necessary tests for your changes.
-* Run _all_ the tests to assure nothing else was accidentally broken.
-* When you are ready to submit a pull request
+- Make sure you have added the necessary tests for your changes.
+- Run _all_ the tests to assure nothing else was accidentally broken.
+- When you are ready to submit a pull request
 
 ### Submitting Changes
 
-* Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
-* Make sure your branch is up to date with its parent branch (i.e. main)
-  * `git checkout main`
-  * `git pull --rebase`
-  * `git checkout <your-branch>`
-  * `git rebase main`
-  * It is a good idea to run your tests again.
-* If you've made more than one commit take a moment to consider whether squashing commits together would help improve their logical grouping.
-  * [Detailed Walkthrough of One Pull Request per Commit](http://ndlib.github.io/practices/one-commit-per-pull-request/)
-  * `git rebase --interactive main` ([See Github help](https://help.github.com/articles/interactive-rebase))
-  * Squashing your branch's changes into one commit is "good form" and helps the person merging your request to see everything that is going on.
-* Push your changes to a topic branch in your fork of the repository.
-* Submit a pull request from your fork to the project.
+- Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
+- Make sure your branch is up to date with its parent branch (i.e. main)
+  - `git checkout main`
+  - `git pull --rebase`
+  - `git checkout <your-branch>`
+  - `git rebase main`
+  - It is a good idea to run your tests again.
+- If you've made more than one commit take a moment to consider whether squashing commits together would help improve their logical grouping.
+  - [Detailed Walkthrough of One Pull Request per Commit](http://ndlib.github.io/practices/one-commit-per-pull-request/)
+  - `git rebase --interactive main` ([See Github help](https://help.github.com/articles/interactive-rebase))
+  - Squashing your branch's changes into one commit is "good form" and helps the person merging your request to see everything that is going on.
+- Push your changes to a topic branch in your fork of the repository.
+- Submit a pull request from your fork to the project.
 
 ### Reviewing and Merging Changes
 
@@ -163,30 +163,30 @@ Common checks that may occur in our repositories:
 
 If one or more of the required checks failed (or are incomplete), the code should not be merged (and the UI will not allow it). If all of the checks have passed, then anyone on the project (including the pull request submitter) may merge the code.
 
-*Example: Carolyn submits a pull request, Justin reviews the pull request and approves. However, Justin is still waiting on other checks (CI tests are usually the culprit), so he does not merge the pull request. Eventually, all of the checks pass. At this point, Carolyn or anyone else may merge the pull request.*
+_Example: Carolyn submits a pull request, Justin reviews the pull request and approves. However, Justin is still waiting on other checks (CI tests are usually the culprit), so he does not merge the pull request. Eventually, all of the checks pass. At this point, Carolyn or anyone else may merge the pull request._
 
 #### Things to Consider When Reviewing
 
 First, the person contributing the code is putting themselves out there. Be mindful of what you say in a review.
 
-* Ask clarifying questions
-* State your understanding and expectations
-* Provide example code or alternate solutions, and explain why
+- Ask clarifying questions
+- State your understanding and expectations
+- Provide example code or alternate solutions, and explain why
 
 This is your chance for a mentoring moment of another developer. Take time to give an honest and thorough review of what has changed. Things to consider:
 
-  * Does the commit message explain what is going on?
-  * Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
-  * Do new or changed methods, modules, and classes have documentation?
-  * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
-  * Does the description of the new/changed specs match your understanding of what the spec is doing?
-  * Did the Continuous Integration tests complete successfully?
+- Does the commit message explain what is going on?
+- Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
+- Do new or changed methods, modules, and classes have documentation?
+- Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
+- Does the description of the new/changed specs match your understanding of what the spec is doing?
+- Did the Continuous Integration tests complete successfully?
 
 If you are uncertain, bring other contributors into the conversation by assigning them as a reviewer.
 
 # Additional Resources
 
-* [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
-* [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
-* [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)
+- [General GitHub documentation](http://help.github.com/)
+- [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
+- [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
+- [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)