[FEAT] go back to jekyll from gatsby

.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 = false
+
+[*.md]
+trim_trailing_whitespace = false

.gitattributes

@@ -0,0 +1,10 @@
+assets/fonts/*                  linguist-vendored
+assets/js/main.min.js           linguist-vendored
+assets/js/lunr/*                linguist-vendored
+assets/js/plugins/*             linguist-vendored
+assets/js/vendor/*              linguist-vendored
+_sass/minimal-mistakes/vendor/* linguist-vendored
+CHANGELOG.md                    text merge=union
+docs/_docs/18-history.md        text merge=union
+
+*.md                            text

.github/CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# Contributing
+
+Found a typo in the documentation or interested in [fixing a bug](https://github.com/mmistakes/minimal-mistakes/issues)? Then by all means [submit an issue](https://github.com/mmistakes/minimal-mistakes/issues/new) or [pull request](https://help.github.com/articles/using-pull-requests/). If this is your first pull request, it may be helpful to read up on the [GitHub Flow](https://guides.github.com/introduction/flow/) first.
+
+For help with using the theme or general Jekyll support questions, please use the [Jekyll Talk forums](https://talk.jekyllrb.com/).
+
+Minimal Mistakes has been designed as a base for you to customize and fit your 
+site's unique needs. Please keep this in mind when requesting features and/or 
+submitting pull requests. If it's not something that most people will use, I 
+probably won't consider it. When in doubt ask.
+
+This goes for author sidebar links and "share button" additions -- I have no 
+intention of merging in every possibly option, the essentials are there to get 
+you started :smile:.
+
+## 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`) and describe the feature or fix.
+3. Open a pull request on GitHub.

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: mmistakes
+custom: ['https://www.paypal.me/mmistakes']

.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 Minimal Mistakes 
+    installed by running `bundle update`.
+  - Thoroughly read the theme's documentation at
+    https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/
+  - Search all issues at https://github.com/mmistakes/minimal-mistakes/issues 
+    for solutions and to avoid duplication.
+  - Ask for help at http://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. 
+-->
+
+- Minimal Mistakes 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/minimal-mistakes#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)?
+-->

.github/stale.yml

@@ -0,0 +1,22 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 30
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - "Status: Accepted"
+  - "Status: Under Consideration"
+  - "Status: Review Needed"
+# Label to use when marking an issue as stale
+staleLabel: "Status: Stale"
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: |
+  This issue has been automatically marked as stale because it has not had recent activity.
+
+  If this is a **bug** and you can still reproduce this error on the `master` branch, please reply with any additional information you have about it in order to keep the issue open.
+
+  If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
+
+  This issue will automatically be closed in 7 days if no further activity occurs. Thank you for all your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

.github/workflows/stale.yml

@@ -0,0 +1,27 @@
+name: "Close stale issues and PRs"
+on:
+  schedule:
+    - cron: "30 1 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v3
+        with:
+          stale-issue-message: |
+            This issue has been automatically marked as stale because it has not had recent activity.
+
+            If this is a **bug** and you can still reproduce this error on the `master` branch, please reply with any additional information you have about it in order to keep the issue open.
+
+            If this is a feature request, please [add as an Idea under discussions](https://github.com/mmistakes/minimal-mistakes/discussions/categories/ideas) and elaborate on why it is core to this project and why you feel more than 80% of users would find it beneficial.
+
+            This issue will automatically be closed in 7 days if no further activity occurs. Thank you for all your contributions.
+          stale-pr-message: |
+            This pull request has been automatically marked as stale because it has not had recent activity.
+
+            This pull request will automatically be closed in 7 days if no further activity occurs. Thank you for all your contributions.
+          stale-issue-label: "Status: Stale"
+          exempt-issue-labels: "Status: Accepted,Status: Under Consideration,Status: Review Needed,Status: In Progress"
+          stale-pr-label: "Status: Stale"
+          exempt-pr-labels: "Status: Accepted,Status: Under Consideration,Status: Review Needed,Status: In Progress"

.gitignore

@@ -0,0 +1,29 @@
+# Vim
+*~
+*.sw[p_]
+
+# Sublime Text
+*.sublime-project
+*.sublime-workspace
+
+# Ruby Gem
+*.gem
+.bundle
+Gemfile.lock
+**/vendor/bundle
+
+# Node.js and NPM
+node_modules
+npm-debug.log*
+package-lock.json
+codekit-config.json
+
+# macOS
+.DS_Store
+
+# Jekyll generated files
+.jekyll-cache
+.jekyll-metadata
+.sass-cache
+_asset_bundler_cache
+_site

.travis.yml

@@ -0,0 +1,11 @@
+language: ruby
+cache: bundler
+gemfile: docs/Gemfile
+script:
+  - bundle exec jekyll algolia --source docs --destination docs/_site --config docs/_config.yml
+branches:
+  only:
+    # Change this to gh-pages if you're deploying using the gh-pages branch
+    - master
+rvm:
+ - 2.4