Merge remote-tracking branch 'upstream/master' into main

.editorconfig

@@ -0,0 +1,13 @@
+# editorconfig.org
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

.gitattributes

@@ -0,0 +1,7 @@
+assets/js/lunr/* linguist-vendored
+assets/js/plugins/* linguist-vendored
+assets/js/vendor/* linguist-vendored
+assets/fonts/* linguist-vendored
+assets/js/main.min.js linguist-vendored
+_sass/so-simple/vendor/* linguist-vendored
+_sass/so-simple/functions/* linguist-vendored

.github/CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# Contributing
+
+Found a typo in the documentation? Requesting a feature or
+[bug fix][issues]? Search through the open and closed issues before [submitting an issue][new-issue] to avoid duplication. 
+
+[Pull requests][using-pull-requests] are also appreciated. If this is your first time, it may be helpful to read up on the [GitHub Flow][github-flow].
+
+If your contribution adds or changes the theme's behavior, make sure to update the documentation and/or sample content. Documentation lives in README.md while sample posts, pages, and collections are in the [`docs`](docs) and [`example`](example) folders.
+
+[issues]: https://github.com/mmistakes/so-simple-theme/issues
+[new-issue]: https://github.com/mmistakes/so-simple-theme/issues/new
+[using-pull-requests]: https://help.github.com/articles/using-pull-requests/
+[github-flow]: https://guides.github.com/introduction/flow/
+
+### Pull Requests
+
+When submitting a pull request:
+
+1. Clone the repo.
+2. Create a branch off of `master` and give it a meaningful name (e.g.
+   `my-awesome-new-feature`).
+3. Open a pull request on GitHub and describe what problem it solves.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,68 @@
+---
+name: "Bug Report"
+about: "Is something not working as expected?"
+---
+
+<!--
+  Before opening a new issue please:
+  
+  - Verify you have the latest versions of Jekyll and So Simple 
+    installed by running `bundle update`.
+  - Thoroughly read the theme's documentation at
+    https://github.com/mmistakes/so-simple-theme
+  - Search all issues at https://github.com/mmistakes/so-simple-theme/issues 
+    for solutions and to avoid duplication.
+  - Ask for help at https://talk.jekyllrb.com/
+  
+  After exhausting these suggestions use the format below.
+-->
+
+## Environment
+
+<!--
+  Please include theme version, Jekyll version, public git repository, whether 
+  you are hosting with GitHub Pages, and the operating system you tested with.
+
+  Issues without a link to a public repository or ZIP file will likely go ignored.
+  Being able to see your actual files is necessary to troubleshoot, as most 
+  issues stem from invalid/missing YAML Front Matter, a mis-configured _config.sys 
+  file, or problematic site content. 
+-->
+
+- So Simple version:
+- Ruby gem or remote theme version:
+- Jekyll version:
+- Git repository URL:
+- GitHub Pages hosted (if yes provide URL to site):
+- Operating system:
+
+## Expected behavior
+
+<!--
+  What is it you expected to happen? This should be a description of how the
+  functionality you tried to use is supposed to work.
+-->
+
+## Steps to reproduce the behavior
+
+<!--
+  Describe the steps you took for this problem to exist. Such as: you installed
+  the theme, customized _config.yml, added your own posts, and started up a 
+  Jekyll server locally.
+
+  If an error occurred on GitHub Pages when pushing, please test a local version
+  following these setup instructions: 
+  https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/
+
+  Then provide a complete log by running `bundle exec jekyll build --trace --verbose` 
+  and include this output in the filed issue.
+
+  Screenshots can also be included if they help illustrate a behavior.
+-->
+
+## Other
+
+<!--
+  NOTE: Please provide a code repository, gist, code snippet, sample files, 
+  screenshots, or anything else you think will aid in reproducing the issue.
+-->

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,16 @@
+---
+name: "Documentation"
+about: "Found a typo or something that needs clarification?"
+---
+
+<!-- Thanks for taking the time to open an issue and help make the docs better -->
+
+## Motivation
+
+<!-- Why should we update our docs? -->
+
+<!-- What should we do instead? -->
+
+## Suggestion
+
+<!-- What should we do instead? -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+<!--
+  Thanks for creating a Pull Request! Before you submit, please make sure
+  you've done the following:
+
+  - Read the contributing document at https://github.com/mmistakes/so-simple-theme#contributing
+-->
+
+<!--
+  Choose one of the following by uncommenting it:
+-->
+
+<!-- This is a bug fix. -->
+<!-- This is an enhancement or feature. -->
+<!-- This is a documentation change. -->
+
+## Summary
+
+<!--
+  Provide a description of what your pull request changes.
+-->
+
+## Context
+
+<!--
+  Is this related to any GitHub issue(s)?
+-->

.gitignore

@@ -0,0 +1,14 @@
+_asset_bundler_cache
+_site
+.bundle
+.DS_Store
+.jekyll-cache
+.jekyll-metadata
+.sass-cache
+*.gem
+*.sublime-project
+*.sublime-workspace
+codekit-config.json
+Gemfile.lock
+node_modules
+npm-debug.log*