diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
index 5aecfc6f..47422e09 100644
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -1,18 +1,21 @@
-name: deploy
 on:
   pull_request:
   push:
-    branches: [real_master]
+    branches: [main]
   schedule:
     - cron: '30 8 * * *'
 
+permissions:
+  contents: write
+
 jobs:
-  build:
-    name: pr
+  pr:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v1
-    - uses: actions/setup-python@v1
+    - uses: actions/checkout@v3
+    - uses: actions/setup-python@v4
+      with:
+        python-version: 3.x
     - run: pip install virtualenv
     - run: make
     - run: make push
diff --git a/.gitignore b/.gitignore
index 2deee430..8658b840 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,8 +1,4 @@
 *.html
 *.pyc
-*.swp
-/.mypy_cache
-/all-hooks.json
 /build
 /node_modules
-/venv
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index db44772d..84487e17 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -1,49 +1,43 @@
 repos:
 -   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v2.4.0
+    rev: v6.0.0
     hooks:
     -   id: trailing-whitespace
     -   id: end-of-file-fixer
     -   id: check-yaml
     -   id: debug-statements
--   repo: https://gitlab.com/pycqa/flake8
-    rev: 3.7.9
-    hooks:
-    -   id: flake8
--   repo: https://github.com/pre-commit/mirrors-autopep8
-    rev: v1.4.4
-    hooks:
-    -   id: autopep8
--   repo: https://github.com/asottile/reorder_python_imports
-    rev: v1.8.0
+    -   id: double-quote-string-fixer
+    -   id: name-tests-test
+    -   id: requirements-txt-fixer
+-   repo: https://github.com/asottile/reorder-python-imports
+    rev: v3.16.0
     hooks:
     -   id: reorder-python-imports
+        args: [--py310-plus, --add-import, 'from __future__ import annotations']
+    -   id: reorder-python-imports
+-   repo: https://github.com/asottile/add-trailing-comma
+    rev: v4.0.0
+    hooks:
+    -   id: add-trailing-comma
 -   repo: https://github.com/asottile/pyupgrade
-    rev: v1.25.2
+    rev: v3.21.2
     hooks:
     -   id: pyupgrade
-        args: [--py36-plus]
-        exclude: ^install-local.py$
+        args: [--py310-plus]
+-   repo: https://github.com/hhatto/autopep8
+    rev: v2.3.2
+    hooks:
+    -   id: autopep8
+-   repo: https://github.com/PyCQA/flake8
+    rev: 7.3.0
+    hooks:
+    -   id: flake8
 -   repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v0.761
+    rev: v1.19.1
     hooks:
     -   id: mypy
-        exclude: ^install-local.py$
--   repo: https://github.com/pre-commit/mirrors-eslint
-    rev: v7.0.0-alpha.3
-    hooks:
-    -   id: eslint
-        args: [--fix]
--   repo: local
-    hooks:
-    -   id: scss-lint
-        name: scss-lint
-        entry: scss-lint
-        types: [scss]
-        language: ruby
-        additional_dependencies: ['scss_lint:0.57.0']
-    -   id: no-github-dot-git
-        name: No need for .git for github/gitlab urls
-        entry: '(github|gitlab).*\.git'
-        files: all-repos.yaml
-        language: pygrep
+-   repo: https://github.com/biomejs/pre-commit
+    rev: v2.3.10
+    hooks:
+    -   id: biome-check
+        additional_dependencies: ["@biomejs/biome@1.8.1"]
diff --git a/Makefile b/Makefile
index 31b669d1..81533eda 100644
--- a/Makefile
+++ b/Makefile
@@ -1,18 +1,13 @@
-# To build scss continuously I use `watch -n 0.1 make build/main.css`
-
-all: install-hooks build/main.css all-hooks.json index.html hooks.html
+all: install-hooks build/main_bs5.css index.html hooks.html
 
 .PHONY: install-hooks
 install-hooks: venv
 	venv/bin/pre-commit install
 
-build/main.css: venv node_modules build scss/main.scss scss/_variables.scss
-	venv/bin/pysassc -s compressed scss/main.scss build/main.css
-
-all-hooks.json: venv make_all_hooks.py all-repos.yaml
-	venv/bin/python make_all_hooks.py
+build/main_bs5.css: node_modules build scss/main_bs5.scss scss/_variables.scss
+	node_modules/.bin/sass --style=compressed --load-path=. scss/main_bs5.scss build/main_bs5.css
 
-index.html hooks.html: venv all-hooks.json base.mako index.mako hooks.mako make_templates.py
+index.html hooks.html: venv base.mako index.mako hooks.mako make_templates.py template_lib.py sections/*.md
 	venv/bin/python make_templates.py
 
 venv: requirements-dev.txt Makefile
@@ -29,14 +24,11 @@ node_modules: package.json
 
 push: venv
 	venv/bin/markdown-to-presentation push \
-		--master-branch real_master \
-		--pages-branch master \
 		.nojekyll README.md CNAME \
-		build assets node_modules *.html *.png *.svg favicon.ico \
-		all-hooks.json install-local.py
+		build assets *.html *.png *.svg favicon.ico
 
 clean:
-	rm -rf venv build node_modules *.html all-hooks.json
+	rm -rf venv build node_modules *.html
 
 build:
 	mkdir -p build
diff --git a/README.md b/README.md
index 9999ed5d..c311257b 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
-pre-commit.github.io
-====================
+pre-commit.com
+==============
 
-[![Build Status](https://dev.azure.com/asottile/asottile/_apis/build/status/pre-commit.pre-commit.github.io?branchName=real_master)](https://dev.azure.com/asottile/asottile/_build/latest?definitionId=58&branchName=real_master)
-[![Build Status](https://github.com/pre-commit/pre-commit.github.io/workflows/deploy/badge.svg)](https://github.com/pre-commit/pre-commit.github.io/actions)
+[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/pre-commit/pre-commit.com/main.svg)](https://results.pre-commit.ci/latest/github/pre-commit/pre-commit.com/main)
+[![Build Status](https://github.com/pre-commit/pre-commit.com/actions/workflows/deploy.yml/badge.svg)](https://github.com/pre-commit/pre-commit.com/actions)
 
 This powers https://pre-commit.com
diff --git a/all-repos.yaml b/all-repos.yaml
deleted file mode 100644
index 010bab9e..00000000
--- a/all-repos.yaml
+++ /dev/null
@@ -1,132 +0,0 @@
-# This file is used to generate all-hooks.json
-- https://github.com/pre-commit/pre-commit-hooks
-- https://github.com/pre-commit/mirrors-autopep8
-- https://github.com/pre-commit/mirrors-coffeelint
-- https://github.com/pre-commit/mirrors-csslint
-- https://github.com/pre-commit/mirrors-eslint
-- https://github.com/pre-commit/mirrors-fixmyjs
-- https://github.com/pre-commit/mirrors-isort
-- https://github.com/pre-commit/mirrors-jshint
-- https://github.com/pre-commit/mirrors-mypy
-- https://github.com/pre-commit/mirrors-puppet-lint
-- https://github.com/pre-commit/mirrors-ruby-lint
-- https://github.com/pre-commit/mirrors-scss-lint
-- https://github.com/pre-commit/mirrors-yapf
-- https://github.com/pre-commit/pygrep-hooks
-- https://github.com/FalconSocial/pre-commit-mirrors-pep257
-- https://github.com/FalconSocial/pre-commit-python-sorter
-- https://github.com/guykisel/pre-commit-robotframework-tidy
-- https://github.com/guykisel/prospector-mirror
-- https://github.com/asottile/add-trailing-comma
-- https://github.com/asottile/pyupgrade
-- https://github.com/asottile/reorder_python_imports
-- https://github.com/asottile/yesqa
-- https://github.com/asottile/seed-isort-config
-- https://github.com/asottile/blacken-docs
-- https://github.com/asottile/dead
-- https://github.com/asottile/setup-cfg-fmt
-- https://github.com/asottile/cheetah_lint
-- https://github.com/digitalpulp/pre-commit-php
-- https://github.com/elidupuis/mirrors-jscs
-- https://github.com/elidupuis/mirrors-sass-lint
-- https://github.com/jumanjihouse/pre-commit-hooks
-- https://github.com/jumanjihouse/pre-commit-hook-yamlfmt
-- https://github.com/Lucas-C/pre-commit-hooks
-- https://github.com/Lucas-C/pre-commit-hooks-go
-- https://github.com/Lucas-C/pre-commit-hooks-java
-- https://github.com/Lucas-C/pre-commit-hooks-lxml
-- https://github.com/Lucas-C/pre-commit-hooks-markup
-- https://github.com/Lucas-C/pre-commit-hooks-nodejs
-- https://github.com/Lucas-C/pre-commit-hooks-safety
-- https://github.com/chriskuehl/puppet-pre-commit-hooks
-- https://github.com/golangci/golangci-lint
-- https://github.com/Bahjat/pre-commit-golang
-- https://github.com/dnephin/pre-commit-golang
-- https://github.com/troian/pre-commit-golang
-- https://github.com/jstewmon/check-swagger
-- https://github.com/detailyang/pre-commit-shell
-- https://github.com/bemeurer/beautysh
-- https://github.com/antonbabenko/pre-commit-terraform
-- https://github.com/ansible/ansible-lint
-- https://github.com/doublify/pre-commit-clang-format
-- https://github.com/doublify/pre-commit-go
-- https://github.com/doublify/pre-commit-hindent
-- https://github.com/doublify/pre-commit-isort
-- https://github.com/doublify/pre-commit-rust
-- https://github.com/kintoandar/pre-commit
-- https://github.com/awebdeveloper/pre-commit-stylelint
-- https://github.com/awebdeveloper/pre-commit-tslint
-- https://github.com/awebdeveloper/pre-commit-prettier
-- https://github.com/prettier/prettier
-- https://github.com/adrienverge/yamllint
-- https://github.com/thlorenz/doctoc
-- https://github.com/noahsark769/xcodeproj-sort-pre-commit-hook
-- https://github.com/jorisroovers/gitlint
-- https://github.com/psf/black
-- https://github.com/IamTheFij/ansible-pre-commit
-- https://github.com/IamTheFij/docker-pre-commit
-- https://github.com/mattlqx/pre-commit-ruby
-- https://github.com/mattlqx/pre-commit-sign
-- https://github.com/mattlqx/pre-commit-search-and-replace
-- https://github.com/openstack-dev/bashate
-- https://github.com/pryorda/dockerfilelint-precommit-hooks
-- https://github.com/alessandrojcm/commitlint-pre-commit-hook
-- https://github.com/henryykt/pre-commit-perl
-- https://github.com/juancarlospaco/pre-commit-nim
-- https://github.com/awslabs/cfn-python-lint
-- https://github.com/thoughtworks/talisman
-- https://gitlab.com/PyCQA/flake8
-- https://github.com/PyCQA/bandit
-- https://github.com/PyCQA/pydocstyle
-- https://github.com/PyCQA/pylint
-- https://github.com/miki725/importanize
-- https://github.com/motet-a/jinjalint
-- https://github.com/milin/giticket
-- https://github.com/sqlalchemyorg/zimports
-- https://github.com/peterdemin/pip-compile-multi
-- https://github.com/homebysix/pre-commit-macadmin
-- https://github.com/fortman/pre-commit-prometheus
-- https://github.com/syntaqx/git-hooks
-- https://github.com/Calinou/pre-commit-luacheck
-- https://github.com/belminf/pre-commit-chef
-- https://github.com/timothycrosley/isort
-- https://github.com/pocc/pre-commit-hooks
-- https://github.com/dwightgunning/pre-commit-nglint
-- https://github.com/codespell-project/codespell
-- https://gitlab.com/smop/pre-commit-hooks
-- https://github.com/seddonym/import-linter
-- https://github.com/marco-c/taskcluster_yml_validator
-- https://github.com/myint/docformatter
-- https://github.com/lorenzwalthert/precommit
-- https://github.com/FelixSeptem/pre-commit-golang
-- https://gitlab.com/daverona/pre-commit-cpp
-- https://github.com/codingjoe/relint
-- https://github.com/nix-community/nixpkgs-fmt
-- https://github.com/d6e/beancount-check
-- https://github.com/iconmaster5326/cmake-format-pre-commit-hook
-- https://github.com/thg-consulting/inspectortiger
-- https://gitlab.com/iamlikeme/nbhooks
-- https://github.com/Kuniwak/vint
-- https://github.com/eschulte/lisp-format
-- https://github.com/shellcheck-py/shellcheck-py
-- https://github.com/APIDevTools/swagger-cli
-- https://github.com/kynan/nbstripout
-- https://gitlab.com/devopshq/gitlab-ci-linter
-- https://github.com/bmorcos/pre-commit-hooks-cpp
-- https://github.com/igorshubovych/markdownlint-cli
-- https://github.com/TekWizely/pre-commit-golang
-- https://github.com/markdownlint/markdownlint
-- https://github.com/jguttman94/pre-commit-gradle
-- https://github.com/Yelp/detect-secrets
-- https://github.com/dmitri-lerko/pre-commit-docker-kustomize
-- https://github.com/perltidy/perltidy
-- https://github.com/talos-systems/conform
-- https://github.com/twu/skjold
-- https://github.com/woile/commitizen
-- https://github.com/gherynos/pre-commit-java
-- https://github.com/JamesWoolfenden/pre-commit
-- https://github.com/lietu/go-pre-commit
-- https://github.com/macisamuele/language-formatters-pre-commit-hooks
-- https://github.com/jlebar/pre-commit-hooks
-- https://github.com/jazzband/pip-tools
-- https://github.com/pappasam/toml-sort
diff --git a/assets/copyable.js b/assets/copyable.js
index 8aba102f..7d18e25b 100644
--- a/assets/copyable.js
+++ b/assets/copyable.js
@@ -1,6 +1,8 @@
-(function () {
+'use strict';
+
+(() => {
     function copyTextToClipboard(text) {
-        var textArea = document.createElement('textarea');
+        const textArea = document.createElement('textarea');
         textArea.value = text;
         textArea.style.position = 'fixed';
         textArea.style.left = '-1';
@@ -11,17 +13,15 @@
         document.execCommand('copy');
         document.body.removeChild(textArea);
     }
-    var codeBlockElements = document.getElementsByClassName('copyable');
-    for (var i = 0; i < codeBlockElements.length; i++) {
-        var block = codeBlockElements[i];
-        var copyIcon = new Image(16, 16);
+    for (const block of document.getElementsByClassName('copyable')) {
+        const copyIcon = new Image(16, 16);
         copyIcon.setAttribute('src', './assets/copy-icon.svg');
         copyIcon.setAttribute('alt', 'copy');
         copyIcon.setAttribute('title', 'copy to clipboard');
         block.insertBefore(copyIcon, block.children[0]);
-        copyIcon.addEventListener('click', function(block) {
-            var text = block.getElementsByTagName('pre')[0].innerText;
+        copyIcon.addEventListener('click', () => {
+            const text = block.getElementsByTagName('pre')[0].innerText;
             copyTextToClipboard(text);
-        }.bind(null, block));
+        });
     }
 })();
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
deleted file mode 100644
index ed46fb18..00000000
--- a/azure-pipelines.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-trigger:
-  branches:
-    include: [real_master, test-me-*]
-  tags:
-    include: ['*']
-
-resources:
-  repositories:
-    - repository: asottile
-      type: github
-      endpoint: github
-      name: asottile/azure-pipeline-templates
-      ref: refs/tags/v1.0.0
-
-jobs:
-- template: job--pre-commit.yml@asottile
diff --git a/base.mako b/base.mako
index 640d2add..77ba61f4 100644
--- a/base.mako
+++ b/base.mako
@@ -2,69 +2,91 @@
 <!DOCTYPE html>
 <html>
     <head>
-        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-        <link href="//fonts.googleapis.com/css?family=Source+Sans+Pro:400,700" rel="stylesheet" type="text/css">
-        <link rel="stylesheet" type="text/css" href="build/main.css">
-        <link rel="icon" href="favicon.ico">
-        <meta name="viewport" content="width=device-width, initial-scale=1">
+        <meta charset="utf-8">
+        <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
+
+        <link rel="shortcut icon" type="image/x-icon" href="favicon.ico">
+
+        <link rel="stylesheet" href="build/main_bs5.css">
+
         <title>pre-commit</title>
     </head>
-    <body class="page-${template_name}" data-spy="scroll" data-target=".pc-sidebar">
-        <header class="navbar navbar-default pc-nav" role="banner">
-            <div class="container">
-                <div class="navbar-header">
-                    <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".pc-navbar-collapse">
-                        <span class="sr-only">Toggle navigtaion</span>
-                        <span class="icon-bar"></span>
-                        <span class="icon-bar"></span>
-                        <span class="icon-bar"></span>
-                    </button>
-                    <a href="/" class="navbar-brand pc-navbar-brand">
-                        <i class="logo"></i>
-                    </a>
-                </div>
-                <nav class="navbar-collapse pc-navbar pc-navbar-collapse collapse" role="navigation">
-                    <ul class="nav navbar-nav">
-                        <li><a href="/">Documentation</a></li>
-                        <li><a href="hooks.html">Supported hooks</a></li>
-                        <li><a href="https://github.com/pre-commit/demo-repo#readme">Demo</a></li>
+    <body data-bs-spy="scroll" data-bs-target="#content-navigation">
+        <nav class="navbar navbar-expand-md navbar-dark bg-primary">
+            <div class="container-md">
+                <a class="navbar-brand" href="/">
+                    <img src="logo.svg" width="55" height="55" alt="" loading="lazy">
+                </a>
+
+                <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbar" aria-controls="navbar" aria-expanded="false" >
+                    <span class="navbar-toggler-icon"></span>
+                </button>
+
+                <div class="collapse navbar-collapse" id="navbar">
+                    <ul class="navbar-nav">
+                        <li class="nav-item">
+                            <a class="nav-link${' active' if template_name == 'index' else ''}" href="index.html">Documentation</a>
+                        </li>
+                        <li class="nav-item">
+                            <a class="nav-link${' active' if template_name == 'hooks' else ''}" href="hooks.html">Supported hooks</a>
+                        </li>
+                        <li class="nav-item">
+                            <a class="nav-link" href="https://github.com/pre-commit/demo-repo#readme">Demo</a>
+                        </li>
                     </ul>
-                    <ul class="nav navbar-nav navbar-right">
-                        <li><a href="https://github.com/pre-commit/pre-commit" class="btn btn-default">Download on GitHub</a></li>
+
+                    <ul class="navbar-nav ms-auto">
+                        <li class="nav-item">
+                            <a href="https://github.com/pre-commit/pre-commit" role="button" class="btn btn-outline-info my-2 my-sm-0">Download on GitHub</a>
+                        </li>
                     </ul>
-                </nav>
+                </div>
+            </div>
+        </nav>
+
+        % if template_name == 'index':
+        <header class="bg-light">
+            <div class="container-md py-4 py-lg-0">
+                <div class="d-flex justify-content-between align-items-center">
+                    <div>
+                        <h1 class="display-5 pb-3 text-secondary fw-bold">pre-commit</h1>
+                        <p class="lead text-white">
+                            A framework for managing and maintaining multi-language <span class="text-nowrap">pre-commit</span> hooks.
+                        </p>
+                        <div class="mb-3">
+                            <a href="https://github.com/pre-commit/pre-commit/actions/workflows/main.yml">
+                                <img src="https://github.com/pre-commit/pre-commit/actions/workflows/main.yml/badge.svg" alt="build status" style="max-width:100%;">
+                            </a>
+                            <a href="https://results.pre-commit.ci/latest/github/pre-commit/pre-commit/main">
+                                <img src="https://results.pre-commit.ci/badge/github/pre-commit/pre-commit/main.svg" alt="pre-commit.ci status" style="max-width:100%;">
+                            </a>
+                        </div>
+                        <div>
+                            ## https://buttons.github.io/
+                            <a class="github-button" href="https://github.com/pre-commit/pre-commit" data-show-count="true" aria-label="Star pre-commit/pre-commit on GitHub">Star</a>
+                            <script async defer src="https://buttons.github.io/buttons.js"></script>
+                        </div>
+                    </div>
+                    <img src="logo-top-shelf.png" alt="pre-commit logo" class="d-none d-lg-block" />
+                </div>
             </div>
         </header>
-        <div class="top-shelf">
-            <div class="container">
-                <img class="pc-logo-top-shelf hidden-xs hidden-sm" src="logo-top-shelf.png">
-                <h1>
-                    <a href="https://github.com/pre-commit/pre-commit">
-                        pre-commit
-                    </a>
-                </h1>
-                <p>A framework for managing and maintaining multi-language <span class="nowrap">pre-commit</span> hooks.</p>
-           <p><a href="https://dev.azure.com/asottile/asottile/_build/latest?definitionId=21&branchName=master"><img src="https://dev.azure.com/asottile/asottile/_apis/build/status/pre-commit.pre-commit?branchName=master" alt="Build Status" style="max-width:100%;"></a>
-<a href="https://dev.azure.com/asottile/asottile/_build/latest?definitionId=21&branchName=master"><img src="https://img.shields.io/azure-devops/coverage/asottile/asottile/21/master.svg" alt="Azure DevOps Coverage" style="max-width:100%;"></a>
-<a href="https://github.com/pre-commit/pre-commit"><img src="https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white" alt="pre-commit" style="max-width:100%;"></a></p>
-            <p><iframe src="https://ghbtns.com/github-btn.html?user=pre-commit&amp;repo=pre-commit&amp;type=watch&amp;count=true"
-  allowtransparency="true" frameborder="0" scrolling="0" width="104px" height="20"></iframe>
-<a href="https://twitter.com/share" class="twitter-share-button" data-url="https://pre-commit.com" data-text="pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.">Tweet</a>
-<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></p>
-        </div>
-        </div>
-        <div class="container pc-main-content">
+        % endif
+
+        <main class="container-md my-4">
             ${self.body()}
-        </div>
-        <footer class="pc-footer"><div class="container"></div></footer>
-        <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script>
-        <script src="node_modules/bootstrap-sass/assets/javascripts/bootstrap.min.js"></script>
+        </main>
+
+        <footer class="navbar navbar-expand navbar-dark bg-primary">
+            <div class="container-md">&nbsp;</div>
+        </footer>
+
+        <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/js/bootstrap.bundle.min.js" integrity="sha384-MrcW6ZMFYlzcLA8Nl+NtUVF0sA7MsXsP1UyJoMp4YLEuNSfAP+JcXn/tWtIaxVXM" crossorigin="anonymous"></script>
         <script>
             (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
             (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
             m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
             })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
-
             ga('create', 'UA-104682927-1', 'auto');
             ga('send', 'pageview');
         </script>
diff --git a/biome.json b/biome.json
new file mode 100644
index 00000000..03e2df98
--- /dev/null
+++ b/biome.json
@@ -0,0 +1,24 @@
+{
+    "$schema": "https://biomejs.dev/schemas/1.4.0/schema.json",
+    "organizeImports": {
+        "enabled": false
+    },
+    "formatter": {
+        "indentStyle": "space",
+        "indentWidth": 4
+    },
+    "javascript": {
+        "formatter": {
+            "quoteStyle": "single"
+        }
+    },
+    "linter": {
+        "enabled": true,
+        "rules": {
+            "recommended": true,
+            "suspicious": {
+                "noRedundantUseStrict": "off"
+            }
+        }
+    }
+}
diff --git a/hooks.mako b/hooks.mako
index 5c2f725d..820178a6 100644
--- a/hooks.mako
+++ b/hooks.mako
@@ -3,30 +3,4 @@
 
 <div class="page-header"><h1>Supported hooks</h1></div>
 
-<p>
-To add to this list, fork <a href="https://github.com/pre-commit/pre-commit.github.io">this repository</a>.
-</p>
-
-<p>
-Also available in <a href="/all-hooks.json">json</a>.
-</p>
-
-% for repository, hooks in all_hooks.items():
-    <h3>
-        <a href="${repository}" target="_blank">
-            ${repository.replace('https://', '')}
-        </a>
-    </h3>
-    <ul>
-        % for hook_dict in hooks:
-            <li>
-                <code>${hook_dict['id']}</code>
-                % if 'description' in hook_dict:
-                    - ${hook_dict['description']}
-                % elif hook_dict['name'].lower() != hook_dict['id'].lower():
-                    - ${hook_dict['name']}
-                % endif
-            </li>
-        % endfor
-    </ul>
-% endfor
+${body}
diff --git a/index.mako b/index.mako
index 986de677..0619b1b5 100644
--- a/index.mako
+++ b/index.mako
@@ -4,1691 +4,19 @@ from template_lib import md
 %>
 <%inherit file="base.mako" />
 <div class="row">
-    <div class="col-sm-3 hidden-xs pc-sidebar">
-        <ul class="nav nav-pills nav-stacked pc-sidenav" data-spy="affix" data-offset-top="400">
-            <li class="active"><a href="#intro">Introduction</a></li>
-            <li><a href="#install">Installation</a></li>
-            <li><a href="#plugins">Adding plugins</a></li>
-            <li><a href="#usage">Usage</a></li>
-            <li><a href="#new-hooks">Creating new hooks</a></li>
-            <li><a href="#cli">Command line interface</a></li>
-            <li><a href="#advanced">Advanced features</a></li>
-            <li><a href="#contributing">Contributing</a></li>
-        </ul>
+    <div class="col-sm-3 d-none d-lg-block">
+        <nav class="nav flex-column nav-pills sticky-top" aria-orientation="vertical" id="content-navigation">
+          <a class="nav-link active" href="#intro" role="tab">Introduction</a>
+          <a class="nav-link" href="#install" role="tab">Installation</a>
+          <a class="nav-link" href="#plugins" role="tab">Adding plugins</a>
+          <a class="nav-link" href="#usage" role="tab">Usage</a>
+          <a class="nav-link" href="#new-hooks" role="tab">Creating new hooks</a>
+          <a class="nav-link" href="#cli" role="tab">Command line interface</a>
+          <a class="nav-link" href="#advanced" role="tab">Advanced features</a>
+          <a class="nav-link" href="#contributing" role="tab">Contributing</a>
+        </nav>
     </div>
-    <div class="col-sm-9">
-        <div id="intro">
-            <div class="page-header">${md('# Introduction')}</div>
-${md('''
-Git hook scripts are useful for identifying simple issues before submission to
-code review.  We run our hooks on every commit to automatically point out
-issues in code such as missing semicolons, trailing whitespace, and debug
-statements.  By pointing these issues out before code review, this allows a
-code reviewer to focus on the architecture of a change while not wasting time
-with trivial style nitpicks.
-
-As we created more libraries and projects we recognized that sharing our
-pre-commit hooks across projects is painful. We copied and pasted unwieldy
-bash scripts from project to project and had to manually change the hooks to
-work for different project structures.
-
-We believe that you should always use the best industry standard linters.
-Some of the best linters are written in languages that you do not use in your
-project or have installed on your machine. For example scss-lint is a linter
-for SCSS written in Ruby. If you’re writing a project in node you should be
-able to use scss-lint as a pre-commit hook without adding a Gemfile to your
-project or understanding how to get scss-lint installed.
-
-We built pre-commit to solve our hook issues. It is a multi-language package
-manager for pre-commit hooks. You specify a list of hooks you want and
-pre-commit manages the installation and execution of any hook written in any
-language before every commit. pre-commit is specifically designed to not
-require root access. If one of your developers doesn’t have node installed
-but modifies a JavaScript file, pre-commit automatically handles downloading
-and building node to run eslint without root.
-''')}
-        </div>
-        <div id="install">
-            <div class="page-header">${md('# Installation')}</div>
-${md('''
-Before you can run hooks, you need to have the pre-commit package manager
-installed.
-
-Using pip:
-
-```bash
-pip install pre-commit
-```
-
-Non-administrative installation:
-
-- _to upgrade: run again, to uninstall: pass `uninstall` to python_
-- _does not work on platforms without symlink support (windows)_
-
-
-```bash
-curl https://pre-commit.com/install-local.py | python -
-```
-
-In a python project, add the following to your requirements.txt (or
-requirements-dev.txt):
-
-```
-pre-commit
-```
-
-Using [homebrew](https://brew.sh):
-
-```bash
-brew install pre-commit
-```
-
-Using [conda](https://conda.io) (via [conda-forge](https://conda-forge.org)):
-
-```bash
-conda install -c conda-forge pre-commit
-```
-
-## Quick start
-
-### 1. Install pre-commit
-
-- follow the [install](#install) instructions above
-- `pre-commit --version` should show you what version you're using
-
-```cmd
-pre-commit --version
-```
-
-### 2. Add a pre-commit configuration
-
-- create a file named `.pre-commit-config.yaml`
-- you can generate a very basic configuration using
-  [`pre-commit sample-config`](#pre-commit-sample-config)
-- the full set of options for the configuration are listed [below](#plugins)
-- this example uses a formatter for python code, however `pre-commit` works for
-  any programming language
-- other [supported hooks](hooks.html) are available
-
-```yaml
-repos:
--   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v2.3.0
-    hooks:
-    -   id: check-yaml
-    -   id: end-of-file-fixer
-    -   id: trailing-whitespace
--   repo: https://github.com/psf/black
-    rev: 19.3b0
-    hooks:
-    -   id: black
-```
-
-### 3. Install the git hook scripts
-
-- run `pre-commit install` to set up the git hook scripts
-
-```console
-$ pre-commit install
-pre-commit installed at .git/hooks/pre-commit
-```
-
-- now `pre-commit` will run automatically on `git commit`!
-
-### 4. (optional) Run against all the files
-
-- it's usually a good idea to run the hooks against all of the files when adding
-  new hooks (usually `pre-commit` will only run on the changed files during
-  git hooks)
-
-```pre-commit
-$ pre-commit run --all-files
-[INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks.
-[INFO] Initializing environment for https://github.com/psf/black.
-[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
-[INFO] Once installed this environment will be reused.
-[INFO] This may take a few minutes...
-[INFO] Installing environment for https://github.com/psf/black.
-[INFO] Once installed this environment will be reused.
-[INFO] This may take a few minutes...
-Check Yaml...............................................................Passed
-Fix End of Files.........................................................Passed
-Trim Trailing Whitespace.................................................Failed
-- hook id: trailing-whitespace
-- exit code: 1
-
-Files were modified by this hook. Additional output:
-
-Fixing sample.py
-
-black....................................................................Passed
-```
-
-- oops! looks like I had some trailing whitespace
-- consider running that in [CI](#usage-in-continuous-integration) too
-
-''')}
-        </div>
-
-        <div id="plugins">
-            <div class="page-header">${md('# Adding pre-commit plugins to your project')}</div>
-${md('''
-Once you have pre-commit installed, adding pre-commit plugins to your project
-is done with the `.pre-commit-config.yaml` configuration file.
-
-Add a file called `.pre-commit-config.yaml` to the root of your project. The
-pre-commit config file describes what repositories and hooks are installed.
-
-## .pre-commit-config.yaml - top level
-
-_new in 1.0.0_: The default configuration file top-level was changed from a
-list to a map.  If you're using an old version of pre-commit, the top-level
-list is the same as the value of [`repos`](#pre-commit-configyaml---repos).
-If you'd like to migrate to the new configuration format, run
-[`pre-commit migrate-config`](#pre-commit-migrate-config) to automatically
-migrate your configuration.
-
-```table
-=r=
-    =c= `repos`
-    =c= A list of [repository mappings](#pre-commit-configyaml---repos).
-=r=
-    =c= `default_language_version`
-    =c= (optional: default `{}`) a mapping from language to the default
-        `language_version` that should be used for that language.  This will
-        only override individual hooks that do not set `language_version`.
-
-        For example to use `python3.7` for `language: python` hooks:
-
-        ```yaml
-        default_language_version:
-            python: python3.7
-        ```
-
-        _new in 1.14.0_
-=r=
-    =c= `default_stages`
-    =c= (optional: default (all stages)) a configuration-wide default for
-        the `stages` property of hooks.  This will only override individual
-        hooks that do not set `stages`.
-
-        For example:
-
-        ```yaml
-        default_stages: [commit, push]
-        ```
-
-        _new in 1.14.0_
-=r=
-    =c= `files`
-    =c= (optional: default `''`) global file include pattern.  _new in 1.21.0_.
-=r=
-    =c= `exclude`
-    =c= (optional: default `^$`) global file exclude pattern.  _new in 1.1.0_.
-=r=
-    =c= `fail_fast`
-    =c= (optional: default `false`) set to `true` to have pre-commit stop
-        running hooks after the first failure.  _new in 1.1.0_.
-=r=
-    =c= `minimum_pre_commit_version`
-    =c= (optional: default `'0'`) require a minimum version of pre-commit.
-        _new in 1.15.0_.
-```
-
-A sample top-level:
-
-```yaml
-exclude: '^$'
-fail_fast: false
-repos:
--   ...
-```
-
-## .pre-commit-config.yaml - repos
-
-The repository mapping tells pre-commit where to get the code for the hook
-from.
-
-```table
-=r=
-    =c= `repo`
-    =c= the repository url to `git clone` from
-=r=
-    =c= `rev`
-    =c= the revision or tag to clone at.  _new in 1.7.0_: previously `sha`
-=r=
-    =c= `hooks`
-    =c= A list of [hook mappings](#pre-commit-configyaml---hooks).
-```
-
-A sample repository with all defaults present:
-
-```yaml
-repos:
--   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v1.2.3
-    hooks:
-    -   ...
-```
-
-## .pre-commit-config.yaml - hooks
-
-The hook mapping configures which hook from the repository is used and allows
-for customization.  All optional keys will receive their default from the
-repository's configuration.
-
-```table
-=r=
-    =c= `id`
-    =c= which hook from the repository to use.
-=r=
-    =c= `alias`
-    =c= (optional) allows the hook to be referenced using an additional id when
-        using `pre-commit run <hookid>`.
-        _new in 1.14.0_.
-=r=
-    =c= `name`
-    =c= (optional) override the name of the hook - shown during hook execution.
-=r=
-    =c= `language_version`
-    =c= (optional) override the language version for the
-        hook.  See [Overriding Language Version](#overriding-language-version).
-=r=
-    =c= `files`
-    =c= (optional) override the default pattern for files to run on.
-=r=
-    =c= `exclude`
-    =c= (optional) file exclude pattern.
-=r=
-    =c= `types`
-    =c= (optional) override the default file types to run on.  See
-        [Filtering files with types](#filtering-files-with-types).
-=r=
-    =c= `exclude_types`
-    =c= (optional) file types to exclude.
-=r=
-    =c= `args`
-    =c= (optional) list of additional parameters to pass to the hook.
-=r=
-    =c= `stages`
-    =c= (optional) confines the hook to the `commit`, `merge-commit`, `push`,
-        `prepare-commit-msg`, `commit-msg`, `post-checkout`, or `manual` stage.  See
-        [Confining hooks to run at certain stages](#confining-hooks-to-run-at-certain-stages).
-=r=
-    =c= `additional_dependencies`
-    =c= (optional) a list of dependencies that will be installed in the
-        environment where this hook gets run.  One useful application is to
-        install plugins for hooks such as `eslint`.
-=r=
-    =c= `always_run`
-    =c= (optional) if `true`, this hook will run even if there are no matching
-        files.
-=r=
-    =c= `verbose`
-    =c= (optional) if `true`, forces the output of the hook to be printed even when
-        the hook passes.  _new in 1.6.0_.
-=r=
-    =c= `log_file`
-    =c= (optional) if present, the hook output will additionally be written
-        to a file.
-```
-
-One example of a complete configuration:
-
-```yaml
-repos:
--   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v1.2.3
-    hooks:
-    -   id: trailing-whitespace
-```
-
-This configuration says to download the pre-commit-hooks project and run its
-trailing-whitespace hook.
-
-## Updating hooks automatically
-
-You can update your hooks to the latest version automatically by running
-[`pre-commit autoupdate`](#pre-commit-autoupdate).  By default, this will
-bring the hooks to the latest tag on the master branch.
-''')}
-        </div>
-
-        <div id="usage">
-            <div class="page-header">${md('# Usage')}</div>
-${md('''
-Run `pre-commit install` to install pre-commit into your git hooks. pre-commit
-will now run on every commit. Every time you clone a project using pre-commit
-running `pre-commit install` should always be the first thing you do.
-
-If you want to manually run all pre-commit hooks on a repository, run
-`pre-commit run --all-files`. To run individual hooks use
-`pre-commit run <hook_id>`.
-
-The first time pre-commit runs on a file it will automatically download,
-install, and run the hook. Note that running a hook for the first time may be
-slow. For example: If the machine does not have node installed, pre-commit
-will download and build a copy of node.
-
-```pre-commit
-$ pre-commit install
-pre-commit installed at /home/asottile/workspace/pytest/.git/hooks/pre-commit
-$ git commit -m "Add super awesome feature"
-black....................................................................Passed
-blacken-docs.........................................(no files to check)Skipped
-Trim Trailing Whitespace.................................................Passed
-Fix End of Files.........................................................Passed
-Check Yaml...........................................(no files to check)Skipped
-Debug Statements (Python)................................................Passed
-Flake8...................................................................Passed
-Reorder python imports...................................................Passed
-pyupgrade................................................................Passed
-rst ``code`` is two backticks........................(no files to check)Skipped
-rst..................................................(no files to check)Skipped
-changelog filenames..................................(no files to check)Skipped
-[master 146c6c2c] Add super awesome feature
- 1 file changed, 1 insertion(+)
-```
-''')}
-        </div>
-
-        <div id="new-hooks">
-            <div class="page-header">${md('# Creating new hooks')}</div>
-${md('''
-pre-commit currently supports hooks written in
-[many languages](#supported-languages). As long as your git repo is an
-installable package (gem, npm, pypi, etc.) or exposes an executable, it can be
-used with pre-commit. Each git repo can support as many languages/hooks as you
-want.
-
-The hook must exit nonzero on failure or modify files in the working directory.
-
-A git repo containing pre-commit plugins must contain a .pre-commit-hooks.yaml
-file that tells pre-commit:
-
-```table
-=r=
-    =c= `id`
-    =c= the id of the hook - used in pre-commit-config.yaml.
-=r=
-    =c= `name`
-    =c= the name of the hook - shown during hook execution.
-=r=
-    =c= `entry`
-    =c= the entry point - the executable to run.  `entry` can also contain
-        arguments that will not be overridden such as `entry: autopep8 -i`.
-=r=
-    =c= `language`
-    =c= the language of the hook - tells pre-commit how to install the hook.
-=r=
-    =c= `files`
-    =c= (optional: default `''`) the pattern of files to run on.
-=r=
-    =c= `exclude`
-    =c= (optional: default `^$`)  exclude files that were matched by `files`.
-=r=
-    =c= `types`
-    =c= (optional: default `[file]`)  list of file types to run on.  See
-        [Filtering files with types](#filtering-files-with-types).
-=r=
-    =c= `exclude_types`
-    =c= (optional: default `[]`)  exclude files that were matched by `types`.
-=r=
-    =c= `always_run`
-    =c= (optional: default `false`) if `true` this hook will run even if there
-        are no matching files.
-=r=
-    =c= `verbose`
-    =c= (optional) if `true`, forces the output of the hook to be printed even when
-        the hook passes.  _new in 1.6.0_.
-=r=
-    =c= `pass_filenames`
-    =c= (optional: default `true`) if `false` no arguments will be passed to
-        the hook.
-=r=
-    =c= `require_serial`
-    =c= (optional: default `false`) if `true` this hook will execute using a
-        single process instead of in parallel. _new in 1.13.0_.
-=r=
-    =c= `description`
-    =c= (optional: default `''`) description of the hook.  used for metadata
-        purposes only.
-=r=
-    =c= `language_version`
-    =c= (optional: default `default`) see
-        [Overriding language version](#overriding-language-version).
-=r=
-    =c= `minimum_pre_commit_version`
-    =c= (optional: default `'0'`) allows one to indicate a minimum
-        compatible pre-commit version.
-=r=
-    =c= `args`
-    =c= (optional: default `[]`) list of additional parameters to pass to the hook.
-
-```
-
-For example:
-
-```yaml
--   id: trailing-whitespace
-    name: Trim Trailing Whitespace
-    description: This hook trims trailing whitespace.
-    entry: trailing-whitespace-fixer
-    language: python
-    types: [text]
-```
-
-## Developing hooks interactively
-
-Since the `repo` property of `.pre-commit-config.yaml` can refer to anything
-that `git clone ...` understands, it's often useful to point it at a local
-directory while developing hooks.
-
-[`pre-commit try-repo`](#pre-commit-try-repo) streamlines this process by
-enabling a quick way to try out a repository.  Here's how one might work
-interactively:
-
-_note_: you may need to provide `--commit-msg-filename` when using this
-command with hook types `prepare-commit-msg` and `commit-msg`.
-
-_new in 1.14.0_: a commit is no longer necessary to `try-repo` on a local
-directory. `pre-commit` will clone any uncommitted changes.
-
-```pre-commit
-~/work/hook-repo $ git checkout origin/master -b feature
-
-# ... make some changes
-
-# new in 1.14.0: a commit is no longer necessary for `try-repo`
-
-# In another terminal or tab
-
-~/work/other-repo $ pre-commit try-repo ../hook-repo foo --verbose --all-files
-===============================================================================
-Using config:
-===============================================================================
-repos:
--   repo: ../hook-repo
-    rev: 84f01ac09fcd8610824f9626a590b83cfae9bcbd
-    hooks:
-    -   id: foo
-===============================================================================
-[INFO] Initializing environment for ../hook-repo.
-Foo......................................................................Passed
-- hook id: foo
-- duration: 0.02s
-
-Hello from foo hook!
-
-```
-
-## Supported languages
-
-- [conda](#conda)
-- [docker](#docker)
-- [docker_image](#docker_image)
-- [fail](#fail)
-- [golang](#golang)
-- [node](#node)
-- [perl](#perl)
-- [python](#python)
-- [python_venv](#python_venv)
-- [ruby](#ruby)
-- [rust](#rust)
-- [swift](#swift)
-- [pygrep](#pygrep)
-- [script](#script)
-- [system](#system)
-
-### conda
-
-_new in 1.21.0_
-
-The hook repository must contain an `environment.yml` file which will be used
-via `conda env create --file environment.yml ...` to create the environment.
-
-The `conda` language also supports `additional_dependencies` and will pass any
-of the values directly into `conda install`.  This language can therefore be
-used with [local](#repository-local-hooks) hooks.
-
-__Support:__ `conda` hooks work as long as there is a system-installed `conda`
-binary (such as [`miniconda`](https://docs.conda.io/en/latest/miniconda.html)).
-It has been tested on linux, macOS, and windows.
-
-### docker
-
-The hook repository must have a `Dockerfile`.  It will be installed via
-`docker build .`.
-
-Running Docker hooks requires a running Docker engine on your host.  For
-configuring Docker hooks, your `entry` should correspond to an executable
-inside the Docker container, and will be used to override the default container
-entrypoint. Your Docker `CMD` will not run when pre-commit passes a file list
-as arguments to the run container command. Docker allows you to use any
-language that's not supported by pre-commit as a builtin.
-
-pre-commit will automatically mount the repository source as a volume using
-`-v $PWD:/src:rw,Z` and set the working directory using `--workdir /src`.
-
-__Support:__ docker hooks are known to work on any system which has a working
-`docker` executable.  It has been tested on linux and macOS.  Hooks that are
-run via `boot2docker` are known to be unable to make modifications to files.
-
-See [this repository](https://github.com/pre-commit/pre-commit-docker-flake8)
-for an example Docker-based hook.
-
-### docker_image
-
-A more lightweight approach to `docker` hooks.  The `docker_image`
-"language" uses existing docker images to provide hook executables.
-
-`docker_image` hooks can be conveniently configured as [local](#repository-local-hooks)
-hooks.
-
-The `entry` specifies the docker tag to use.  If an image has an
-`ENTRYPOINT` defined, nothing special is needed to hook up the executable.
-If the container does not specify an `ENTRYPOINT` or you want to change the
-entrypoint you can specify it as well in your `entry`.
-
-For example:
-
-```yaml
--   id: dockerfile-provides-entrypoint
-    name: ...
-    language: docker_image
-    entry: my.registry.example.com/docker-image-1:latest
--   id: dockerfile-no-entrypoint-1
-    name: ...
-    language: docker_image
-    entry: --entrypoint my-exe my.registry.example.com/docker-image-2:latest
-# Alternative equivalent solution
--   id: dockerfile-no-entrypoint-2
-    name: ...
-    language: docker_image
-    entry: my.registry.example.com/docker-image-3:latest my-exe
-```
-
-### fail
-
-_new in 1.11.0_
-
-A lightweight `language` to forbid files by filename.  The `fail` language is
-especially useful for [local](#repository-local-hooks) hooks.
-
-The `entry` will be printed when the hook fails.  It is suggested to provide
-a brief description for `name` and more verbose fix instructions in `entry`.
-
-Here's an example which prevents any file except those ending with `.rst` from
-being added to the `changelog` directory:
-
-```yaml
--   repo: local
-    hooks:
-    -   id: changelogs-rst
-        name: changelogs must be rst
-        entry: changelog filenames must end in .rst
-        language: fail
-        files: 'changelog/.*(?<!\.rst)$'
-```
-
-### golang
-
-The hook repository must contain go source code.  It will be installed via
-`go get ./...`.  pre-commit will create an isolated `GOPATH` for each hook and
-the `entry` should match an executable which will get installed into the
-`GOPATH`'s `bin` directory.
-
-__Support:__ golang hooks are known to work on any system which has go
-installed.  It has been tested on linux, macOS, and windows.
-
-### node
-
-The hook repository must have a `package.json`.  It will be installed via
-`npm install .`.  The installed package will provide an executable that will
-match the `entry` – usually through `bin` in package.json.
-
-__Support:__ node hooks work without any system-level dependencies.  It has
-been tested on linux and macOS and _may_ work under cygwin.
-
-_new in 1.5.0_: windows is now supported for node hooks.  Currently python3
-only due to [a bug in cpython](https://bugs.python.org/issue32539).
-
-### perl
-
-_new in 2.1.0_
-
-Perl hooks are installed using the system installation of
-[cpan](https://perldoc.perl.org/5.30.0/cpan.html), the CPAN package installer
-that comes with Perl.
-
-Hook repositories must have something that `cpan` supports, typically
-`Makefile.PL` or `Build.PL`, which it uses to install an executable to
-use in the `entry` definition for your hook. The repository will be installed
-via `cpan -T .` (with the installed files stored in your pre-commit cache,
-not polluting other Perl installations).
-
-When specifying `additional_dependencies` for Perl, you can use any of the
-[install argument formats understood by `cpan`](https://perldoc.perl.org/5.30.0/CPAN.html#get%2c-make%2c-test%2c-install%2c-clean-modules-or-distributions).
-
-__Support:__ Perl hooks currently require a pre-existing Perl installation,
-including the `cpan` tool in `PATH`.  It has been tested on linux, macOS, and
-Windows.
-
-### python
-
-The hook repository must be installable via `pip install .` (usually by either
-`setup.py` or `pyproject.toml`).  The installed package will provide an
-executable that will match the `entry` – usually through `console_scripts` or
-`scripts` in setup.py.
-
-__Support:__ python hooks work without any system-level dependencies.  It
-has been tested on linux, macOS, windows, and cygwin.
-
-### python_venv
-
-_new in 1.9.0_
-
-An alternate implementation of the [python](#python) language which uses the
-python 3 [`venv`](https://docs.python.org/3/library/venv.html) module.
-On many systems you need to additionally install the `python3-venv` system
-package to use this language.  This is otherwise a drop-in replacement for the
-`python` language for situations where [`virtualenv` may not
-work](https://github.com/pre-commit/pre-commit/issues/631).
-
-__Support:__ python hooks work without any system-level dependencies.  It
-has been tested on linux, macOS, windows, and cygwin.  Only python3
-environments can be created with this language.
-
-### ruby
-
-The hook repository must have a `*.gemspec`.  It will be installed via
-`gem build *.gemspec && gem install *.gem`.  The installed package will
-produce an executable that will match the `entry` – usually through
-`executables` in your gemspec.
-
-__Support:__ ruby hooks work without any system-level dependencies.  It has
-been tested on linux and macOS and _may_ work under cygwin.
-
-### rust
-
-_new in 1.10.0_
-
-Rust hooks are installed using the system installation of
-[Cargo](https://github.com/rust-lang/cargo), Rust's official package manager.
-
-Hook repositories must have a `Cargo.toml` file which produces at least one
-binary ([example](https://github.com/chriskuehl/example-rust-pre-commit-hook)),
-whose name should match the `entry` definition for your hook. The repo will be
-installed via `cargo install --bins` (with the binaries stored in your
-pre-commit cache, not polluting your user-level Cargo installations).
-
-When specifying `additional_dependencies` for Rust, you can use the syntax
-`{package_name}:{package_version}` to specify a new library dependency (used to
-build _your_ hook repo), or the special syntax
-`cli:{package_name}:{package_version}` for a CLI dependency (built separately,
-with binaries made available for use by hooks).
-
-__Support:__ Rust hooks currently require a pre-existing Rust installation.  It
-has been tested on linux, Windows, and macOS.
-
-### swift
-
-The hook repository must have a `Package.swift`.  It will be installed via
-`swift build -c release`.  The `entry` should match an executable created by
-building the repository.
-
-__Support:__ swift hooks are known to work on any system which has swift
-installed.  It has been tested on linux and macOS.
-
-### pygrep
-
-_new in 1.2.0_
-
-A cross-platform python implementation of `grep` – pygrep hooks are a quick
-way to write a simple hook which prevents commits by file matching.  Specify
-the regex as the `entry`.  The `entry` may be any python
-[regular expression](#regular-expressions).  For case insensitive regexes you
-can apply the `(?i)` flag as the start of your entry, or use `args: [-i]`.
-
-_new in 1.8.0_: For multiline matches, use `args: [--multiline]`.
-
-__Support:__ pygrep hooks are supported on all platforms which pre-commit runs
-on.
-
-### script
-
-Script hooks provide a way to write simple scripts which validate files. The
-`entry` should be a path relative to the root of the hook repository.
-
-This hook type will not be given a virtual environment to work with – if it
-needs additional dependencies the consumer must install them manually.
-
-__Support:__ the support of script hooks depend on the scripts themselves.
-
-### system
-
-System hooks provide a way to write hooks for system-level executables which
-don't have a supported language above (or have special environment
-requirements that don't allow them to run in isolation such as pylint).
-
-This hook type will not be given a virtual environment to work with – if it
-needs additional dependencies the consumer must install them manually.
-
-__Support:__ the support of system hooks depend on the executables.
-''')}
-        </div>
-
-        <div id="cli">
-            <div class="page-header">${md('# Command line interface')}</div>
-
-${md('''
-All pre-commit commands take the following options:
-
-- `--color {auto,always,never}`: whether to use color in output.
-  Defaults to `auto`.  _new in 1.18.0_: can be overridden by using
-  `PRE_COMMIT_COLOR={auto,always,never}` or disabled using `TERM=dumb`.
-- `-c CONFIG`, `--config CONFIG`: path to alternate config file
-- `-h`, `--help`: show help and available options.
-
-## pre-commit autoupdate [options] [](#pre-commit-autoupdate)
-
-Auto-update pre-commit config to the latest repos' versions.
-
-Options:
-
-- `--bleeding-edge`: update to the bleeding edge of `master` instead of the
-  latest tagged version (the default behaviour).
-- `--freeze`: _new in 1.21.0_): Store "frozen" hashes in `rev` instead of tag
-  names.
-- `--repo REPO`: _new in 1.4.1_: Only update this repository. _new in 1.7.0_:
-  This option may be specified multiple times.
-
-Here are some sample invocations using this `.pre-commit-config.yaml`:
-
-```yaml
-repos:
--   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v2.1.0
-    hooks:
-    -   id: trailing-whitespace
--   repo: https://github.com/asottile/pyupgrade
-    rev: v1.25.0
-    hooks:
-    -   id: pyupgrade
-        args: [--py36-plus]
-```
-
-```console
-$ : default: update to latest tag on default branch
-$ pre-commit autoupdate  # by default: pick tags
-Updating https://github.com/pre-commit/pre-commit-hooks ... updating v2.1.0 -> v2.4.0.
-Updating https://github.com/asottile/pyupgrade ... updating v1.25.0 -> v1.25.2.
-$ grep rev: .pre-commit-config.yaml
-    rev: v2.4.0
-    rev: v1.25.2
-```
-
-```console
-$ : update a specific repository to the latest revision of the default branch
-$ pre-commit autoupdate --bleeding-edge --repo https://github.com/pre-commit/pre-commit-hooks
-Updating https://github.com/pre-commit/pre-commit-hooks ... updating v2.1.0 -> 5df1a4bf6f04a1ed3a643167b38d502575e29aef.
-$ grep rev: .pre-commit-config.yaml
-    rev: 5df1a4bf6f04a1ed3a643167b38d502575e29aef
-    rev: v1.25.0
-```
-
-```console
-$ : update to frozen versions
-$ pre-commit autoupdate --freeze
-Updating https://github.com/pre-commit/pre-commit-hooks ... updating v2.1.0 -> v2.4.0 (frozen).
-Updating https://github.com/asottile/pyupgrade ... updating v1.25.0 -> v1.25.2 (frozen).
-$ grep rev: .pre-commit-config.yaml
-    rev: 0161422b4e09b47536ea13f49e786eb3616fe0d7  # frozen: v2.4.0
-    rev: 34a269fd7650d264e4de7603157c10d0a9bb8211  # frozen: v1.25.2
-```
-
-## pre-commit clean [options] [](#pre-commit-clean)
-
-Clean out cached pre-commit files.
-
-Options: (no additional options)
-
-## pre-commit gc [options] [](#pre-commit-gc)
-
-_new in 1.14.0_
-
-Clean unused cached repos.
-
-`pre-commit` keeps a cache of installed hook repositories which grows over
-time.  This command can be run periodically to clean out unused repos from
-the cache directory.
-
-Options: (no additional options)
-
-## pre-commit init-templatedir DIRECTORY [options] [](#pre-commit-init-templatedir)
-
-_new in 1.18.0_
-
-Install hook script in a directory intended for use with
-`git config init.templateDir`.
-
-Options:
-
-- `-t {pre-commit,pre-merge-commit,pre-push,prepare-commit-msg,commit-msg,post-checkout}`,
-  `--hook-type {pre-commit,pre-merge-commit,pre-push,prepare-commit-msg,commit-msg,post-checkout}`:
-  which hook type to install.
-
-Some example useful invocations:
-
-```bash
-git config --global init.templateDir ~/.git-template
-pre-commit init-templatedir ~/.git-template
-```
-
-Now whenever a repository is cloned or created, it will have the hooks set up
-already!
-
-## pre-commit install [options] [](#pre-commit-install)
-
-Install the pre-commit script.
-
-Options:
-
-- `-f`, `--overwrite`: Replace any existing git hooks with the pre-commit
-  script.
-- `--install-hooks`: Also install environments for all available hooks now
-  (rather than when they are first executed). See [`pre-commit
-  install-hooks`](#pre-commit-install-hooks).
-- `-t {pre-commit,pre-merge-commit,pre-push,prepare-commit-msg,commit-msg,post-checkout}`,
-  `--hook-type {pre-commit,pre-merge-commit,pre-push,prepare-commit-msg,commit-msg,post-checkout}`:
-  Specify which hook type to install.
-- `--allow-missing-config`: Hook scripts will permit a missing configuration
-  file.
-
-Some example useful invocations:
-
-- `pre-commit install`: Default invocation. Installs the pre-commit script
-   alongside any existing git hooks.
-- `pre-commit install --install-hooks --overwrite`: Idempotently replaces
-   existing git hook scripts with pre-commit, and also installs hook
-   environments.
-
-## pre-commit install-hooks [options] [](#pre-commit-install-hooks)
-
-Install all missing environments for the available hooks. Unless this command or
-`install --install-hooks` is executed, each hook's environment is created the
-first time the hook is called.
-
-Each hook is initialized in a separate environment appropriate to the language
-the hook is written in. See [supported languages](#supported-languages).
-
-This command does not install the pre-commit script. To install the script along with
-the hook environments in one command, use `pre-commit install --install-hooks`.
-
-Options: (no additional options)
-
-## pre-commit migrate-config [options] [](#pre-commit-migrate-config)
-
-_new in 1.0.0_
-
-Migrate list configuration to the new map configuration format.
-
-Options: (no additional options)
-
-## pre-commit run [hook-id] [options] [](#pre-commit-run)
-
-Run hooks.
-
-Options:
-
-- `[hook-id]`: specify a single hook-id to run only that hook.
-- `-a`, `--all-files`: run on all the files in the repo.
-- `--files [FILES [FILES ...]]`: specific filenames to run hooks on.
-- `--from-ref FROM_REF` + `--to-ref TO_REF`: run against the files changed
-  between `FROM_REF...TO_REF` in git.
-    - _new in 2.2.0_: prior to 2.2.0 the arguments were `--source` and
-      `--origin`.
-- `--show-diff-on-failure`: when hooks fail, run `git diff` directly afterward.
-- `-v`, `--verbose`: produce hook output independent of success.  Include hook
-  ids in output.
-
-Some example useful invocations:
-- `pre-commit run`: this is what pre-commit runs by default when committing.
-  This will run all hooks against currently staged files.
-- `pre-commit run --all-files`: run all the hooks against all the files.  This
-  is a useful invocation if you are using pre-commit in CI.
-- `pre-commit run flake8`: run the `flake8` hook against all staged files.
-- `git ls-files -- '*.py' | xargs pre-commit run --files`: run all hooks
-  against all `*.py` files in the repository.
-- `pre-commit run --from-ref HEAD^^^ --to-ref HEAD`: run against the files that
-  have changed between `HEAD^^^` and `HEAD`.  This form is useful when
-  leveraged in a pre-receive hook.
-
-## pre-commit sample-config [options] [](#pre-commit-sample-config)
-
-Produce a sample `.pre-commit-config.yaml`.
-
-Options: (no additional options)
-
-## pre-commit try-repo REPO [options] [](#pre-commit-try-repo)
-
-_new in 1.3.0_
-
-Try the hooks in a repository, useful for developing new hooks.
-`try-repo` can also be used for testing out a repository before adding it to
-your configuration.  `try-repo` prints a configuration it generates based on
-the remote hook repository before running the hooks.
-
-Options:
-
-- `REPO`: required clonable hooks repository.  Can be a local path on
-  disk.
-- `--ref REF`: Manually select a ref to run against, otherwise the `HEAD`
-  revision will be used.
-- `pre-commit try-repo` also supports all available options for
-  [`pre-commit run`](#pre-commit-run).
-
-Some example useful invocations:
-- `pre-commit try-repo https://github.com/pre-commit/pre-commit-hooks`: runs
-  all the hooks in the latest revision of `pre-commit/pre-commit-hooks`.
-- `pre-commit try-repo ../path/to/repo`: run all the hooks in a repository on
-  disk.
-- `pre-commit try-repo ../pre-commit-hooks flake8`: run only the `flake8` hook
-  configured in a local `../pre-commit-hooks` repository.
-- See [`pre-commit run`](#pre-commit-run) for more useful `run` invocations
-  which are also supported by `pre-commit try-repo`.
-
-## pre-commit uninstall [options] [](#pre-commit-uninstall)
-
-Uninstall the pre-commit script.
-
-Options:
-
-- `-t {pre-commit,pre-merge-commit,pre-push,prepare-commit-msg,commit-msg}`,
-  `--hook-type {pre-commit,pre-merge-commit,pre-push,prepare-commit-msg,commit-msg}`: which hook
-  type to uninstall.
-''')}
-        </div>
-
-        <div id="advanced">
-            <div class="page-header">${md('# Advanced features')}</div>
-
-${md('''
-## Running in migration mode
-
-By default, if you have existing hooks `pre-commit install` will install in a
-migration mode which runs both your existing hooks and hooks for pre-commit.
-To disable this behavior, pass `-f` / `--overwrite` to the `install` command.
-If you decide not to use pre-commit, `pre-commit uninstall` will
-restore your hooks to the state prior to installation.
-
-## Temporarily disabling hooks
-
-Not all hooks are perfect so sometimes you may need to skip execution of one
-or more hooks. pre-commit solves this by querying a `SKIP` environment
-variable. The `SKIP` environment variable is a comma separated list of hook
-ids. This allows you to skip a single hook instead of `--no-verify`ing the
-entire commit.
-
-```console
-$ SKIP=flake8 git commit -m "foo"
-```
-
-## pre-commit during commits
-
-Running hooks on unstaged changes can lead to both false-positives and
-false-negatives during committing.  pre-commit only runs on the staged
-contents of files by temporarily saving the contents of your files at commit
-time and stashing the unstaged changes while running hooks.
-
-## pre-commit during merges
-
-The biggest gripe we’ve had in the past with pre-commit hooks was during merge
-conflict resolution.  When working on very large projects a merge often
-results in hundreds of committed files. I shouldn’t need to run hooks on all
-of these files that I didn’t even touch!  This often led to running commit
-with `--no-verify` and allowed introduction of real bugs that hooks could have
-caught.
-
-pre-commit solves this by only running hooks on files that conflict or were
-manually edited during conflict resolution.  This also includes files which
-were automatically merged by git.  Git isn't perfect and this can often catch
-implicit conflicts (such as with removed python imports).
-
-## pre-commit during clean merges
-
-_new in 1.21.0_ pre-commit can be used to manage [pre-merge-commit] hooks.
-
-To use `pre-merge-commit` hooks with pre-commit, run:
-
-```console
-$ pre-commit install --hook-type pre-merge-commit
-pre-commit installed at .git/hooks/pre-merge-commit
-```
-
-The hook fires after a merge succeeds but before the merge commit is created.
-
-Note that you need to be using at least git 2.24 which added support for the
-pre-merge-commit hook.
-
-[pre-merge-commit]: https://git-scm.com/docs/githooks#_pre_merge_commit
-
-## pre-commit during push
-
-To use `pre-push` hooks with pre-commit, run:
-
-```console
-$ pre-commit install --hook-type pre-push
-pre-commit installed at .git/hooks/pre-push
-```
-
-During a push, pre-commit will export the following environment variables:
-- `PRE_COMMIT_FROM_REF`: the remote revision that is being pushed to.
-    - _new in 2.2.0_ prior to 2.2.0 the variable was `PRE_COMMIT_SOURCE`.
-- `PRE_COMMIT_TO_REF`: the local revision that is being pushed to the remote.
-    - _new in 2.2.0_ prior to 2.2.0 the variable was `PRE_COMMIT_ORIGIN`.
-- `PRE_COMMIT_REMOTE_NAME`: _new in 2.0.0_ which remote is being pushed to
-  (for example `origin`)
-- `PRE_COMMIT_REMOTE_URL`: _new in 2.0.0_ the url of the remote that is being
-  pushed to (for example `git@github.com:pre-commit/pre-commit`.
-
-[pre-push]: https://git-scm.com/docs/githooks#_pre_push
-
-## pre-commit for commit messages
-
-pre-commit can be used to manage [commit-msg] hooks.
-
-To use `commit-msg` hooks with pre-commit, run:
-
-```console
-$ pre-commit install --hook-type commit-msg
-pre-commit installed at .git/hooks/commit-msg
-```
-
-`commit-msg` hooks can be configured by setting `stages: [commit-msg]`.
-`commit-msg` hooks will be passed a single filename -- this file contains the
-current contents of the commit message which can be validated.  If a hook
-exits nonzero, the commit will be aborted.
-
-_new in 1.16.0_: pre-commit can be used to manage [prepare-commit-msg] hooks.
-
-To use `prepare-commit-msg` hooks with pre-commit run:
-
-```console
-$ pre-commit install --hook-type prepare-commit-msg`
-pre-commit installed at .git/hooks/prepare-commit-msg
-```
-
-`prepare-commit-msg` hooks can be used to create dynamic templates for commit
-messages. `prepare-commit-msg` hooks can be configured by setting
-`stages: [prepare-commit-msg]`. `prepare-commit-msg` hooks will be passed a
-single filename -- this file contains any initial commit message (e.g. from
-`git commit -m "..."` or a template) and can be modified by the hook before
-the editor is shown. A hook may want to check for `GIT_EDITOR=:` as this
-indicates that no editor will be launched. If a hook exits nonzero,
-the commit will be aborted.
-
-[commit-msg]: https://git-scm.com/docs/githooks#_commit_msg
-[prepare-commit-msg]: https://git-scm.com/docs/githooks#_prepare_commit_msg
-
-
-## pre-commit for switching branches
-_new in 2.2.0_: pre-commit can be used to manage [post-checkout] hooks.
-
-To use `post-checkout` hooks with pre-commit run:
-
-```console
-$ pre-commit install --hook-type post-checkout
-pre-commit installed at .git/hooks/post-checkout
-```
-
-`post-checkout` hooks can be used to perform repository validity checks,
-auto-display differences from the previous HEAD if different,
-or set working dir metadata properties. Since `post-checkout` doesn't operate
-on files, any hooks must set `always_run`:
-
-```yaml
--   repo: local
-    hooks:
-    -   id: post-checkout-local
-        name: Post checkout
-        always_run: true
-        stages: [post-checkout]
-        # ...
-```
-
-`post-checkout` hooks have three environment variables they can check to
-do their work: `$PRE_COMMIT_FROM_REF`, `$PRE_COMMIT_TO_REF`,
-and `$PRE_COMMIT_CHECKOUT_TYPE`. These correspond to the first, second,
-and third arguments (respectively) that are normally passed to a regular
-post-checkout hook from Git.
-
-[post-checkout]: https://git-scm.com/docs/githooks#_post_checkout
-
-## Confining hooks to run at certain stages
-
-Since the `default_stages` top level configuration property of the
-`.pre-commit-config.yaml` file is set to all stages by default, when installing
-hooks using the `-t`/`--hook-type` option (see [pre-commit
-install [options]](#pre-commit-install)), all hooks will be installed by default
-to run at the stage defined through that option. for instance,
-`pre-commit install --hook-type pre-push` will install by default all hooks
-to run at the `push` stage.
-
-Hooks can however be confined to a stage by setting the `stages` property in
-your `.pre-commit-config.yaml`.  The `stages` property is an array and can
-contain any of `commit`, `merge-commit`, `push`, `prepare-commit-msg`,
-`commit-msg` and `manual`.
-
-If you do not want to have hooks installed by default on the stage passed
-during a `pre-commit install --hook-type ...`, please set the `default_stages`
-top level configuration property to the desired stages, also as an array.
-
-_new in 1.8.0_: An additional `manual` stage is available for one off execution
-that won't run in any hook context.  This special stage is useful for taking
-advantage of `pre-commit`'s cross-platform / cross-language package management
-without running it on every commit.  Hooks confied to `stages: [manual]` can
-be executed by running `pre-commit run --hook-stage manual <hookid>`.
-
-## Passing arguments to hooks
-
-Sometimes hooks require arguments to run correctly. You can pass static
-arguments by specifying the `args` property in your `.pre-commit-config.yaml`
-as follows:
-
-```yaml
--   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v1.2.3
-    hooks:
-    -   id: flake8
-        args: [--max-line-length=131]
-```
-
-This will pass `--max-line-length=131` to `flake8`.
-
-### Arguments pattern in hooks
-
-If you are writing your own custom hook, your hook should expect to receive
-the `args` value and then a list of staged files.
-
-For example, assuming a `.pre-commit-config.yaml`:
-
-```yaml
--   repo: https://github.com/path/to/your/hook/repo
-    rev: badf00ddeadbeef
-    hooks:
-    -   id: my-hook-script-id
-        args: [--myarg1=1, --myarg1=2]
-```
-
-When you next run `pre-commit`, your script will be called:
-
-```
-path/to/script-or-system-exe --myarg1=1 --myarg1=2 dir/file1 dir/file2 file3
-```
-
-If the `args` property is empty or not defined, your script will be called:
-
-```
-path/to/script-or-system-exe dir/file1 dir/file2 file3
-```
-
-## Repository local hooks
-
-Repository-local hooks are useful when:
-
-- The scripts are tightly coupled to the repository and it makes sense to
-  distribute the hook scripts with the repository.
-- Hooks require state that is only present in a built artifact of your
-  repository (such as your app's virtualenv for pylint).
-- The official repository for a linter doesn't have the pre-commit metadata.
-
-You can configure repository-local hooks by specifying the `repo` as the
-sentinel `local`.
-
-local hooks can use any language which supports `additional_dependencies` or
-`docker_image` / `fail` / `pygrep` / `script` / `system`.
-This enables you to install things which previously would require a trivial
-mirror repository.
-
-A `local` hook must define `id`, `name`, `language`, `entry`, and `files` /
-`types` as specified under [Creating new hooks](#new-hooks).
-
-Here's an example configuration with a few `local` hooks:
-
-```yaml
--   repo: local
-    hooks:
-    -   id: pylint
-        name: pylint
-        entry: pylint
-        language: system
-        types: [python]
-    -   id: check-x
-        name: Check X
-        entry: ./bin/check-x.sh
-        language: script
-        files: \.x$
-    -   id: scss-lint
-        name: scss-lint
-        entry: scss-lint
-        language: ruby
-        language_version: 2.1.5
-        types: [scss]
-        additional_dependencies: ['scss_lint:0.52.0']
-```
-
-## meta hooks
-
-_new in 1.4.0_
-
-`pre-commit` provides several hooks which are useful for checking the
-pre-commit configuration itself.  These can be enabled using `repo: meta`.
-
-```yaml
--   repo: meta
-    hooks:
-    -   id: ...
-```
-
-The currently available `meta` hooks:
-
-```table
-=r=
-    =c= `check-hooks-apply`
-    =c= ensures that the configured hooks apply to at least one file in the
-        repository.
-        _new in 1.4.0_.
-=r=
-    =c= `check-useless-excludes`
-    =c= ensures that `exclude` directives apply to _any_ file in the
-        repository.
-        _new in 1.4.0_.
-=r=
-    =c= `identity`
-    =c= a simple hook which prints all arguments passed to it, useful for
-        debugging.
-        _new in 1.14.0_.
-```
-
-## automatically enabling pre-commit on repositories
-
-_new in 1.18.0_
-
-`pre-commit init-templatedir` can be used to set up a skeleton for `git`'s
-`init.templateDir` option.  This means that any newly cloned repository will
-automatically have the hooks set up without the need to run
-`pre-commit install`.
-
-To configure, first set `git`'s `init.templateDir` -- in this example I'm
-using `~/.git-template` as my template directory.
-
-```console
-$ git config --global init.templateDir ~/.git-template
-$ pre-commit init-templatedir ~/.git-template
-pre-commit installed at /home/asottile/.git-template/hooks/pre-commit
-```
-
-Now whenever you clone a pre-commit enabled repo, the hooks will already be
-set up!
-
-```pre-commit
-$ git clone -q git@github.com:asottile/pyupgrade
-$ cd pyupgrade
-$ git commit --allow-empty -m 'Hello world!'
-Check docstring is first.............................(no files to check)Skipped
-Check Yaml...........................................(no files to check)Skipped
-Debug Statements (Python)............................(no files to check)Skipped
-...
-```
-
-`init-templatedir` uses the `--allow-missing-config` option from
-`pre-commit install` so repos without a config will be skipped:
-
-```console
-$ git init sample
-Initialized empty Git repository in /tmp/sample/.git/
-$ cd sample
-$ git commit --allow-empty -m 'Initial commit'
-`.pre-commit-config.yaml` config file not found. Skipping `pre-commit`.
-[master (root-commit) d1b39c1] Initial commit
-```
-
-## Filtering files with types
-
-Filtering with `types` provides several advantages over traditional filtering
-with `files`.
-
-- no error-prone regular expressions
-- files can be matched by their shebang (even when extensionless)
-- symlinks / submodules can be easily ignored
-
-`types` is specified per hook as an array of tags.  The tags are discovered
-through a set of heuristics by the
-[identify](https://github.com/chriskuehl/identify) library.  `identify` was
-chosen as it is a small portable pure python library.
-
-Some of the common tags you'll find from identify:
-
-- `file`
-- `symlink`
-- `directory` - in the context of pre-commit this will be a submodule
-- `executable` - whether the file has the executable bit set
-- `text` - whether the file looks like a text file
-- `binary` - whether the file looks like a binary file
-- [tags by extension / naming convention](https://github.com/chriskuehl/identify/blob/master/identify/extensions.py)
-- [tags by shebang (`#!`)](https://github.com/chriskuehl/identify/blob/master/identify/interpreters.py)
-
-To discover the type of any file on disk, you can use `identify`'s cli:
-
-```console
-$ identify-cli setup.py
-["file", "non-executable", "python", "text"]
-$ identify-cli some-random-file
-["file", "non-executable", "text"]
-$ identify-cli --filename-only some-random-file; echo $?
-1
-```
-
-If a file extension you use is not supported, please
-[submit a pull request](https://github.com/chriskuehl/identify)!
-
-`types` and `files` are evaluated with `AND` when filtering.  Tags within
-`types` are also evaluated using `AND`.
-
-For example:
-
-```yaml
-    files: ^foo/
-    types: [file, python]
-```
-
-will match a file `foo/1.py` but will not match `setup.py`.
-
-If you want to match a file path that isn't included in a `type` when using an
-existing hook you'll need to revert back to `files` only matching by overriding
-the `types` setting.  Here's an example of using `check-json` against non-json
-files:
-
-```yaml
-    -   id: check-json
-        types: [file]  # override `types: [json]`
-        files: \.(json|myext)$
-```
-
-Files can also be matched by shebang.  With `types: python`, an `exe` starting
-with `#!/usr/bin/env python3` will also be matched.
-
-As with `files` and `exclude`, you can also exclude types if necessary using
-`exclude_types`.
-
-If you'd like to use `types` with compatibility for older versions
-[here is a guide to ensuring compatibility](https://github.com/pre-commit/pre-commit/pull/551#issuecomment-312535540).
-
-## Regular expressions
-
-The patterns for `files` and `exclude` are python
-[regular expressions](https://docs.python.org/3/library/re.html#regular-expression-syntax)
-and are matched with [`re.search`](https://docs.python.org/3/library/re.html#re.search).
-
-As such, you can use any of the features that python regexes support.
-
-If you find that your regular expression is becoming unwieldy due to a long
-list of excluded / included things, you may find a
-[verbose](https://docs.python.org/3/library/re.html#re.VERBOSE) regular
-expression useful.  One can enable this with yaml's multiline literals and
-the `(?x)` regex flag.
-
-```yaml
-# ...
-    -   id: my-hook
-        exclude: >
-            (?x)^(
-                path/to/file1.py|
-                path/to/file2.py|
-                path/to/file3.py
-            )$
-```
-
-## Overriding language version
-
-Sometimes you only want to run the hooks on a specific version of the
-language. For each language, they default to using the system installed
-language (So for example if I’m running `python3.7` and a hook specifies
-`python`, pre-commit will run the hook using `python3.7`). Sometimes you
-don’t want the default system installed version so you can override this on a
-per-hook basis by setting the `language_version`.
-
-```yaml
--   repo: https://github.com/pre-commit/mirrors-scss-lint
-    rev: v0.54.0
-    hooks:
-    -   id: scss-lint
-        language_version: 2.1.5
-```
-
-This tells pre-commit to use ruby `2.1.5` to run the `scss-lint` hook.
-
-Valid values for specific languages are listed below:
-- python: Whatever system installed python interpreters you have. The value of
-  this argument is passed as the `-p` to `virtualenv`.
-    - _new in 1.4.3_: on windows the
-      [pep394](https://www.python.org/dev/peps/pep-0394/) name will be
-      translated into a py launcher call for portability.  So continue to use
-      names like `python3` (`py -3`) or `python3.6` (`py -3.6`) even on
-      windows.
-- node: See [nodeenv](https://github.com/ekalinin/nodeenv#advanced).
-- ruby: See [ruby-build](https://github.com/sstephenson/ruby-build/tree/master/share/ruby-build).
-
-_new in 1.14.0_: you can now set `default_language_version` at the
-[top level](#pre-commit-configyaml---top-level) in your configuration to
-control the default versions across all hooks of a language.
-
-```yaml
-default_language_version:
-    # force all unspecified python hooks to run python3
-    python: python3
-    # force all unspecified ruby hooks to run ruby 2.1.5
-    ruby: 2.1.5
-```
-
-## badging your repository
-
-you can add a badge to your repository to show your contributors / users that
-you use pre-commit!
-
-[![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
-
-- Markdown:
-
-  ```md#copyable
-  [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
-  ```
-
-- HTML:
-
-  ```html#copyable
-  <a href="https://github.com/pre-commit/pre-commit"><img src="https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white" alt="pre-commit" style="max-width:100%;"></a>
-  ```
-
-- reStructuredText:
-
-  ```rst#copyable
-  .. image:: https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white
-     :target: https://github.com/pre-commit/pre-commit
-     :alt: pre-commit
-  ```
-
-- AsciiDoc:
-
-  ```#copyable
-  image:https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white[pre-commit, link=https://github.com/pre-commit/pre-commit]
-  ```
-
-## Usage in continuous integration
-
-pre-commit can also be used as a tool for continuous integration.  For
-instance, adding `pre-commit run --all-files` as a CI step will ensure
-everything stays in tip-top shape.  To check only files which have changed,
-which may be faster, use something like
-`pre-commit run --from-ref origin.HEAD --to-ref HEAD`
-
-## Managing CI Caches
-
-`pre-commit` by default places its repository store in `~/.cache/pre-commit`
--- this can be configured in two ways:
-
-- `PRE_COMMIT_HOME`: if set, pre-commit will use that location instead.
-- `XDG_CACHE_HOME`: if set, pre-commit will use `$XDG_CACHE_HOME/pre-commit`
-  following the [XDG Base Directory Specification].
-
-[XDG Base Directory Specification]: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
-
-### travis-ci example
-
-```yaml
-cache:
-  directories:
-  - $HOME/.cache/pre-commit
-```
-
-### appveyor example
-
-```yaml
-cache:
-- '%USERPROFILE%\.cache\pre-commit'
-```
-
-### azure pipelines example
-
-note: azure pipelines uses immutable caches so the python version and
-`.pre-commit-config.yaml` hash must be included in the cache key.  for a
-repository template, see [asottile@job--pre-commit.yml].
-
-[job--pre-commit.yml]: https://github.com/asottile/azure-pipeline-templates/blob/master/job--pre-commit.yml
-
-```yaml
-jobs:
-- job: precommit
-
-  # ...
-
-  variables:
-    PRE_COMMIT_HOME: $(Pipeline.Workspace)/pre-commit-cache
-
-  steps:
-
-  # ...
-
-  - script: echo "##vso[task.setvariable variable=PY]$(python -VV)"
-  - task: CacheBeta@0
-    inputs:
-      key: pre-commit | .pre-commit-config.yaml | "$(PY)"
-      path: $(PRE_COMMIT_HOME)
-```
-
-### github actions example
-
-**see the [official pre-commit github action]**
-
-[official pre-commit github action]: https://github.com/pre-commit/action
-
-like [azure pipelines](#azure-pipelines-example), github actions also uses
-immutable caches:
-
-```yaml
-    - name: set PY
-      run: echo "::set-env name=PY::$(python -VV | sha256sum | cut -d' ' -f1)"
-    - uses: actions/cache@v1
-      with:
-        path: ~/.cache/pre-commit
-        key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }}
-```
-
-## Usage with tox
-
-[tox](https://tox.readthedocs.io/) is useful for configuring test / CI tools
-such as pre-commit.  One feature of `tox>=2` is it will clear environment
-variables such that tests are more reproducible.  Under some conditions,
-pre-commit requires a few environment variables and so they must be
-whitelisted.
-
-When cloning repos over ssh (`repo: git@github.com:...`), `git` requires the
-`SSH_AUTH_SOCK` variable and will otherwise fail:
-
-```pre-commit
-[INFO] Initializing environment for git@github.com:pre-commit/pre-commit-hooks.
-An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'fetch', 'origin', '--tags')
-return code: 128
-expected return code: 0
-stdout: (none)
-stderr:
-    git@github.com: Permission denied (publickey).
-    fatal: Could not read from remote repository.
-
-    Please make sure you have the correct access rights
-    and the repository exists.
-
-Check the log at /home/asottile/.cache/pre-commit/pre-commit.log
-```
-
-Add the following to your tox testenv:
-
-```ini
-[testenv]
-passenv = SSH_AUTH_SOCK
-```
-
-Likewise, when cloning repos over http / https
-(`repo: https://github.com:...`), you might be working behind a corporate
-http(s) proxy server, in which case `git` requires the `http_proxy`,
-`https_proxy` and `no_proxy` variables to be set, or the clone may fail:
-
-```ini
-[testenv]
-passenv = http_proxy https_proxy no_proxy
-```
-
-## Using the latest version for a repository
-
-`pre-commit` configuration aims to give a repeatable and fast experience and
-therefore intentionally doesn't provide facilities for "unpinned latest
-version" for hook repositories.
-
-Instead, `pre-commit` provides tools to make it easy to upgrade to the
-latest versions with [`pre-commit autoupdate`](#pre-commit-autoupdate).  If
-you need the absolute latest version of a hook (instead of the latest tagged
-version), pass the `--bleeding-edge` parameter to `autoupdate`.
-
-`pre-commit` assumes that the value of `rev` is an immutable ref (such as a
-tag or SHA) and will cache based on that.  Using a branch name (or `HEAD`) for
-the value of `rev` is not supported and will only represent the state of
-that mutable ref at the time of hook installation (and will *NOT* update
-automatically).
-''')}
-        </div>
-
-        <div id="contributing">
-            <div class="page-header">${md('# Contributing')}</div>
-
-${md('''
-We’re looking to grow the project and get more contributors especially to
-support more languages/versions. We’d also like to get the
-.pre-commit-hooks.yaml files added to popular linters without maintaining
-forks / mirrors.
-
-Feel free to submit bug reports, pull requests, and feature requests.
-
-## Contributors
-
-- website by [Molly Finkle](https://github.com/mfnkl)
-- created by [Anthony Sottile](https://github.com/asottile)
-- core developers: [Ken Struys](https://github.com/struys),
-  [Chris Kuehl](https://github.com/chriskuehl)
-- [framework contributors](https://github.com/pre-commit/pre-commit/graphs/contributors)
-- [core hook contributors](https://github.com/pre-commit/pre-commit-hooks/graphs/contributors)
-- and users like you!
-''')}
-        </div>
+    <div class="col-lg-9 col-12">
+        ${body}
     </div>
 </div>
diff --git a/install-local.py b/install-local.py
deleted file mode 100644
index 3be09157..00000000
--- a/install-local.py
+++ /dev/null
@@ -1,103 +0,0 @@
-#!/usr/bin/env python
-from __future__ import absolute_import
-from __future__ import unicode_literals
-
-import contextlib
-import distutils.spawn
-import io
-import os.path
-import shutil
-import subprocess
-import sys
-import tarfile
-
-
-if str is bytes:
-    from urllib import urlopen
-else:
-    from urllib.request import urlopen
-
-
-TGZ = (
-    'https://pypi.python.org/packages/d4/0c/'
-    '9840c08189e030873387a73b90ada981885010dd9aea134d6de30cd24cb8/'
-    'virtualenv-15.1.0.tar.gz'
-)
-PKG_PATH = '/tmp/.virtualenv-pkg'
-
-
-def clean(dirname):
-    if os.path.exists(dirname):
-        shutil.rmtree(dirname)
-
-
-@contextlib.contextmanager
-def clean_path():
-    try:
-        yield
-    finally:
-        clean(PKG_PATH)
-
-
-def virtualenv(path):
-    clean(PKG_PATH)
-    clean(path)
-
-    print('Downloading ' + TGZ)
-    tar_contents = io.BytesIO(urlopen(TGZ).read())
-    with contextlib.closing(tarfile.open(fileobj=tar_contents)) as tarfile_obj:
-        # Chop off the first path segment to avoid having the version in
-        # the path
-        for member in tarfile_obj.getmembers():
-            _, _, member.name = member.name.partition('/')
-            if member.name:
-                tarfile_obj.extract(member, PKG_PATH)
-    print('Done.')
-
-    with clean_path():
-        return subprocess.call((
-            sys.executable, os.path.join(PKG_PATH, 'virtualenv.py'), path,
-        ))
-
-
-def main():
-    venv_path = os.path.join(os.environ['HOME'], '.pre-commit-venv')
-    bin_dir = os.path.join(os.environ['HOME'], 'bin')
-    script_src = os.path.join(venv_path, 'bin', 'pre-commit')
-    script_dest = os.path.join(bin_dir, 'pre-commit')
-
-    if sys.argv[1:] == ['uninstall']:
-        clean(PKG_PATH)
-        clean(venv_path)
-        if os.path.lexists(script_dest):
-            os.remove(script_dest)
-        print('Cleaned ~/.pre-commit-venv ~/bin/pre-commit')
-        return 0
-
-    virtualenv(venv_path)
-
-    subprocess.check_call((
-        os.path.join(venv_path, 'bin', 'pip'), 'install', 'pre-commit',
-    ))
-
-    print('*' * 79)
-    print('Installing pre-commit to {0}'.format(script_dest))
-    print('*' * 79)
-
-    if not os.path.exists(bin_dir):
-        os.mkdir(bin_dir)
-
-    # os.symlink is not idempotent
-    if os.path.exists(script_dest):
-        os.remove(script_dest)
-
-    os.symlink(script_src, script_dest)
-
-    if not distutils.spawn.find_executable('pre-commit'):
-        print('It looks like {0} is not on your path'.format(bin_dir))
-        print('You may want to add it.')
-        print('Often this does the trick: source ~/.profile')
-
-
-if __name__ == '__main__':
-    exit(main())
diff --git a/logo.png b/logo.png
deleted file mode 100644
index 4473f174..00000000
Binary files a/logo.png and /dev/null differ
diff --git a/make_all_hooks.py b/make_all_hooks.py
deleted file mode 100644
index 75350c48..00000000
--- a/make_all_hooks.py
+++ /dev/null
@@ -1,44 +0,0 @@
-import functools
-import json
-import multiprocessing
-import os.path
-import subprocess
-import tempfile
-from typing import Any
-from typing import Dict
-from typing import Tuple
-
-import yaml
-from pre_commit.clientlib import load_manifest
-
-Loader = getattr(yaml, 'CSafeLoader', yaml.SafeLoader)
-fast_load = functools.partial(yaml.load, Loader=Loader)
-
-
-def get_manifest(repo_path: str) -> Tuple[str, Dict[str, Any]]:
-    print(f'*** {repo_path}')
-    with tempfile.TemporaryDirectory() as directory:
-        repo_dir = os.path.join(directory, 'repo')
-        cmd = ('git', 'clone', '--depth', '1', '-q', repo_path, repo_dir)
-        subprocess.check_call(cmd)
-        manifest_path = os.path.join(repo_dir, '.pre-commit-hooks.yaml')
-        # Validate the manifest just to make sure it's ok.
-        load_manifest(manifest_path)
-        with open(manifest_path) as f:
-            return repo_path, fast_load(f)
-
-
-def main() -> int:
-    with open('all-repos.yaml') as f:
-        repos = fast_load(f)
-
-    pool = multiprocessing.Pool(4)
-    hooks_json = dict(pool.map(get_manifest, repos))
-
-    with open('all-hooks.json', 'w') as hooks_json_file:
-        json.dump(hooks_json, hooks_json_file, indent=4)
-    return 0
-
-
-if __name__ == '__main__':
-    exit(main())
diff --git a/make_templates.py b/make_templates.py
index 8935944a..aca62aed 100644
--- a/make_templates.py
+++ b/make_templates.py
@@ -1,10 +1,22 @@
-import collections
-import json
+from __future__ import annotations
+
 import os.path
-from typing import Any
-from typing import Dict
 
 import mako.lookup
+import markupsafe
+
+from template_lib import md
+
+SECTIONS = (
+    ('Introduction', 'sections/intro.md'),
+    ('Installation', 'sections/install.md'),
+    ('Adding pre-commit plugins to your project', 'sections/plugins.md'),
+    ('Usage', 'sections/usage.md'),
+    ('Creating new hooks', 'sections/new-hooks.md'),
+    ('Command line interface', 'sections/cli.md'),
+    ('Advanced features', 'sections/advanced.md'),
+    ('Contributing', 'sections/contributing.md'),
+)
 
 
 template_lookup = mako.lookup.TemplateLookup(
@@ -14,30 +26,39 @@
 )
 
 
-ALL_TEMPLATES = [
-    filename for filename in os.listdir('.')
-    if filename.endswith('.mako') and filename != 'base.mako'
-]
+def index_body() -> markupsafe.Markup:
+    body_parts = []
+    for title, filename in SECTIONS:
+        div_id, _ = os.path.splitext(os.path.basename(filename))
+        title_rendered = md(f'# {title}')
+        with open(filename) as f:
+            rendered = md(f.read())
+        body_parts.append(
+            markupsafe.Markup(
+                f'<div id="{div_id}">\n'
+                f'    <div class="page-header">{title_rendered}</div>\n'
+                f'    {rendered}\n'
+                f'</div>\n',
+            ),
+        )
+    return markupsafe.Markup().join(body_parts)
 
 
-def get_env() -> Dict[str, Any]:
-    all_hooks = json.loads(
-        open('all-hooks.json').read(),
-        object_pairs_hook=collections.OrderedDict,
-    )
-    return {'all_hooks': all_hooks}
+def hooks_body() -> markupsafe.Markup:
+    with open('sections/hooks.md') as f:
+        return md(f.read())
 
 
 def main() -> int:
-    env = get_env()
-    for template in ALL_TEMPLATES:
-        template_name, _ = os.path.splitext(template)
-        env['template_name'] = template_name
-        with open(f'{template_name}.html', 'w') as html_file:
-            template_obj = template_lookup.get_template(template)
-            html_file.write(template_obj.render(**env))
+    with open('index.html', 'w') as f:
+        tmpl = template_lookup.get_template('index.mako')
+        f.write(tmpl.render(body=index_body(), template_name='index'))
+
+    with open('hooks.html', 'w') as f:
+        tmpl = template_lookup.get_template('hooks.mako')
+        f.write(tmpl.render(body=hooks_body(), template_name='hooks'))
     return 0
 
 
 if __name__ == '__main__':
-    exit(main())
+    raise SystemExit(main())
diff --git a/package.json b/package.json
index 99a627c7..8a5f9f53 100644
--- a/package.json
+++ b/package.json
@@ -1,30 +1,8 @@
 {
-    "repository": "github.com/pre-commit/pre-commit.github.io",
+    "repository": "github.com/pre-commit/pre-commit.com",
     "license": "MIT",
     "dependencies": {
-        "bootstrap-sass": "3.4.1"
-    },
-    "eslintConfig": {
-        "extends": "eslint:recommended",
-        "rules": {
-            "indent": [
-                "error",
-                4
-            ],
-            "quotes": [
-                "error",
-                "single"
-            ],
-            "semi": [
-                "error",
-                "always"
-            ]
-        },
-        "parserOptions": {
-            "ecmaVersion": 6
-        },
-        "env": {
-            "browser": true
-        }
+        "bootstrap": "5.0.2",
+        "sass": "^1.32.13"
     }
 }
diff --git a/requirements-dev.txt b/requirements-dev.txt
index 2f9cb64c..05abc0ec 100644
--- a/requirements-dev.txt
+++ b/requirements-dev.txt
@@ -1,8 +1,5 @@
 mako
-libsass
-markdown-code-blocks
+markdown-code-blocks>=3.0.0
 markdown-to-presentation>=0.0.12
-# remove once merged and release
-git+https://github.com/lepture/mistune@449c2b5
 pre-commit>=1.21.0
 pygments-pre-commit>=1.4.0
diff --git a/scss/_variables.scss b/scss/_variables.scss
index a495baeb..c4339549 100644
--- a/scss/_variables.scss
+++ b/scss/_variables.scss
@@ -1,35 +1,27 @@
-$pc-green-dark: #1f2d23;
-$pc-green-light: #76877c;
-$pc-yellow: #f8b424;
+@import url('https://fonts.googleapis.com/css2?family=Source+Sans+Pro:wght@400;700&display=swap');
 
-$font-family-sans-serif: "Source Sans Pro", "Hevetica Neue", arial, sans-serif;
-$font-size-base: 16px;
 
-// Bootstrap overrides
-$brand-primary: $pc-green-light;
+$primary: #1f2d23 !default;
+$light: #76877c !default;
+$info: #fff !default;
+$secondary: #f8b424 !default;
 
-// Buttons
-$btn-default-color: white;
-$btn-default-bg: transparent;
-$btn-default-border: $btn-default-color;
 
-// Navbar
-$navbar-default-bg: $pc-green-dark;
-$navbar-default-link-active-bg: darken($navbar-default-bg, 2.5%);
-$navbar-default-link-hover-bg: $navbar-default-link-active-bg;
+$font-family-sans-serif: "Source Sans Pro", "Hevetica Neue", arial, sans-serif !default;
+$link-color: $light !default;
 
-$navbar-default-color: white;
-$navbar-default-link-active-color: $navbar-default-color;
-$navbar-default-link-color: $navbar-default-color;
-$navbar-default-link-hover-color: $navbar-default-color;
 
-$navbar-default-toggle-border-color: $btn-default-color;
-$navbar-default-toggle-hover-bg: $btn-default-bg;
-$navbar-default-toggle-icon-bar-bg: $btn-default-color;
+$console-background:  #2d0922 !default;
+$console-color:  #fff !default;
 
-$navbar-border-radius: 0;
-$navbar-default-border: transparent;
-$navbar-height: 70px;
-$navbar-margin-bottom: 0;
+$pre-background: #f5f5f5 !default;
+$pre-color: #333 !default;
 
-$nav-link-padding: 10px 30px;
+$code-background: #f9f2f4 !default;
+$code-color: #e83e8c !default;
+
+
+$lead-font-size: 1.75rem !default;
+$lead-font-weight: 400 !default;
+
+$enable-smooth-scroll: false;
diff --git a/scss/main.scss b/scss/main_bs5.scss
similarity index 54%
rename from scss/main.scss
rename to scss/main_bs5.scss
index 514a67f1..88d9547d 100644
--- a/scss/main.scss
+++ b/scss/main_bs5.scss
@@ -1,150 +1,133 @@
 @import 'scss/variables';
-@import 'node_modules/bootstrap-sass/assets/stylesheets/bootstrap';
+@import 'node_modules/bootstrap/scss/bootstrap';
 
+// flush footer to bottom
+html {
+    height: 100%;
+}
 
 body {
+    min-height: 100%;
     position: relative;
+    padding-bottom: 40px;
 }
 
-pre {
-    margin-bottom: 20px;
-}
-
-
-code {
-    // Allow wrapping of code
-    white-space: normal;
-}
-
-.nowrap {
-    white-space: nowrap;
+footer {
+    // scss-lint:disable ImportantRule
+    position: absolute  !important;
+    right: 0;
+    bottom: 0;
+    left: 0;
 }
 
-h1,
-.page-header:first-child {
-    margin-top: 0;
-}
 
-// Navbar
+a {
+    text-decoration: none;
 
-.pc-navbar-brand {
-    padding: 13px 15px;
+    &:hover {
+        text-decoration: underline;
+    }
 }
 
-.logo {
-    height: 44px;
-    width: 44px;
-    display: block;
-    background: url('../logo.png');
+nav a:hover {
+    text-decoration: none;
 }
 
-.pc-navbar-collapse {
-    @include box-shadow(none);
-}
 
-.pc-navbar .btn {
-    margin: 18px 15px;
-    padding: 6px 12px;
+// additional spacing for sticky object
+.sticky-top {
+    top: $spacer * 3;
 }
 
 
-// Top shelf
-
-.top-shelf {
-    margin-bottom: 40px;
-    background: $pc-green-light;
-    color: white;
-
-    .container {
-        position: relative;
+// show anchor on hover
+h1,
+h2,
+h3 {
+    small {
+        display: none;
     }
 
-    .pc-logo-top-shelf {
-        float: right;
-        margin: -30px 20px 0 40px;
+    &:hover small {
+        display: inline;
     }
+}
 
-    h1 {
-        font-weight: bold;
-        margin: 40px 0 20px;
 
-        a {
-            color: $pc-yellow;
+// underline headline
+.page-header {
+    padding-bottom: 10px;
+    margin: 44px 0 22px;
+    border-bottom: $border-width solid $border-color;
 
-            &:hover {
-                text-decoration: none;
-            }
-        }
-    }
-
-    p {
-        margin-bottom: 10px;
-        font-size: $font-size-h3;
+    &:first-child {
+        margin-top: 0;
     }
 }
 
-@media (min-width: $screen-sm-min) and (max-width: $screen-sm-max) {
-    .top-shelf h1 {
-        font-size: $font-size-h2;
-        margin-top: 20px;
+// wrap table headers
+@include media-breakpoint-down(md) {
+    .table-bordered td:first-child {
+        background: $table-striped-bg;
+        border-width: 1px;
     }
-}
-
-
-// Sidebar
-
-.pc-sidenav.affix {
-    top: 40px;
-}
 
-@media (min-width: $screen-sm-min) and (max-width: $screen-sm-max) {
-    .pc-sidenav.affix {
-        width: 158px;
+    .table-bordered td {
+        display: block;
     }
 }
 
-@media (min-width: $screen-md-min) and (max-width: $screen-md-max) {
-    .pc-sidenav.affix {
-        width: 213px;
-    }
+// remove double spacing in tables
+td > :last-child {
+    margin: 0;
 }
 
 
-@media (min-width: $screen-lg-min) {
-    .pc-sidenav.affix {
-        width: 263px;
-    }
+// code boxes
+pre {
+    background-color: $pre-background;
+    color: $pre-color;
+    border: 1px solid darken($pre-background, 15%);
+    border-radius: $border-radius;
+    padding: 0.5rem;
 }
 
-
-// Footer
-
-.pc-footer {
-    margin-top: 40px;
-    background: $pc-green-dark;
-    color: white;
-    text-align: center;
-
-    .container {
-        padding: 40px;
+.highlight.pre-commit,
+.highlight.console {
+    pre {
+        background-color: $console-background;
+        color: $console-color;
+        border: 1px solid darken($console-background, 15%);
     }
 
-    a:hover {
-        color: white;
-    }
+    // pygments
+    // scss-lint:disable SelectorFormat
+    .-Color-BGRed { background-color: #c00; }
+    .-Color-BGGreen { background-color: #4e9a06; }
+    .-Color-Black-BGYellow { background-color: #c4a000; color: #2e3436; }
+    .-Color-Black-BGCyan { background-color: #06989a; color: #2e3436; }
+    .-Color-Faint { color: #ccc; }
+    .c1 { color: #06989a; }
+    .s { color: #8ae234; }
+    .s1 { color: #8ae234; }
+    .s2 { color: #8ae234; }
 }
 
-.page-hooks {
-    .top-shelf {
-        display: none;
-    }
+code {
+    // scss-lint:disable ImportantRule
+    color: $code-color !important;
+    background-color: $code-background;
+    padding: $kbd-padding-y $kbd-padding-x;
+    border-radius: $border-radius;
+}
 
-    .pc-main-content {
-        margin-top: 30px;
-    }
+// copyable
+.copyable img {
+    cursor: pointer;
 }
 
-// vs.css: https://github.com/richleland/pygments-css
+
+// https://github.com/richleland/pygments-css/blob/master/vs.css
 .highlight {
     .hll { background-color: #ffc; }
     .c { color: #008000; } /* Comment */
@@ -183,33 +166,3 @@ h1,
     .gi { color: #070; }
     .gd { color: #911; }
 }
-
-// pygments-pre-commit
-.highlight.pre-commit,
-.highlight.console {
-    pre { border: 0; background-color: #2d0922; color: #fff; }
-
-    // scss-lint:disable SelectorFormat
-    .-Color-BGRed { background-color: #c00; }
-    .-Color-BGGreen { background-color: #4e9a06; }
-    .-Color-Black-BGYellow { background-color: #c4a000; color: #2e3436; }
-    .-Color-Black-BGCyan { background-color: #06989a; color: #2e3436; }
-    .-Color-Faint { color: #ccc; }
-
-    .c1 { color: #06989a; }
-    .s { color: #8ae234; }
-    .s1 { color: #8ae234; }
-    .s2 { color: #8ae234; }
-}
-
-.copyable img { cursor: pointer; }
-
-@media (max-width: $screen-md-max) {
-    .table-bordered td:first-child {
-        background: #f5f5f5;
-    }
-
-    .table-bordered td {
-        display: block;
-    }
-}
diff --git a/sections/advanced.md b/sections/advanced.md
new file mode 100644
index 00000000..442dbff1
--- /dev/null
+++ b/sections/advanced.md
@@ -0,0 +1,887 @@
+## Running in migration mode
+
+By default, if you have existing hooks `pre-commit install` will install in a
+migration mode which runs both your existing hooks and hooks for pre-commit.
+To disable this behavior, pass `-f` / `--overwrite` to the `install` command.
+If you decide not to use pre-commit, `pre-commit uninstall` will
+restore your hooks to the state prior to installation.
+
+## Temporarily disabling hooks
+
+Not all hooks are perfect so sometimes you may need to skip execution of one
+or more hooks. pre-commit solves this by querying a `SKIP` environment
+variable. The `SKIP` environment variable is a comma separated list of hook
+ids. This allows you to skip a single hook instead of `--no-verify`ing the
+entire commit.
+
+```console
+$ SKIP=flake8 git commit -m "foo"
+```
+
+## Confining hooks to run at certain stages
+
+pre-commit supports many different types of `git` hooks (not just
+`pre-commit`!).
+
+Providers of hooks can select which git hooks they run on by setting the
+[`stages`](#hooks-stages) property in `.pre-commit-hooks.yaml` -- this can
+also be overridden by setting [`stages`](#config-stages) in
+`.pre-commit-config.yaml`.  If `stages` is not set in either of those places
+the default value will be pulled from the top-level
+[`default_stages`](#top_level-default_stages) option (which defaults to _all_
+stages).  By default, tools are enabled for [every hook type](#supported-git-hooks)
+that pre-commit supports.
+
+_new in 3.2.0_: The values of `stages` match the hook names.  Previously,
+`commit`, `push`, and `merge-commit` matched `pre-commit`, `pre-push`, and
+`pre-merge-commit` respectively.
+
+The `manual` stage (via `stages: [manual]`) is a special stage which will not
+be automatically triggered by any `git` hook -- this is useful if you want to
+add a tool which is not automatically run, but is run on demand using
+`pre-commit run --hook-stage manual [hookid]`.
+
+If you are authoring a tool, it is usually a good idea to provide an appropriate
+`stages` property.  For example a reasonable setting for a linter or code
+formatter would be `stages: [pre-commit, pre-merge-commit, pre-push, manual]`.
+
+To install `pre-commit` for particular git hooks, pass `--hook-type` to
+`pre-commit install`.  This can be specified multiple times such as:
+
+```console
+$ pre-commit install --hook-type pre-commit --hook-type pre-push
+pre-commit installed at .git/hooks/pre-commit
+pre-commit installed at .git/hooks/pre-push
+```
+
+Additionally, one can specify a default set of git hook types to be installed
+for by setting the top-level [`default_install_hook_types`](#top_level-default_install_hook_types).
+
+For example:
+
+```yaml
+default_install_hook_types: [pre-commit, pre-push, commit-msg]
+```
+
+```console
+$ pre-commit  install
+pre-commit installed at .git/hooks/pre-commit
+pre-commit installed at .git/hooks/pre-push
+pre-commit installed at .git/hooks/commit-msg
+```
+
+[anchor](__#pre-commit-during-commits)
+[anchor](__#pre-commit-during-merges)
+[anchor](__#pre-commit-during-clean-merges)
+[anchor](__#pre-commit-during-push)
+[anchor](__#pre-commit-for-commit-messages)
+[anchor](__#pre-commit-for-switching-branches)
+[anchor](__#pre-commit-for-rewriting)
+
+## Supported git hooks
+
+- [commit-msg](#commit-msg)
+- [post-checkout](#post-checkout)
+- [post-commit](#post-commit)
+- [post-merge](#post-merge)
+- [post-rewrite](#post-rewrite)
+- [pre-commit](#pre-commit)
+- [pre-merge-commit](#pre-merge-commit)
+- [pre-push](#pre-push)
+- [pre-rebase](#pre-rebase)
+- [prepare-commit-msg](#prepare-commit-msg)
+
+### commit-msg
+
+[git commit-msg docs](https://git-scm.com/docs/githooks#_commit_msg)
+
+`commit-msg` hooks will be passed a single filename -- this file contains the
+current contents of the commit message to be validated.  The commit will be
+aborted if there is a nonzero exit code.
+
+### post-checkout
+
+[git post-checkout docs](https://git-scm.com/docs/githooks#_post_checkout)
+
+post-checkout hooks run *after* a `checkout` has occurred and can be used to
+set up or manage state in the repository.
+
+`post-checkout` hooks do not operate on files so they must be set as
+`always_run: true` or they will always be skipped.
+
+environment variables:
+- `PRE_COMMIT_FROM_REF`: the first argument to the `post-checkout` git hook
+- `PRE_COMMIT_TO_REF`:  the second argument to the `post-checkout` git hook
+- `PRE_COMMIT_CHECKOUT_TYPE`: the third argument to the `post-checkout` git hook
+
+### post-commit
+
+[git post-commit docs](https://git-scm.com/docs/githooks#_post_commit)
+
+`post-commit` runs after the commit has already succeeded so it cannot be used
+to prevent the commit from happening.
+
+`post-commit` hooks do not operate on files so they must be set as
+`always_run: true` or they will always be skipped.
+
+### post-merge
+
+[git post-merge docs](https://git-scm.com/docs/githooks#_post_merge)
+
+`post-merge` runs after a successful `git merge`.
+
+`post-merge` hooks do not operate on files so they must be set as
+`always_run: true` or they will always be skipped.
+
+environment variables:
+- `PRE_COMMIT_IS_SQUASH_MERGE`: the first argument to the `post-merge` git hook.
+
+### post-rewrite
+
+[git post-rewrite docs](https://git-scm.com/docs/githooks#_post_rewrite)
+
+`post-rewrite` runs after a git command which modifies history such as
+`git commit --amend` or `git rebase`.
+
+`post-rewrite` hooks do not operate on files so they must be set as
+`always_run: true` or they will always be skipped.
+
+environment variables:
+- `PRE_COMMIT_REWRITE_COMMAND`: the first argument to the `post-rewrite` git hook.
+
+### pre-commit
+
+[git pre-commit docs](https://git-scm.com/docs/githooks#_pre_commit)
+
+`pre-commit` is triggered before the commit is finalized to allow checks on the
+code being committed.  Running hooks on unstaged changes can lead to both
+false-positives and false-negatives during committing.  pre-commit only runs
+on the staged contents of files by temporarily stashing the unstaged changes
+while running hooks.
+
+### pre-merge-commit
+
+[git pre-merge-commit docs](https://git-scm.com/docs/githooks#_pre_merge_commit)
+
+`pre-merge-commit` fires after a merge succeeds but before the merge commit is
+created.  This hook runs on all staged files from the merge.
+
+Note that you need to be using at least git 2.24 for this hook.
+
+### pre-push
+
+[git pre-push docs](https://git-scm.com/docs/githooks#_pre_push)
+
+`pre-push` is triggered on `git push`.
+
+environment variables:
+- `PRE_COMMIT_FROM_REF`: the revision that is being pushed to.
+- `PRE_COMMIT_TO_REF`: the local revision that is being pushed to the remote.
+- `PRE_COMMIT_REMOTE_NAME`: which remote is being pushed to (for example `origin`)
+- `PRE_COMMIT_REMOTE_URL`: the url of the remote that is being pushed to (for
+  example `git@github.com:pre-commit/pre-commit`)
+- `PRE_COMMIT_REMOTE_BRANCH`: the name of the remote branch to which we are
+   pushing (for example `refs/heads/target-branch`)
+- `PRE_COMMIT_LOCAL_BRANCH`: the name of the local branch that is being pushed
+  to the remote (for example `HEAD`)
+
+### pre-rebase
+
+_new in 3.2.0_
+
+[git pre-rebase docs](https://git-scm.com/docs/githooks#_pre_rebase)
+
+`pre-rebase` is triggered before a rebase occurs.  A hook failure can cancel a
+rebase from occurring.
+
+`pre-rebase` hooks do not operate on files so they must be set as
+`always_run: true` or they will always be skipped.
+
+environment variables:
+- `PRE_COMMIT_PRE_REBASE_UPSTREAM`: the first argument to the `pre-rebase` git hook
+- `PRE_COMMIT_PRE_REBASE_BRANCH`: the second argument to the `pre-rebase` git hook.
+
+### prepare-commit-msg
+
+[git prepare-commit-msg docs](https://git-scm.com/docs/githooks#_prepare_commit_msg)
+
+`prepare-commit-msg` hooks will be passed a single filename -- this file may
+be empty or it could contain the commit message from `-m` or from other
+templates.  `prepare-commit-msg` hooks can modify the contents of this file to
+change what will be committed.  A hook may want to check for `GIT_EDITOR=:` as
+this indicates that no editor will be launched.  If a hook exits nonzero, the
+commit will be aborted.
+
+environment variables:
+- `PRE_COMMIT_COMMIT_MSG_SOURCE`: the second argument to the
+  `prepare-commit-msg` git hook
+- `PRE_COMMIT_COMMIT_OBJECT_NAME`: the third argument to the
+  `prepare-commit-msg` git hook
+
+## Passing arguments to hooks
+
+Sometimes hooks require arguments to run correctly. You can pass static
+arguments by specifying the [`args`](#config-args) property in your `.pre-commit-config.yaml`
+as follows:
+
+```yaml
+-   repo: https://github.com/PyCQA/flake8
+    rev: 4.0.1
+    hooks:
+    -   id: flake8
+        args: [--max-line-length=131]
+```
+
+This will pass `--max-line-length=131` to `flake8`.
+
+### Arguments pattern in hooks
+
+If you are writing your own custom hook, your hook should expect to receive
+the [`args`](#config-args) value and then a list of staged files.
+
+For example, assuming a `.pre-commit-config.yaml`:
+
+```yaml
+-   repo: https://github.com/path/to/your/hook/repo
+    rev: badf00ddeadbeef
+    hooks:
+    -   id: my-hook-script-id
+        args: [--myarg1=1, --myarg1=2]
+```
+
+When you next run `pre-commit`, your script will be called:
+
+```
+path/to/script-or-system-exe --myarg1=1 --myarg1=2 dir/file1 dir/file2 file3
+```
+
+If the [`args`](#config-args) property is empty or not defined, your script will be called:
+
+```
+path/to/script-or-system-exe dir/file1 dir/file2 file3
+```
+
+When creating local hooks, there's no reason to put command arguments
+into [`args`](#config-args) as there is nothing which can override them --
+instead put your arguments directly in the hook [`entry`](#hooks-entry).
+
+For example:
+
+```yaml
+-   repo: local
+    hooks:
+    -   id: check-requirements
+        name: check requirements files
+        language: unsupported
+        entry: python -m scripts.check_requirements --compare
+        files: ^requirements.*\.txt$
+```
+
+## Repository local hooks
+
+Repository-local hooks are useful when:
+
+- The scripts are tightly coupled to the repository and it makes sense to
+  distribute the hook scripts with the repository.
+- Hooks require state that is only present in a built artifact of your
+  repository (such as your app's virtualenv for pylint).
+- The official repository for a linter doesn't have the pre-commit metadata.
+
+You can configure repository-local hooks by specifying the [`repo`](#repos-repo) as the
+sentinel `local`.
+
+local hooks can use any language which supports [`additional_dependencies`](#config-additional_dependencies)
+or [`docker_image`](#docker_image) / [`fail`](#fail) / [`pygrep`](#pygrep) / [`unsupported`](#unsupported) / [`unsupported_script`](#unsupported_script).
+This enables you to install things which previously would require a trivial
+mirror repository.
+
+A `local` hook must define [`id`](#hooks-id), [`name`](#hooks-name), [`language`](#hooks-language),
+[`entry`](#hooks-entry), and [`files`](#hooks-files) / [`types`](#hooks-types)
+as specified under [Creating new hooks](#new-hooks).
+
+Here's an example configuration with a few `local` hooks:
+
+```yaml
+-   repo: local
+    hooks:
+    -   id: pylint
+        name: pylint
+        entry: pylint
+        language: unsupported
+        types: [python]
+        require_serial: true
+    -   id: check-x
+        name: Check X
+        entry: ./bin/check-x.sh
+        language: unsupported_script
+        files: \.x$
+    -   id: scss-lint
+        name: scss-lint
+        entry: scss-lint
+        language: ruby
+        language_version: 2.1.5
+        types: [scss]
+        additional_dependencies: ['scss_lint:0.52.0']
+```
+
+## meta hooks
+
+`pre-commit` provides several hooks which are useful for checking the
+pre-commit configuration itself.  These can be enabled using `repo: meta`.
+
+```yaml
+-   repo: meta
+    hooks:
+    -   id: ...
+```
+
+The currently available `meta` hooks:
+
+```table
+=r=
+    =c= [`check-hooks-apply`](_#meta-check_hooks_apply)
+    =c= ensures that the configured hooks apply to at least one file in the
+        repository.
+=r=
+    =c= [`check-useless-excludes`](_#meta-check_useless_excludes)
+    =c= ensures that `exclude` directives apply to _any_ file in the
+        repository.
+=r=
+    =c= [`identity`](_#meta-identity)
+    =c= a simple hook which prints all arguments passed to it, useful for
+        debugging.
+```
+
+## `pre-commit hazmat`
+
+"hazardous materials"
+
+pre-commit provides a few `entry` prefix "helpers" for unusual situations.
+
+in case it's not clear, using these is _usually_ a bad idea.
+
+_note_: hazmat helpers do not work on languages which adjust `entry` (`docker`
+/ `docker_image` / `fail` / `julia` / `pygrep` / `r` / `unsupported_script`).
+
+### `pre-commit hazmat cd`
+
+_new in 4.5.0_
+
+for "monorepo" usage one can use this to target a subdirectory.
+
+this entry prefix will cd to the target subdir and adjust filename arguments
+
+example usage:
+
+```yaml
+# recommended:
+# minimum_pre_commit_version: 4.5.0
+repos:
+-   repo: ...
+    rev: ...
+    hooks:
+    -   id: example
+        alias: example-repo1
+        name: example (repo1)
+        files: ^repo1/
+        # important! ends with `--`
+        # important! copy `args: [...]` to entry and blank out `args: []`
+        entry: pre-commit hazmat cd repo1 example-bin --arg1 --
+        args: []
+
+    -   id: example
+        alias: example-repo2
+        name: example (repo2)
+        files: ^repo2/
+        entry: pre-commit hazmat cd repo2 example-bin --arg1 --
+        args: []
+
+    # ... etc.
+```
+
+### `pre-commit hazmat ignore-exit-code`
+
+_new in 4.5.0_
+
+it's a bad idea to introduce warning noise but this gives you a way to do it.
+
+example:
+
+```yaml
+# recommended:
+# minimum_pre_commit_version: 4.5.0
+repos:
+-   repo: ...
+    rev: ...
+    hooks:
+    -   id: example
+        # important! copy `args: [...]` to entry and blank out `args: []`
+        entry: pre-commit hazmat ignore-exit-code example-bin --arg1 --
+        args: []
+        # otherwise the output will always be hidden
+        verbose: true
+```
+
+### `pre-commit hazmat n1`
+
+_new in 4.5.0_
+
+some hooks only take one filename argument.  this runs them one at a time
+(which is super slow!)
+
+example:
+
+```yaml
+# recommended:
+# minimum_pre_commit_version: 4.5.0
+repos:
+-   repo: ...
+    rev: ...
+    hooks:
+    -   id: example
+        # important! ends with `--`
+        # important! copy `args: [...]` to entry and blank out `args: []`
+        entry: pre-commit hazmat n1 example-bin --arg1 --
+        args: []
+```
+
+## automatically enabling pre-commit on repositories
+
+`pre-commit init-templatedir` can be used to set up a skeleton for `git`'s
+`init.templateDir` option.  This means that any newly cloned repository will
+automatically have the hooks set up without the need to run
+`pre-commit install`.
+
+To configure, first set `git`'s `init.templateDir` -- in this example I'm
+using `~/.git-template` as my template directory.
+
+```console
+$ git config --global init.templateDir ~/.git-template
+$ pre-commit init-templatedir ~/.git-template
+pre-commit installed at /home/asottile/.git-template/hooks/pre-commit
+```
+
+Now whenever you clone a pre-commit enabled repo, the hooks will already be
+set up!
+
+```pre-commit
+$ git clone -q git@github.com:asottile/pyupgrade
+$ cd pyupgrade
+$ git commit --allow-empty -m 'Hello world!'
+Check docstring is first.............................(no files to check)Skipped
+Check Yaml...........................................(no files to check)Skipped
+Debug Statements (Python)............................(no files to check)Skipped
+...
+```
+
+`init-templatedir` uses the `--allow-missing-config` option from
+`pre-commit install` so repos without a config will be skipped:
+
+```console
+$ git init sample
+Initialized empty Git repository in /tmp/sample/.git/
+$ cd sample
+$ git commit --allow-empty -m 'Initial commit'
+`.pre-commit-config.yaml` config file not found. Skipping `pre-commit`.
+[main (root-commit) d1b39c1] Initial commit
+```
+
+To still require opt-in, but prompt the user to set up pre-commit use a
+template hook as follows (for example in `~/.git-template/hooks/pre-commit`).
+
+```bash
+#!/usr/bin/env bash
+if [ -f .pre-commit-config.yaml ]; then
+    echo 'pre-commit configuration detected, but `pre-commit install` was never run' 1>&2
+    exit 1
+fi
+```
+
+With this, a forgotten `pre-commit install` produces an error on commit:
+
+```console
+$ git clone -q https://github.com/asottile/pyupgrade
+$ cd pyupgrade/
+$ git commit -m 'foo'
+pre-commit configuration detected, but `pre-commit install` was never run
+```
+
+## Filtering files with types
+
+Filtering with `types` provides several advantages over traditional filtering
+with `files`.
+
+- no error-prone regular expressions
+- files can be matched by their shebang (even when extensionless)
+- symlinks / submodules can be easily ignored
+
+`types` is specified per hook as an array of tags.  The tags are discovered
+through a set of heuristics by the
+[identify](https://github.com/pre-commit/identify) library.  `identify` was
+chosen as it is a small portable pure python library.
+
+Some of the common tags you'll find from identify:
+
+- `file`
+- `symlink`
+- `directory` - in the context of pre-commit this will be a submodule
+- `executable` - whether the file has the executable bit set
+- `text` - whether the file looks like a text file
+- `binary` - whether the file looks like a binary file
+- [tags by extension / naming convention](https://github.com/pre-commit/identify/blob/main/identify/extensions.py)
+- [tags by shebang (`#!`)](https://github.com/pre-commit/identify/blob/main/identify/interpreters.py)
+
+To discover the type of any file on disk, you can use `identify`'s cli:
+
+```console
+$ identify-cli setup.py
+["file", "non-executable", "python", "text"]
+$ identify-cli some-random-file
+["file", "non-executable", "text"]
+$ identify-cli --filename-only some-random-file; echo $?
+1
+```
+
+If a file extension you use is not supported, please
+[submit a pull request](https://github.com/pre-commit/identify)!
+
+`types`, `types_or`, and `files` are evaluated together with `AND` when
+filtering.  Tags within `types` are also evaluated using `AND`.
+
+Tags within `types_or` are evaluated using `OR`.
+
+For example:
+
+```yaml
+    files: ^foo/
+    types: [file, python]
+```
+
+will match a file `foo/1.py` but will not match `setup.py`.
+
+Another example:
+
+```yaml
+    files: ^foo/
+    types_or: [javascript, jsx, ts, tsx]
+```
+
+will match any of `foo/bar.js` / `foo/bar.jsx` / `foo/bar.ts` / `foo/bar.tsx`
+but not `baz.js`.
+
+If you want to match a file path that isn't included in a `type` when using an
+existing hook you'll need to revert back to `files` only matching by overriding
+the `types` setting.  Here's an example of using `check-json` against non-json
+files:
+
+```yaml
+    -   id: check-json
+        types: [file]  # override `types: [json]`
+        files: \.(json|myext)$
+```
+
+Files can also be matched by shebang.  With `types: python`, an `exe` starting
+with `#!/usr/bin/env python3` will also be matched.
+
+As with `files` and `exclude`, you can also exclude types if necessary using
+`exclude_types`.
+
+## Regular expressions
+
+The patterns for `files` and `exclude` are python
+[regular expressions](https://docs.python.org/3/library/re.html#regular-expression-syntax)
+and are matched with [`re.search`](https://docs.python.org/3/library/re.html#re.search).
+
+As such, you can use any of the features that python regexes support.
+
+If you find that your regular expression is becoming unwieldy due to a long
+list of excluded / included things, you may find a
+[verbose](https://docs.python.org/3/library/re.html#re.VERBOSE) regular
+expression useful.  One can enable this with yaml's multiline literals and
+the `(?x)` regex flag.
+
+```yaml
+# ...
+    -   id: my-hook
+        exclude: |
+            (?x)^(
+                path/to/file1.py|
+                path/to/file2.py|
+                path/to/file3.py
+            )$
+```
+
+## Overriding language version
+
+Sometimes you only want to run the hooks on a specific version of the
+language. For each language, they default to using the system installed
+language (So for example if I’m running `python3.7` and a hook specifies
+`python`, pre-commit will run the hook using `python3.7`). Sometimes you
+don’t want the default system installed version so you can override this on a
+per-hook basis by setting the [`language_version`](#config-language_version).
+
+```yaml
+-   repo: https://github.com/pre-commit/mirrors-scss-lint
+    rev: v0.54.0
+    hooks:
+    -   id: scss-lint
+        language_version: 2.1.5
+```
+
+This tells pre-commit to use ruby `2.1.5` to run the `scss-lint` hook.
+
+Valid values for specific languages are listed below:
+- python: Whatever system installed python interpreters you have. The value of
+  this argument is passed as the `-p` to `virtualenv`.
+    - on windows the
+      [pep394](https://www.python.org/dev/peps/pep-0394/) name will be
+      translated into a py launcher call for portability.  So continue to use
+      names like `python3` (`py -3`) or `python3.6` (`py -3.6`) even on
+      windows.
+- node: See [nodeenv](https://github.com/ekalinin/nodeenv#advanced).
+- ruby: See [ruby-build](https://github.com/sstephenson/ruby-build/tree/master/share/ruby-build).
+- rust: `language_version` is passed to `rustup`
+- _new in 3.0.0_ golang: use the versions on [go.dev/dl](https://go.dev/dl/) such as `1.19.5`
+
+you can set [`default_language_version`](#top_level-default_language_version)
+at the [top level](#pre-commit-configyaml---top-level) in your configuration to
+control the default versions across all hooks of a language.
+
+```yaml
+default_language_version:
+    # force all unspecified python hooks to run python3
+    python: python3
+    # force all unspecified ruby hooks to run ruby 2.1.5
+    ruby: 2.1.5
+```
+
+## badging your repository
+
+you can add a badge to your repository to show your contributors / users that
+you use pre-commit!
+
+[![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit)](https://github.com/pre-commit/pre-commit)
+
+- Markdown:
+
+  ```md#copyable
+  [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit)](https://github.com/pre-commit/pre-commit)
+  ```
+
+- HTML:
+
+  ```html#copyable
+  <a href="https://github.com/pre-commit/pre-commit"><img src="https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit" alt="pre-commit" style="max-width:100%;"></a>
+  ```
+
+- reStructuredText:
+
+  ```rst#copyable
+  .. image:: https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit
+     :target: https://github.com/pre-commit/pre-commit
+     :alt: pre-commit
+  ```
+
+- AsciiDoc:
+
+  ```#copyable
+  image:https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit[pre-commit, link=https://github.com/pre-commit/pre-commit]
+  ```
+
+## Usage in continuous integration
+
+pre-commit can also be used as a tool for continuous integration.  For
+instance, adding `pre-commit run --all-files` as a CI step will ensure
+everything stays in tip-top shape.  To check only files which have changed,
+which may be faster, use something like
+`pre-commit run --from-ref origin/HEAD --to-ref HEAD`
+
+## Managing CI Caches
+
+`pre-commit` by default places its repository store in `~/.cache/pre-commit`
+-- this can be configured in two ways:
+
+- `PRE_COMMIT_HOME`: if set, pre-commit will use that location instead.
+- `XDG_CACHE_HOME`: if set, pre-commit will use `$XDG_CACHE_HOME/pre-commit`
+  following the [XDG Base Directory Specification].
+
+[XDG Base Directory Specification]: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
+
+### pre-commit.ci example
+
+no additional configuration is needed to run in [pre-commit.ci]!
+
+pre-commit.ci also has the following benefits:
+
+- it's faster than other free CI solutions
+- it will autofix pull requests
+- it will periodically autoupdate your configuration
+
+[![pre-commit.ci speed comparison](https://raw.githubusercontent.com/pre-commit-ci-demo/demo/main/img/2020-12-15_noop.svg)](https://github.com/pre-commit-ci-demo/demo#results)
+
+[pre-commit.ci]: https://pre-commit.ci
+
+### appveyor example
+
+```yaml
+cache:
+- '%USERPROFILE%\.cache\pre-commit'
+```
+
+### azure pipelines example
+
+note: azure pipelines uses immutable caches so the python version and
+`.pre-commit-config.yaml` hash must be included in the cache key.  for a
+repository template, see [asottile@job--pre-commit.yml].
+
+[asottile@job--pre-commit.yml]: https://github.com/asottile/azure-pipeline-templates/blob/main/job--pre-commit.yml
+
+```yaml
+jobs:
+- job: precommit
+
+  # ...
+
+  variables:
+    PRE_COMMIT_HOME: $(Pipeline.Workspace)/pre-commit-cache
+
+  steps:
+
+  # ...
+
+  - script: echo "##vso[task.setvariable variable=PY]$(python -VV)"
+  - task: CacheBeta@0
+    inputs:
+      key: pre-commit | .pre-commit-config.yaml | "$(PY)"
+      path: $(PRE_COMMIT_HOME)
+```
+
+### circleci example
+
+like [azure pipelines](#azure-pipelines-example), circleci also uses immutable
+caches:
+
+```yaml
+  steps:
+  - run:
+    command: |
+      cp .pre-commit-config.yaml pre-commit-cache-key.txt
+      python --version --version >> pre-commit-cache-key.txt
+  - restore_cache:
+    keys:
+    - v1-pc-cache-{{ checksum "pre-commit-cache-key.txt" }}
+
+  # ...
+
+  - save_cache:
+    key: v1-pc-cache-{{ checksum "pre-commit-cache-key.txt" }}
+    paths:
+      - ~/.cache/pre-commit
+```
+
+(source: [@chriselion])
+
+[@chriselion]: https://github.com/Unity-Technologies/ml-agents/pull/3094/files#diff-1d37e48f9ceff6d8030570cd36286a61
+
+### github actions example
+
+**see the [official pre-commit github action]**
+
+[official pre-commit github action]: https://github.com/pre-commit/action
+
+like [azure pipelines](#azure-pipelines-example), github actions also uses
+immutable caches:
+
+```yaml
+    - name: set PY
+      run: echo "PY=$(python -VV | sha256sum | cut -d' ' -f1)" >> $GITHUB_ENV
+    - uses: actions/cache@v3
+      with:
+        path: ~/.cache/pre-commit
+        key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }}
+```
+
+### gitlab CI example
+
+See the [Gitlab caching best practices](https://docs.gitlab.com/ee/ci/caching/#good-caching-practices) to fine tune the cache scope.
+
+```yaml
+my_job:
+  variables:
+    PRE_COMMIT_HOME: ${CI_PROJECT_DIR}/.cache/pre-commit
+  cache:
+    paths:
+      - ${PRE_COMMIT_HOME}
+```
+
+pre-commit's cache requires to be served from a constant location between the different builds. This isn't the default when using k8s runners
+on GitLab. In case you face the error `InvalidManifestError`, set `builds_dir` to something static e.g `builds_dir = "/builds"` in your `[[runner]]` config
+
+### travis-ci example
+
+```yaml
+cache:
+  directories:
+  - $HOME/.cache/pre-commit
+```
+
+## Usage with tox
+
+[tox](https://tox.readthedocs.io/) is useful for configuring test / CI tools
+such as pre-commit.  One feature of `tox>=2` is it will clear environment
+variables such that tests are more reproducible.  Under some conditions,
+pre-commit requires a few environment variables and so they must be
+allowed to be passed through.
+
+When cloning repos over ssh (`repo: git@github.com:...`), `git` requires the
+`SSH_AUTH_SOCK` variable and will otherwise fail:
+
+```pre-commit
+[INFO] Initializing environment for git@github.com:pre-commit/pre-commit-hooks.
+An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'fetch', 'origin', '--tags')
+return code: 128
+expected return code: 0
+stdout: (none)
+stderr:
+    git@github.com: Permission denied (publickey).
+    fatal: Could not read from remote repository.
+
+    Please make sure you have the correct access rights
+    and the repository exists.
+
+Check the log at /home/asottile/.cache/pre-commit/pre-commit.log
+```
+
+Add the following to your tox testenv:
+
+```ini
+[testenv]
+passenv = SSH_AUTH_SOCK
+```
+
+Likewise, when cloning repos over http / https
+(`repo: https://github.com:...`), you might be working behind a corporate
+http(s) proxy server, in which case `git` requires the `http_proxy`,
+`https_proxy` and `no_proxy` variables to be set, or the clone may fail:
+
+```ini
+[testenv]
+passenv = http_proxy https_proxy no_proxy
+```
+
+## Using the latest version for a repository
+
+`pre-commit` configuration aims to give a repeatable and fast experience and
+therefore intentionally doesn't provide facilities for "unpinned latest
+version" for hook repositories.
+
+Instead, `pre-commit` provides tools to make it easy to upgrade to the
+latest versions with [`pre-commit autoupdate`](#pre-commit-autoupdate).  If
+you need the absolute latest version of a hook (instead of the latest tagged
+version), pass the `--bleeding-edge` parameter to `autoupdate`.
+
+`pre-commit` assumes that the value of [`rev`](#repos-rev) is an immutable ref (such as a
+tag or SHA) and will cache based on that.  Using a branch name (or `HEAD`) for
+the value of [`rev`](#repos-rev) is not supported and will only represent the state of
+that mutable ref at the time of hook installation (and will *NOT* update
+automatically).
diff --git a/sections/cli.md b/sections/cli.md
new file mode 100644
index 00000000..a644a0ae
--- /dev/null
+++ b/sections/cli.md
@@ -0,0 +1,235 @@
+All pre-commit commands take the following options:
+
+- `--color {auto,always,never}`: whether to use color in output.
+  Defaults to `auto`.  can be overridden by using
+  `PRE_COMMIT_COLOR={auto,always,never}` or disabled using `TERM=dumb`.
+- `-c CONFIG`, `--config CONFIG`: path to alternate config file
+- `-h`, `--help`: show help and available options.
+
+`pre-commit` exits with specific codes:
+- `1`: a detected / expected error
+- `3`: an unexpected error
+- `130`: the process was interrupted by `^C`
+
+## pre-commit autoupdate [options] #pre-commit-autoupdate
+
+Auto-update pre-commit config to the latest repos' versions.
+
+Options:
+
+- `--bleeding-edge`: update to the bleeding edge of the default branch instead
+  of the latest tagged version (the default behaviour).
+- `--freeze`: Store "frozen" hashes in [`rev`](#repos-rev) instead of tag names.
+- `--repo REPO`: Only update this repository. This option may be specified
+  multiple times.
+- `-j` / `--jobs`: _new in 3.3.0_ Number of threads to use (default: 1).
+
+Here are some sample invocations using this `.pre-commit-config.yaml`:
+
+```yaml
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v2.1.0
+    hooks:
+    -   id: trailing-whitespace
+-   repo: https://github.com/asottile/pyupgrade
+    rev: v1.25.0
+    hooks:
+    -   id: pyupgrade
+        args: [--py36-plus]
+```
+
+```console
+$ : default: update to latest tag on default branch
+$ pre-commit autoupdate  # by default: pick tags
+Updating https://github.com/pre-commit/pre-commit-hooks ... updating v2.1.0 -> v2.4.0.
+Updating https://github.com/asottile/pyupgrade ... updating v1.25.0 -> v1.25.2.
+$ grep rev: .pre-commit-config.yaml
+    rev: v2.4.0
+    rev: v1.25.2
+```
+
+```console
+$ : update a specific repository to the latest revision of the default branch
+$ pre-commit autoupdate --bleeding-edge --repo https://github.com/pre-commit/pre-commit-hooks
+Updating https://github.com/pre-commit/pre-commit-hooks ... updating v2.1.0 -> 5df1a4bf6f04a1ed3a643167b38d502575e29aef.
+$ grep rev: .pre-commit-config.yaml
+    rev: 5df1a4bf6f04a1ed3a643167b38d502575e29aef
+    rev: v1.25.0
+```
+
+```console
+$ : update to frozen versions
+$ pre-commit autoupdate --freeze
+Updating https://github.com/pre-commit/pre-commit-hooks ... updating v2.1.0 -> v2.4.0 (frozen).
+Updating https://github.com/asottile/pyupgrade ... updating v1.25.0 -> v1.25.2 (frozen).
+$ grep rev: .pre-commit-config.yaml
+    rev: 0161422b4e09b47536ea13f49e786eb3616fe0d7  # frozen: v2.4.0
+    rev: 34a269fd7650d264e4de7603157c10d0a9bb8211  # frozen: v1.25.2
+```
+
+pre-commit will preferentially pick tags containing a `.` if there are ties.
+
+## pre-commit clean [options] #pre-commit-clean
+
+Clean out cached pre-commit files.
+
+Options: (no additional options)
+
+## pre-commit gc [options] #pre-commit-gc
+
+Clean unused cached repos.
+
+`pre-commit` keeps a cache of installed hook repositories which grows over
+time.  This command can be run periodically to clean out unused repos from
+the cache directory.
+
+Options: (no additional options)
+
+## pre-commit init-templatedir DIRECTORY [options] #pre-commit-init-templatedir
+
+Install hook script in a directory intended for use with
+`git config init.templateDir`.
+
+Options:
+
+- `-t HOOK_TYPE, --hook-type HOOK_TYPE`:
+  which hook type to install.
+
+Some example useful invocations:
+
+```bash
+git config --global init.templateDir ~/.git-template
+pre-commit init-templatedir ~/.git-template
+```
+
+For Windows cmd.exe use `%HOMEPATH%` instead of `~`:
+
+```batch
+pre-commit init-templatedir %HOMEPATH%\.git-template
+```
+
+For Windows PowerShell use `$HOME` instead of `~`:
+
+```powershell
+pre-commit init-templatedir $HOME\.git-template
+```
+
+Now whenever a repository is cloned or created, it will have the hooks set up
+already!
+
+## pre-commit install [options] #pre-commit-install
+
+Install the pre-commit script.
+
+Options:
+
+- `-f`, `--overwrite`: Replace any existing git hooks with the pre-commit
+  script.
+- `--install-hooks`: Also install environments for all available hooks now
+  (rather than when they are first executed). See [`pre-commit
+  install-hooks`](#pre-commit-install-hooks).
+- `-t HOOK_TYPE, --hook-type HOOK_TYPE`:
+  Specify which hook type to install.
+- `--allow-missing-config`: Hook scripts will permit a missing configuration
+  file.
+
+Some example useful invocations:
+
+- `pre-commit install`: Default invocation. Installs the hook scripts
+   alongside any existing git hooks.
+- `pre-commit install --install-hooks --overwrite`: Idempotently replaces
+   existing git hook scripts with pre-commit, and also installs hook
+   environments.
+
+`pre-commit install` will install hooks from
+[`default_install_hook_types`](#top_level-default_install_hook_types) if
+`--hook-type` is not specified on the command line.
+
+## pre-commit install-hooks [options] #pre-commit-install-hooks
+
+Install all missing environments for the available hooks. Unless this command or
+`install --install-hooks` is executed, each hook's environment is created the
+first time the hook is called.
+
+Each hook is initialized in a separate environment appropriate to the language
+the hook is written in. See [supported languages](#supported-languages).
+
+This command does not install the pre-commit script. To install the script along with
+the hook environments in one command, use `pre-commit install --install-hooks`.
+
+Options: (no additional options)
+
+## pre-commit migrate-config [options] #pre-commit-migrate-config
+
+Migrate list configuration to the new map configuration format.
+
+Options: (no additional options)
+
+## pre-commit run [hook-id] [options] #pre-commit-run
+
+Run hooks.
+
+Options:
+
+- `[hook-id]`: specify a single hook-id to run only that hook.
+- `-a`, `--all-files`: run on all the files in the repo.
+- `--files [FILES [FILES ...]]`: specific filenames to run hooks on.
+- `--from-ref FROM_REF` + `--to-ref TO_REF`: run against the files changed
+  between `FROM_REF...TO_REF` in git.
+- `--hook-stage STAGE`: select a [`stage` to run](#confining-hooks-to-run-at-certain-stages).
+- `--show-diff-on-failure`: when hooks fail, run `git diff` directly afterward.
+- `-v`, `--verbose`: produce hook output independent of success.  Include hook
+  ids in output.
+
+Some example useful invocations:
+- `pre-commit run`: this is what pre-commit runs by default when committing.
+  This will run all hooks against currently staged files.
+- `pre-commit run --all-files`: run all the hooks against all the files.  This
+  is a useful invocation if you are using pre-commit in CI.
+- `pre-commit run flake8`: run the `flake8` hook against all staged files.
+- `git ls-files -- '*.py' | xargs pre-commit run --files`: run all hooks
+  against all `*.py` files in the repository.
+- `pre-commit run --from-ref HEAD^^^ --to-ref HEAD`: run against the files that
+  have changed between `HEAD^^^` and `HEAD`.  This form is useful when
+  leveraged in a pre-receive hook.
+
+## pre-commit sample-config [options] #pre-commit-sample-config
+
+Produce a sample `.pre-commit-config.yaml`.
+
+Options: (no additional options)
+
+## pre-commit try-repo REPO [options] #pre-commit-try-repo
+
+Try the hooks in a repository, useful for developing new hooks.
+`try-repo` can also be used for testing out a repository before adding it to
+your configuration.  `try-repo` prints a configuration it generates based on
+the remote hook repository before running the hooks.
+
+Options:
+
+- `REPO`: required clonable hooks repository.  Can be a local path on
+  disk.
+- `--ref REF`: Manually select a ref to run against, otherwise the `HEAD`
+  revision will be used.
+- `pre-commit try-repo` also supports all available options for
+  [`pre-commit run`](#pre-commit-run).
+
+Some example useful invocations:
+- `pre-commit try-repo https://github.com/pre-commit/pre-commit-hooks`: runs
+  all the hooks in the latest revision of `pre-commit/pre-commit-hooks`.
+- `pre-commit try-repo ../path/to/repo`: run all the hooks in a repository on
+  disk.
+- `pre-commit try-repo ../pre-commit-hooks flake8`: run only the `flake8` hook
+  configured in a local `../pre-commit-hooks` repository.
+- See [`pre-commit run`](#pre-commit-run) for more useful `run` invocations
+  which are also supported by `pre-commit try-repo`.
+
+## pre-commit uninstall [options] #pre-commit-uninstall
+
+Uninstall the pre-commit script.
+
+Options:
+
+- `-t HOOK_TYPE, --hook-type HOOK_TYPE`: which hook type to uninstall.
diff --git a/sections/contributing.md b/sections/contributing.md
new file mode 100644
index 00000000..46096952
--- /dev/null
+++ b/sections/contributing.md
@@ -0,0 +1,37 @@
+We’re looking to grow the project and get more contributors especially to
+support more languages/versions. We’d also like to get the
+.pre-commit-hooks.yaml files added to popular linters without maintaining
+forks / mirrors.
+
+Feel free to submit bug reports, pull requests, and feature requests.
+
+## Sponsoring
+
+If you or your company would like to support the development of pre-commit one
+can contribute in the following ways:
+
+- [GitHub Sponsors (asottile)](https://github.com/sponsors/asottile)
+- [Open Collective](https://opencollective.com/pre-commit)
+
+## Getting help
+
+There are several ways to get help for pre-commit:
+
+- Ask a question on [stackoverflow tagged `<kbd>pre-commit.com</kbd>`]
+- Create an issue on [pre-commit/pre-commit]
+- Ask in the #pre-commit channel in [asottile's twitch discord]
+
+[stackoverflow tagged `<kbd>pre-commit.com</kbd>`]: https://stackoverflow.com/questions/tagged/pre-commit.com
+[pre-commit/pre-commit]: https://github.com/pre-commit/pre-commit/issues/
+[asottile's twitch discord]: https://discord.gg/xDKGPaW
+
+
+## Contributors
+
+- website by [Molly Finkle](https://github.com/mfnkl)
+- created by [Anthony Sottile](https://github.com/asottile)
+- core developers: [Ken Struys](https://github.com/struys),
+  [Chris Kuehl](https://github.com/chriskuehl)
+- [framework contributors](https://github.com/pre-commit/pre-commit/graphs/contributors)
+- [core hook contributors](https://github.com/pre-commit/pre-commit-hooks/graphs/contributors)
+- and users like you!
diff --git a/sections/hooks.md b/sections/hooks.md
new file mode 100644
index 00000000..a045f6f6
--- /dev/null
+++ b/sections/hooks.md
@@ -0,0 +1,167 @@
+## featured hooks
+
+here are a few hand-picked repositories which provide pre-commit integrations.
+
+these are fairly popular and are generally known to work well in most setups!
+
+_this list is not intended to be exhaustive_
+
+provided by the pre-commit team:
+- [pre-commit/pre-commit-hooks]: a handful of language-agnostic hooks which
+  are universally useful!
+- [pre-commit/pygrep-hooks]: a few quick regex-based hooks for a handful of
+  quick syntax checks
+- [pre-commit/sync-pre-commit-deps]: sync pre-commit hook dependencies based
+  on other installed hooks
+- [pre-commit/mirrors-*]: pre-commit mirrors of a handful of popular tools
+
+[pre-commit/pre-commit-hooks]: https://github.com/pre-commit/pre-commit-hooks
+[pre-commit/pygrep-hooks]: https://github.com/pre-commit/pygrep-hooks
+[pre-commit/sync-pre-commit-deps]: https://github.com/pre-commit/sync-pre-commit-deps
+[pre-commit/mirrors-*]: https://github.com/orgs/pre-commit/repositories?language=&q=%22mirrors-%22+archived%3AFalse&sort=
+
+for python projects:
+- [asottile/pyupgrade]: automatically upgrade syntax for newer versions of the
+  language
+- [asottile/(others)]: a few other repos by the pre-commit creator
+- [psf/black]: The uncompromising Python code formatter
+- [hhatto/autopep8]: automatically fixes PEP8 violations
+- [astral-sh/ruff-pre-commit]: the ruff linter and formatter for python
+- [google/yapf]: a highly configurable python formatter
+- [PyCQA/flake8]: a linter framework for python
+- [PyCQA/isort]: an import sorter for python
+- [PyCQA/(others)]: a few other python code quality tools
+- [adamchainz/django-upgrade]: automatically upgrade your Django project code
+
+[asottile/pyupgrade]: https://github.com/asottile/pyupgrade
+[asottile/(others)]: https://sourcegraph.com/search?q=context:global+file:%5E%5C.pre-commit-hooks%5C.yaml%24+repo:%5Egithub.com/asottile/
+[psf/black]: https://github.com/psf/black
+[hhatto/autopep8]: https://github.com/hhatto/autopep8
+[astral-sh/ruff-pre-commit]: https://github.com/astral-sh/ruff-pre-commit
+[google/yapf]: https://github.com/google/yapf
+[PyCQA/flake8]: https://github.com/PyCQA/flake8
+[PyCQA/isort]: https://github.com/PyCQA/isort
+[PyCQA/(others)]: https://sourcegraph.com/search?q=context:global+file:%5E%5C.pre-commit-hooks%5C.yaml%24+repo:%5Egithub.com/PyCQA/
+[adamchainz/django-upgrade]: https://github.com/adamchainz/django-upgrade
+
+for shell scripts:
+- [shellcheck-py/shellcheck-py]: runs shellcheck on your scripts
+- [openstack/bashate]: code style enforcement for bash programs
+
+[shellcheck-py/shellcheck-py]: https://github.com/shellcheck-py/shellcheck-py
+[openstack/bashate]: https://github.com/openstack/bashate
+
+for the web:
+- [biomejs/pre-commit]: a fast formatter / fixer written in rust
+- [standard/standard]: linter / fixer
+- [oxipng/oxipng]: optimize png files
+
+[biomejs/pre-commit]: https://github.com/biomejs/pre-commit
+[standard/standard]: https://github.com/standard/standard
+[oxipng/oxipng]: https://github.com/oxipng/oxipng
+
+for configuration files:
+- [python-jsonschema/check-jsonschema]: check many common configurations with jsonschema
+- [rhysd/actionlint]: lint your GitHub Actions workflow files
+- [google/yamlfmt]: a formatter for yaml files
+- [adrienverge/yamllint]: a linter for YAML files
+
+[python-jsonschema/check-jsonschema]: https://github.com/python-jsonschema/check-jsonschema
+[rhysd/actionlint]: https://github.com/rhysd/actionlint
+[google/yamlfmt]: https://github.com/google/yamlfmt
+[adrienverge/yamllint]: https://github.com/adrienverge/yamllint
+
+for text / docs / prose:
+- [crate-ci/typos]: find and fix common typographical errors
+- [thlorenz/doctoc]: generate a table-of-contents in markdown files
+- [amperser/proselint]: A linter for prose.
+- [markdownlint/markdownlint]: a Markdown lint tool in Ruby
+- [DavidAnson/markdownlint-cli2]: a Markdown lint tool in Node
+- [codespell-project/codespell]: check code for common misspellings
+
+[crate-ci/typos]: https://github.com/crate-ci/typos
+[thlorenz/doctoc]: https://github.com/thlorenz/doctoc
+[amperser/proselint]: https://github.com/amperser/proselint
+[markdownlint/markdownlint]: https://github.com/markdownlint/markdownlint
+[DavidAnson/markdownlint-cli2]: https://github.com/DavidAnson/markdownlint-cli2
+[codespell-project/codespell]: https://github.com/codespell-project/codespell
+
+for linting commit messages:
+- [jorisroovers/gitlint]
+- [commitizen-tools/commitizen]
+
+[jorisroovers/gitlint]: https://github.com/jorisroovers/gitlint
+[commitizen-tools/commitizen]: https://github.com/commitizen-tools/commitizen
+
+for secret scanning / security:
+- [gitleaks/gitleaks]
+- [trufflesecurity/truffleHog]
+- [thoughtworks/talisman]
+
+[gitleaks/gitleaks]: https://github.com/gitleaks/gitleaks
+[trufflesecurity/truffleHog]: https://github.com/trufflesecurity/truffleHog
+[thoughtworks/talisman]: https://github.com/thoughtworks/talisman
+
+for other programming languages:
+- [realm/SwiftLint]: enforce Swift style and conventions
+- [nicklockwood/SwiftFormat]: a formatter for Swift
+- [AleksaC/terraform-py]: format and validate terraform syntax
+- [rubocop/rubocop]: static analysis and formatting for Ruby
+- [bufbuild/buf]: tooling for Protocol Buffers
+- [sqlfluff/sqlfluff]: a modular linter and auto formatter for SQL
+- [aws-cloudformation/cfn-lint]: aws CloudFormation linter
+- [google/go-jsonnet]: linter / formatter for jsonnet
+- [JohnnyMorganz/StyLua]: an opinionated Lua code formatter
+- [Koihik/LuaFormatter]: a formatter for Lua code
+- [mrtazz/checkmake]: linter for Makefile syntax
+- [nbqa-dev/nbqa]: run common linters on Jupyter Notebooks
+
+[realm/SwiftLint]: https://github.com/realm/SwiftLint
+[nicklockwood/SwiftFormat]: https://github.com/nicklockwood/SwiftFormat
+[AleksaC/terraform-py]: https://github.com/AleksaC/terraform-py
+[rubocop/rubocop]: https://github.com/rubocop/rubocop
+[bufbuild/buf]: https://github.com/bufbuild/buf
+[sqlfluff/sqlfluff]: https://github.com/sqlfluff/sqlfluff
+[aws-cloudformation/cfn-lint]: https://github.com/aws-cloudformation/cfn-lint
+[google/go-jsonnet]: https://github.com/google/go-jsonnet
+[JohnnyMorganz/StyLua]: https://github.com/JohnnyMorganz/StyLua
+[Koihik/LuaFormatter]: https://github.com/Koihik/LuaFormatter
+[mrtazz/checkmake]: https://github.com/mrtazz/checkmake
+[nbqa-dev/nbqa]: https://github.com/nbQA-dev/nbQA
+
+## finding hooks
+
+it's recommended to use your favorite searching tool to find existing hooks to
+use in your project.
+
+for example, here's some searches you may find useful using [sourcegraph]:
+
+- hooks which run on python files: [`file:^\.pre-commit-hooks\.yaml$ "types: [python]"`](https://sourcegraph.com/search?q=context:global+file:^\.pre-commit-hooks\.yaml%24+%22types:+[python]%22)
+- hooks which run on shell files: [`file:^\.pre-commit-hooks\.yaml$ "types: [shell]"`](https://sourcegraph.com/search?q=context:global+file:^\.pre-commit-hooks\.yaml%24+"types:+[shell]")
+- pre-commit configurations in popular projects: [`file:^\.pre-commit-config\.yaml$`](https://sourcegraph.com/search?q=context:global+file:^\.pre-commit-hooks\.yaml)
+
+[sourcegraph]: https://sourcegraph.com/search
+
+you may also find [github's search] useful as well, though its querying and
+sorting capabilities are quite limited plus it requires a login:
+
+- repositories providing hooks: [`path:.pre-commit-hooks.yaml language:YAML`](https://github.com/search?q=path%3A.pre-commit-hooks.yaml+language%3AYAML&type=code&l=YAML)
+
+[github's search]: https://github.com/search
+
+
+## adding to this page
+
+the previous iteration of this page was a laundry list of hooks and maintaining
+quality of the listed tools was cumbersome.
+
+**this page is not intended to be exhaustive**
+
+you may send [a pull request] to expand this list however there are a few
+requirements you *must* follow or your PR will be closed without comment:
+
+- the tool must already be fairly popular (>500 stars)
+- the tool must use a managed language (no `unsupported` / `unsupported_script` / `docker` hooks)
+- the tool must operate on files
+
+[a pull request]: https://github.com/pre-commit/pre-commit.com/blob/main/sections/hooks.md
diff --git a/sections/install.md b/sections/install.md
new file mode 100644
index 00000000..3d6d4d85
--- /dev/null
+++ b/sections/install.md
@@ -0,0 +1,101 @@
+Before you can run hooks, you need to have the pre-commit package manager
+installed.
+
+Using pip:
+
+```bash
+pip install pre-commit
+```
+
+In a python project, add the following to your requirements.txt (or
+requirements-dev.txt):
+
+```
+pre-commit
+```
+
+As a 0-dependency [zipapp]:
+
+- locate and download the `.pyz` file from the [github releases]
+- run `python pre-commit-#.#.#.pyz ...` in place of `pre-commit ...`
+
+[zipapp]: https://docs.python.org/3/library/zipapp.html
+[github releases]: https://github.com/pre-commit/pre-commit/releases
+
+## Quick start
+
+### 1. Install pre-commit
+
+- follow the [install](#install) instructions above
+- `pre-commit --version` should show you what version you're using
+
+```cmd
+pre-commit --version
+```
+
+### 2. Add a pre-commit configuration
+
+- create a file named `.pre-commit-config.yaml`
+- you can generate a very basic configuration using
+  [`pre-commit sample-config`](#pre-commit-sample-config)
+- the full set of options for the configuration are listed [below](#plugins)
+- this example uses a formatter for python code, however `pre-commit` works for
+  any programming language
+- other [supported hooks](hooks.html) are available
+
+```yaml
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v2.3.0
+    hooks:
+    -   id: check-yaml
+    -   id: end-of-file-fixer
+    -   id: trailing-whitespace
+-   repo: https://github.com/psf/black
+    rev: 22.10.0
+    hooks:
+    -   id: black
+```
+
+### 3. Install the git hook scripts
+
+- run `pre-commit install` to set up the git hook scripts
+
+```console
+$ pre-commit install
+pre-commit installed at .git/hooks/pre-commit
+```
+
+- now `pre-commit` will run automatically on `git commit`!
+
+### 4. (optional) Run against all the files
+
+- it's usually a good idea to run the hooks against all of the files when adding
+  new hooks (usually `pre-commit` will only run on the changed files during
+  git hooks)
+
+```pre-commit
+$ pre-commit run --all-files
+[INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks.
+[INFO] Initializing environment for https://github.com/psf/black.
+[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
+[INFO] Once installed this environment will be reused.
+[INFO] This may take a few minutes...
+[INFO] Installing environment for https://github.com/psf/black.
+[INFO] Once installed this environment will be reused.
+[INFO] This may take a few minutes...
+Check Yaml...............................................................Passed
+Fix End of Files.........................................................Passed
+Trim Trailing Whitespace.................................................Failed
+- hook id: trailing-whitespace
+- exit code: 1
+
+Files were modified by this hook. Additional output:
+
+Fixing sample.py
+
+black....................................................................Passed
+```
+
+- oops! looks like I had some trailing whitespace
+- consider running that in [CI](#usage-in-continuous-integration) too
diff --git a/sections/intro.md b/sections/intro.md
new file mode 100644
index 00000000..cd0d1173
--- /dev/null
+++ b/sections/intro.md
@@ -0,0 +1,26 @@
+Git hook scripts are useful for identifying simple issues before submission to
+code review.  We run our hooks on every commit to automatically point out
+issues in code such as missing semicolons, trailing whitespace, and debug
+statements.  By pointing these issues out before code review, this allows a
+code reviewer to focus on the architecture of a change while not wasting time
+with trivial style nitpicks.
+
+As we created more libraries and projects we recognized that sharing our
+pre-commit hooks across projects is painful. We copied and pasted unwieldy
+bash scripts from project to project and had to manually change the hooks to
+work for different project structures.
+
+We believe that you should always use the best industry standard linters.
+Some of the best linters are written in languages that you do not use in your
+project or have installed on your machine. For example scss-lint is a linter
+for SCSS written in Ruby. If you’re writing a project in node you should be
+able to use scss-lint as a pre-commit hook without adding a Gemfile to your
+project or understanding how to get scss-lint installed.
+
+We built pre-commit to solve our hook issues. It is a multi-language package
+manager for pre-commit hooks. You specify a list of hooks you want and
+pre-commit manages the installation and execution of any hook written in any
+language before every commit. pre-commit is specifically designed to not
+require root access. If one of your developers doesn’t have node installed
+but modifies a JavaScript file, pre-commit automatically handles downloading
+and building node to run eslint without root.
diff --git a/sections/new-hooks.md b/sections/new-hooks.md
new file mode 100644
index 00000000..6154b821
--- /dev/null
+++ b/sections/new-hooks.md
@@ -0,0 +1,518 @@
+pre-commit currently supports hooks written in
+[many languages](#supported-languages). As long as your git repo is an
+installable package (gem, npm, pypi, etc.) or exposes an executable, it can be
+used with pre-commit. Each git repo can support as many languages/hooks as you
+want.
+
+The hook must exit nonzero on failure or modify files.
+
+A git repo containing pre-commit plugins must contain a `.pre-commit-hooks.yaml`
+file that tells pre-commit:
+
+```table
+=r=
+    =c= [`id`](_#hooks-id)
+    =c= the id of the hook - used in pre-commit-config.yaml.
+=r=
+    =c= [`name`](_#hooks-name)
+    =c= the name of the hook - shown during hook execution.
+=r=
+    =c= [`entry`](_#hooks-entry)
+    =c= the entry point - the executable to run.  `entry` can also contain
+        arguments that will not be overridden such as `entry: autopep8 -i`.
+=r=
+    =c= [`language`](_#hooks-language)
+    =c= the language of the hook - tells pre-commit how to install the hook.
+=r=
+    =c= [`files`](_#hooks-files)
+    =c= (optional: default `''`) the pattern of files to run on.
+=r=
+    =c= [`exclude`](_#hooks-exclude)
+    =c= (optional: default `^$`)  exclude files that were matched by [`files`](#hooks-files).
+=r=
+    =c= [`types`](_#hooks-types)
+    =c= (optional: default `[file]`)  list of file types to run on (AND).  See
+        [Filtering files with types](#filtering-files-with-types).
+=r=
+    =c= [`types_or`](_#hooks-types_or)
+    =c= (optional: default `[]`)  list of file types to run on (OR).  See
+        [Filtering files with types](#filtering-files-with-types).
+=r=
+    =c= [`exclude_types`](_#hooks-exclude_types)
+    =c= (optional: default `[]`)  the pattern of files to exclude.
+=r=
+    =c= [`always_run`](_#hooks-always_run)
+    =c= (optional: default `false`) if `true` this hook will run even if there
+        are no matching files.
+=r=
+    =c= [`fail_fast`](_#hooks-fail_fast)
+    =c= (optional: default `false`) if `true` pre-commit will stop running
+        hooks if this hook fails.
+=r=
+    =c= [`verbose`](_#hooks-verbose)
+    =c= (optional: default `false`) if `true`, forces the output of the hook to be printed even when
+        the hook passes.
+=r=
+    =c= [`pass_filenames`](_#hooks-pass_filenames)
+    =c= (optional: default `true`) if `false` no filenames will be passed to
+        the hook.
+=r=
+    =c= [`require_serial`](_#hooks-require_serial)
+    =c= (optional: default `false`) if `true` this hook will execute using a
+        single process instead of in parallel.
+=r=
+    =c= [`description`](_#hooks-description)
+    =c= (optional: default `''`) description of the hook.  used for metadata
+        purposes only.
+=r=
+    =c= [`language_version`](_#hooks-language_version)
+    =c= (optional: default `default`) see
+        [Overriding language version](#overriding-language-version).
+=r=
+    =c= [`minimum_pre_commit_version`](_#hooks-minimum_pre_commit_version)
+    =c= (optional: default `'0'`) allows one to indicate a minimum
+        compatible pre-commit version.
+=r=
+    =c= [`args`](_#hooks-args)
+    =c= (optional: default `[]`) list of additional parameters to pass to the hook.
+=r=
+    =c= [`stages`](_#hooks-stages)
+    =c= (optional: default (all stages)) selects which git hook(s) to run for.
+        See [Confining hooks to run at certain stages](#confining-hooks-to-run-at-certain-stages).
+
+```
+
+For example:
+
+```yaml
+-   id: trailing-whitespace
+    name: Trim Trailing Whitespace
+    description: This hook trims trailing whitespace.
+    entry: trailing-whitespace-fixer
+    language: python
+    types: [text]
+```
+
+## Developing hooks interactively
+
+Since the [`repo`](#repos-repo) property of `.pre-commit-config.yaml` can refer to anything
+that `git clone ...` understands, it's often useful to point it at a local
+directory while developing hooks.
+
+[`pre-commit try-repo`](#pre-commit-try-repo) streamlines this process by
+enabling a quick way to try out a repository.  Here's how one might work
+interactively:
+
+_note_: you may need to provide `--commit-msg-filename` when using this
+command with hook types `prepare-commit-msg` and `commit-msg`.
+
+a commit is not necessary to `try-repo` on a local
+directory. `pre-commit` will clone any tracked uncommitted changes.
+
+```pre-commit
+~/work/hook-repo $ git checkout origin/main -b feature
+
+# ... make some changes
+
+# In another terminal or tab
+
+~/work/other-repo $ pre-commit try-repo ../hook-repo foo --verbose --all-files
+===============================================================================
+Using config:
+===============================================================================
+repos:
+-   repo: ../hook-repo
+    rev: 84f01ac09fcd8610824f9626a590b83cfae9bcbd
+    hooks:
+    -   id: foo
+===============================================================================
+[INFO] Initializing environment for ../hook-repo.
+Foo......................................................................Passed
+- hook id: foo
+- duration: 0.02s
+
+Hello from foo hook!
+
+```
+
+## Supported languages
+
+- [conda](#conda)
+- [coursier](#coursier)
+- [dart](#dart)
+- [docker](#docker)
+- [docker_image](#docker_image)
+- [dotnet](#dotnet)
+- [fail](#fail)
+- [golang](#golang)
+- [haskell](#haskell)
+- [lua](#lua)
+- [node](#node)
+- [perl](#perl)
+- [python](#python)
+- [r](#r)
+- [ruby](#ruby)
+- [rust](#rust)
+- [swift](#swift)
+- [pygrep](#pygrep)
+- [unsupported](#unsupported)
+- [unsupported_script](#unsupported_script)
+
+### conda
+
+The hook repository must contain an `environment.yml` file which will be used
+via `conda env create --file environment.yml ...` to create the environment.
+
+The `conda` language also supports [`additional_dependencies`](#config-additional_dependencies)
+and will pass any of the values directly into `conda install`.  This language can therefore be
+used with [local](#repository-local-hooks) hooks.
+
+`mamba` or `micromamba` can be used to install instead via the
+`PRE_COMMIT_USE_MAMBA=1` or `PRE_COMMIT_USE_MICROMAMBA=1` environment
+variables.
+
+__Support:__ `conda` hooks work as long as there is a system-installed `conda`
+binary (such as [`miniconda`](https://docs.conda.io/en/latest/miniconda.html)).
+It has been tested on linux, macOS, and windows.
+
+### coursier
+
+The hook repository must have a `.pre-commit-channel` folder and that folder
+must contain the coursier
+[application descriptors](https://get-coursier.io/docs/2.0.0-RC6-10/cli-install.html#application-descriptor-reference)
+for the hook to install. For configuring coursier hooks, your
+[`entry`](#hooks-entry) should correspond to an executable installed from the
+repository's `.pre-commit-channel` folder.
+
+__Support:__ `coursier` hooks are known to work on any system which has the
+`cs` or `coursier` package manager installed. The specific coursier
+applications you install may depend on various versions of the JVM, consult
+the hooks' documentation for clarification.  It has been tested on linux.
+
+pre-commit also supports the `coursier` naming of the package manager
+executable.
+
+_new in 3.0.0_: `language: coursier` hooks now support `repo: local` and
+`additional_dependencies`.
+
+### dart
+
+The hook repository must have a `pubspec.yaml` -- this must contain an
+`executables` section which will list the binaries that will be available
+after installation.  Match the [`entry`](#hooks-entry) to an executable.
+
+`pre-commit` will build each executable using `dart compile exe bin/{executable}.dart`.
+
+`language: dart` also supports [`additional_dependencies`](#config-additional_dependencies).
+to specify a version for a dependency, separate the package name by a `:`:
+
+```yaml
+        additional_dependencies: ['hello_world_dart:1.0.0']
+```
+
+__Support:__ `dart` hooks are known to work on any system which has the `dart`
+sdk installed.  It has been tested on linux, macOS, and windows.
+
+### docker
+
+The hook repository must have a `Dockerfile`.  It will be installed via
+`docker build .`.
+
+Running Docker hooks requires a running Docker engine on your host.  For
+configuring Docker hooks, your [`entry`](#hooks-entry) should correspond to an executable
+inside the Docker container, and will be used to override the default container
+entrypoint. Your Docker `CMD` will not run when pre-commit passes a file list
+as arguments to the run container command. Docker allows you to use any
+language that's not supported by pre-commit as a builtin.
+
+pre-commit will automatically mount the repository source as a volume using
+`-v $PWD:/src:rw,Z` and set the working directory using `--workdir /src`.
+
+__Support:__ docker hooks are known to work on any system which has a working
+`docker` executable.  It has been tested on linux and macOS.  Hooks that are
+run via `boot2docker` are known to be unable to make modifications to files.
+
+See [this repository](https://github.com/pre-commit/pre-commit-docker-flake8)
+for an example Docker-based hook.
+
+### docker_image
+
+A more lightweight approach to `docker` hooks.  The `docker_image`
+"language" uses existing docker images to provide hook executables.
+
+`docker_image` hooks can be conveniently configured as [local](#repository-local-hooks)
+hooks.
+
+The [`entry`](#hooks-entry) specifies the docker tag to use.  If an image has an
+`ENTRYPOINT` defined, nothing special is needed to hook up the executable.
+If the container does not specify an `ENTRYPOINT` or you want to change the
+entrypoint you can specify it as well in your [`entry`](#hooks-entry).
+
+For example:
+
+```yaml
+-   id: dockerfile-provides-entrypoint
+    name: ...
+    language: docker_image
+    entry: my.registry.example.com/docker-image-1:latest
+-   id: dockerfile-no-entrypoint-1
+    name: ...
+    language: docker_image
+    entry: --entrypoint my-exe my.registry.example.com/docker-image-2:latest
+# Alternative equivalent solution
+-   id: dockerfile-no-entrypoint-2
+    name: ...
+    language: docker_image
+    entry: my.registry.example.com/docker-image-3:latest my-exe
+```
+
+### dotnet
+
+dotnet hooks are installed using the system installation of the dotnet CLI.
+
+Hook repositories must contain a dotnet CLI tool which can be `pack`ed and
+`install`ed as per [this](https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools-how-to-create)
+example. The `entry` should match an executable created by building the
+repository. Additional dependencies are not currently supported.
+
+__Support:__ dotnet hooks are known to work on any system which has the dotnet
+CLI installed.  It has been tested on linux and windows.
+
+### fail
+
+A lightweight [`language`](#hooks-language) to forbid files by filename.  The `fail` language is
+especially useful for [local](#repository-local-hooks) hooks.
+
+The [`entry`](#hooks-entry) will be printed when the hook fails.  It is suggested to provide
+a brief description for [`name`](#hooks-name) and more verbose fix instructions in [`entry`](#hooks-entry).
+
+Here's an example which prevents any file except those ending with `.rst` from
+being added to the `changelog` directory:
+
+```yaml
+-   repo: local
+    hooks:
+    -   id: changelogs-rst
+        name: changelogs must be rst
+        entry: changelog filenames must end in .rst
+        language: fail
+        files: 'changelog/.*(?<!\.rst)$'
+```
+
+### golang
+
+The hook repository must contain go source code.  It will be installed via
+`go install ./...`.  pre-commit will create an isolated `GOPATH` for each hook
+and the [`entry`](#hooks-entry) should match an executable which will get installed into the
+`GOPATH`'s `bin` directory.
+
+This language supports `additional_dependencies` and will pass any of the values directly to `go
+install`. It can be used as a `repo: local` hook.
+
+_changed in 2.17.0_: previously `go get ./...` was used
+
+_new in 3.0.0_: pre-commit will bootstrap `go` if it is not present. `language: golang`
+also now supports `language_version`
+
+__Support:__ golang hooks are known to work on any system which has go
+installed.  It has been tested on linux, macOS, and windows.
+
+### haskell
+
+_new in 3.4.0_
+
+The hook repository must have one or more `*.cabal` files.  Once installed
+the `executable`s from these packages will be available to use with `entry`.
+
+This language supports `additional_dependencies` so it can be used as a
+`repo: local` hook.
+
+__Support:__ haskell hooks are known to work on any system which has `cabal`
+installed.  It has been tested on linux, macOS, and windows.
+
+### julia
+
+_new in 4.1.0_
+
+For configuring julia hooks, your [`entry`](#hooks-entry) should be a path to a julia source
+file relative to the hook repository (optionally with arguments).
+
+Hooks run in an isolated package environment defined by a `Project.toml` file (optionally
+with a `Manifest.toml` file) in the hook repository. If no `Project.toml` file is found the
+hook is run in an empty environment.
+
+Julia hooks support [`additional_dependencies`](#config-additional_dependencies) which can
+be used to augment, or override, the existing environment in the hooks repository. This also
+means that julia can be used as a `repo: local` hook. `additional_dependencies` are passed
+to `pkg> add` and should be specified using
+[Pkg REPL mode syntax](https://pkgdocs.julialang.org/v1/repl/#repl-add).
+
+Examples:
+
+```yaml
+- id: foo-without-args
+  name: ...
+  language: julia
+  entry: bin/foo.jl
+- id: bar-with-args
+  name: ...
+  language: julia
+  entry: bin/bar.jl --arg1 --arg2
+- id: baz-with-extra-deps
+  name: ...
+  language: julia
+  entry: bin/baz.jl
+  additional_dependencies:
+   - 'ExtraDepA@1'
+   - 'ExtraDepB@2.4'
+```
+
+__Support:__ julia hooks are known to work on any system which has `julia` installed.
+
+### lua
+
+Lua hooks are installed with the version of Lua that is used by Luarocks.
+
+__Support:__ Lua hooks are known to work on any system which has Luarocks
+installed.  It has been tested on linux and macOS and _may_ work on windows.
+
+### node
+
+The hook repository must have a `package.json`.  It will be installed via
+`npm install .`.  The installed package will provide an executable that will
+match the [`entry`](#hooks-entry) – usually through `bin` in package.json.
+
+__Support:__ node hooks work without any system-level dependencies.  It has
+been tested on linux, windows, and macOS and _may_ work under cygwin.
+
+### perl
+
+Perl hooks are installed using the system installation of
+[cpan](https://perldoc.perl.org/cpan), the CPAN package installer
+that comes with Perl.
+
+Hook repositories must have something that `cpan` supports, typically
+`Makefile.PL` or `Build.PL`, which it uses to install an executable to
+use in the [`entry`](#hooks-entry) definition for your hook. The repository will be installed
+via `cpan -T .` (with the installed files stored in your pre-commit cache,
+not polluting other Perl installations).
+
+When specifying [`additional_dependencies`](#config-additional_dependencies) for Perl, you can use any of the
+[install argument formats understood by `cpan`](https://perldoc.perl.org/CPAN#get%2c-make%2c-test%2c-install%2c-clean-modules-or-distributions).
+
+__Support:__ Perl hooks currently require a pre-existing Perl installation,
+including the `cpan` tool in `PATH`.  It has been tested on linux, macOS, and
+Windows.
+
+### python
+
+The hook repository must be installable via `pip install .` (usually by either
+`setup.py` or `pyproject.toml`).  The installed package will provide an
+executable that will match the [`entry`](#hooks-entry) – usually through `console_scripts` or
+`scripts` in setup.py.
+
+This language also supports `additional_dependencies`
+so it can be used with [local](#repository-local-hooks) hooks.
+The specified dependencies will be appended to the `pip install` command.
+
+__Support:__ python hooks work without any system-level dependencies.  It
+has been tested on linux, macOS, windows, and cygwin.
+
+### r
+
+This hook repository must have a `renv.lock` file that will be restored with
+[`renv::restore()`](https://rstudio.github.io/renv/reference/restore.html) on
+hook installation. If the repository is an R package (i.e. has `Type: Package`
+in `DESCRIPTION`), it is installed. The supported syntax in [`entry`](#hooks-entry) is
+`Rscript -e {expression}` or `Rscript path/relative/to/hook/root`. The
+R Startup process is skipped (emulating `--vanilla`), as all configuration
+should be exposed via [`args`](#hooks-args) for maximal transparency and portability.
+
+When specifying [`additional_dependencies`](#config-additional_dependencies)
+for R, you can use any of the install argument formats understood by
+[`renv::install()`](https://rstudio.github.io/renv/reference/install.html#examples).
+
+__Support:__ `r` hooks work as long as [`R`](https://www.r-project.org) is
+installed and on `PATH`. It has been tested on linux, macOS, and windows.
+
+
+### ruby
+
+The hook repository must have a `*.gemspec`.  It will be installed via
+`gem build *.gemspec && gem install *.gem`.  The installed package will
+produce an executable that will match the [`entry`](#hooks-entry) – usually through
+`executables` in your gemspec.
+
+__Support:__ ruby hooks work without any system-level dependencies.  It has
+been tested on linux and macOS and _may_ work under cygwin.
+
+### rust
+
+Rust hooks are installed using [Cargo](https://github.com/rust-lang/cargo),
+Rust's official package manager.
+
+Hook repositories must have a `Cargo.toml` file which produces at least one
+binary ([example](https://github.com/chriskuehl/example-rust-pre-commit-hook)),
+whose name should match the [`entry`](#hooks-entry) definition for your hook. The repo will be
+installed via `cargo install --bins` (with the binaries stored in your
+pre-commit cache, not polluting your user-level Cargo installations).
+
+When specifying [`additional_dependencies`](#config-additional_dependencies) for Rust, you can use the syntax
+`{package_name}:{package_version}` to specify a new library dependency (used to
+build _your_ hook repo), or the special syntax
+`cli:{package_name}:{package_version}` for a CLI dependency (built separately,
+with binaries made available for use by hooks).
+
+pre-commit will bootstrap `rust` if it is not present.
+`language: rust` also supports `language_version`
+
+__Support:__ It has been tested on linux, Windows, and macOS.
+
+### swift
+
+The hook repository must have a `Package.swift`.  It will be installed via
+`swift build -c release`.  The [`entry`](#hooks-entry) should match an executable created by
+building the repository.
+
+__Support:__ swift hooks are known to work on any system which has swift
+installed.  It has been tested on linux and macOS.
+
+### pygrep
+
+A cross-platform python implementation of `grep` – pygrep hooks are a quick
+way to write a simple hook which prevents commits by file matching.  Specify
+the regex as the [`entry`](#hooks-entry).  The [`entry`](#hooks-entry) may be any python
+[regular expression](#regular-expressions).  For case insensitive regexes you
+can apply the `(?i)` flag as the start of your entry, or use `args: [-i]`.
+
+For multiline matches, use `args: [--multiline]`.
+
+To require all files to match, use `args: [--negate]`.
+
+__Support:__ pygrep hooks are supported on all platforms which pre-commit runs
+on.
+
+### unsupported
+
+[anchor](__#system)
+_new in 4.4.0_: previously `language: system`.  the alias will be removed in a
+future version
+
+System hooks provide a way to write hooks for system-level executables which
+don't have a supported language above (or have special environment
+requirements that don't allow them to run in isolation such as pylint).
+
+This hook type will not be given a virtual environment to work with – if it
+needs additional dependencies the consumer must install them manually.
+
+### unsupported_script
+
+[anchor](__#script)
+_new in 4.4.0_: previously `language: script`.  the alias will be removed in a
+future version
+
+Script hooks provide a way to write simple scripts which validate files. The
+[`entry`](#hooks-entry) should be a path relative to the root of the hook repository.
+
+This hook type will not be given a virtual environment to work with – if it
+needs additional dependencies the consumer must install them manually.
diff --git a/sections/plugins.md b/sections/plugins.md
new file mode 100644
index 00000000..96cb213c
--- /dev/null
+++ b/sections/plugins.md
@@ -0,0 +1,176 @@
+Once you have pre-commit installed, adding pre-commit plugins to your project
+is done with the `.pre-commit-config.yaml` configuration file.
+
+Add a file called `.pre-commit-config.yaml` to the root of your project. The
+pre-commit config file describes what repositories and hooks are installed.
+
+## .pre-commit-config.yaml - top level
+
+```table
+=r=
+    =c= [`repos`](_#top_level-repos)
+    =c= A list of [repository mappings](#pre-commit-configyaml---repos).
+=r=
+    =c= [`default_install_hook_types`](_#top_level-default_install_hook_types)
+    =c= (optional: default `[pre-commit]`) a list of `--hook-type`s which will
+        be used by default when running
+        [`pre-commit install`](#pre-commit-install).
+=r=
+    =c= [`default_language_version`](_#top_level-default_language_version)
+    =c= (optional: default `{}`) a mapping from language to the default
+        [`language_version`](#config-language_version) that should be used for that language.  This will
+        only override individual hooks that do not set [`language_version`](#config-language_version).
+
+        For example to use `python3.7` for `language: python` hooks:
+
+        ```yaml
+        default_language_version:
+            python: python3.7
+        ```
+=r=
+    =c= [`default_stages`](_#top_level-default_stages)
+    =c= (optional: default (all stages)) a configuration-wide default for
+        the [`stages`](#config-stages) property of hooks.  This will only override individual
+        hooks that do not set [`stages`](#config-stages).
+
+        For example:
+
+        ```yaml
+        default_stages: [pre-commit, pre-push]
+        ```
+=r=
+    =c= [`files`](_#top_level-files)
+    =c= (optional: default `''`) global file include pattern.
+=r=
+    =c= [`exclude`](_#top_level-exclude)
+    =c= (optional: default `^$`) global file exclude pattern.
+=r=
+    =c= [`fail_fast`](_#top_level-fail_fast)
+    =c= (optional: default `false`) set to `true` to have pre-commit stop
+        running hooks after the first failure.
+=r=
+    =c= [`minimum_pre_commit_version`](_#top_level-minimum_pre_commit_version)
+    =c= (optional: default `'0'`) require a minimum version of pre-commit.
+```
+
+A sample top-level:
+
+```yaml
+exclude: '^$'
+fail_fast: false
+repos:
+-   ...
+```
+
+## .pre-commit-config.yaml - repos
+
+The repository mapping tells pre-commit where to get the code for the hook
+from.
+
+```table
+=r=
+    =c= [`repo`](_#repos-repo)
+    =c= the repository url to `git clone` from
+        or one of the special sentinel values:
+        [`local`](#repository-local-hooks),
+        [`meta`](#meta-hooks).
+=r=
+    =c= [`rev`](_#repos-rev)
+    =c= the revision or tag to clone at.
+=r=
+    =c= [`hooks`](_#repos-hooks)
+    =c= A list of [hook mappings](#pre-commit-configyaml---hooks).
+```
+
+A sample repository:
+
+```yaml
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v1.2.3
+    hooks:
+    -   ...
+```
+
+## .pre-commit-config.yaml - hooks
+
+The hook mapping configures which hook from the repository is used and allows
+for customization.  All optional keys will receive their default from the
+repository's configuration.
+
+```table
+=r=
+    =c= [`id`](_#config-id)
+    =c= which hook from the repository to use.
+=r=
+    =c= [`alias`](_#config-alias)
+    =c= (optional) allows the hook to be referenced using an additional id when
+        using `pre-commit run <hookid>`.
+=r=
+    =c= [`name`](_#config-name)
+    =c= (optional) override the name of the hook - shown during hook execution.
+=r=
+    =c= [`language_version`](_#config-language_version)
+    =c= (optional) override the language version for the
+        hook.  See [Overriding Language Version](#overriding-language-version).
+=r=
+    =c= [`files`](_#config-files)
+    =c= (optional) override the default pattern for files to run on.
+=r=
+    =c= [`exclude`](_#config-exclude)
+    =c= (optional) file exclude pattern.
+=r=
+    =c= [`types`](_#config-types)
+    =c= (optional) override the default file types to run on (AND).  See
+        [Filtering files with types](#filtering-files-with-types).
+=r=
+    =c= [`types_or`](_#config-types_or)
+    =c= (optional) override the default file types to run on (OR).  See
+        [Filtering files with types](#filtering-files-with-types).
+=r=
+    =c= [`exclude_types`](_#config-exclude_types)
+    =c= (optional) file types to exclude.
+=r=
+    =c= [`args`](_#config-args)
+    =c= (optional) list of additional parameters to pass to the hook.
+=r=
+    =c= [`stages`](_#config-stages)
+    =c= (optional) selects which git hook(s) to run for.
+        See [Confining hooks to run at certain stages](#confining-hooks-to-run-at-certain-stages).
+=r=
+    =c= [`additional_dependencies`](_#config-additional_dependencies)
+    =c= (optional) a list of dependencies that will be installed in the
+        environment where this hook gets run.  One useful application is to
+        install plugins for hooks such as `eslint`.
+=r=
+    =c= [`always_run`](_#config-always_run)
+    =c= (optional) if `true`, this hook will run even if there are no matching
+        files.
+=r=
+    =c= [`verbose`](_#config-verbose)
+    =c= (optional) if `true`, forces the output of the hook to be printed even when
+        the hook passes.
+=r=
+    =c= [`log_file`](_#config-log_file)
+    =c= (optional) if present, the hook output will additionally be written to
+        a file when the hook fails or [verbose](#config-verbose) is `true`.
+```
+
+One example of a complete configuration:
+
+```yaml
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v1.2.3
+    hooks:
+    -   id: trailing-whitespace
+```
+
+This configuration says to download the pre-commit-hooks project and run its
+trailing-whitespace hook.
+
+## Updating hooks automatically
+
+You can update your hooks to the latest version automatically by running
+[`pre-commit autoupdate`](#pre-commit-autoupdate).  By default, this will
+bring the hooks to the latest tag on the default branch.
diff --git a/sections/usage.md b/sections/usage.md
new file mode 100644
index 00000000..94addae8
--- /dev/null
+++ b/sections/usage.md
@@ -0,0 +1,32 @@
+Run `pre-commit install` to install pre-commit into your git hooks. pre-commit
+will now run on every commit. Every time you clone a project using pre-commit
+running `pre-commit install` should always be the first thing you do.
+
+If you want to manually run all pre-commit hooks on a repository, run
+`pre-commit run --all-files`. To run individual hooks use
+`pre-commit run <hook_id>`.
+
+The first time pre-commit runs on a file it will automatically download,
+install, and run the hook. Note that running a hook for the first time may be
+slow. For example: If the machine does not have node installed, pre-commit
+will download and build a copy of node.
+
+```pre-commit
+$ pre-commit install
+pre-commit installed at /home/asottile/workspace/pytest/.git/hooks/pre-commit
+$ git commit -m "Add super awesome feature"
+black....................................................................Passed
+blacken-docs.........................................(no files to check)Skipped
+Trim Trailing Whitespace.................................................Passed
+Fix End of Files.........................................................Passed
+Check Yaml...........................................(no files to check)Skipped
+Debug Statements (Python)................................................Passed
+Flake8...................................................................Passed
+Reorder python imports...................................................Passed
+pyupgrade................................................................Passed
+rst ``code`` is two backticks........................(no files to check)Skipped
+rst..................................................(no files to check)Skipped
+changelog filenames..................................(no files to check)Skipped
+[main 146c6c2c] Add super awesome feature
+ 1 file changed, 1 insertion(+)
+```
diff --git a/template_lib.py b/template_lib.py
index 5466484b..05a26c61 100644
--- a/template_lib.py
+++ b/template_lib.py
@@ -1,15 +1,17 @@
+from __future__ import annotations
+
+import html
 import os
 import re
 import shlex
 import subprocess
 import sys
-from typing import Optional
 
 import markdown_code_blocks
 import markupsafe
 
 
-ID_RE = re.compile(r'\[\]\(#([a-z0-9-]+)\)')
+ID_RE = re.compile(r' #([a-z0-9-]+)$')
 SPECIAL_CHARS_RE = re.compile('[^a-z0-9 _-]')
 
 
@@ -63,13 +65,13 @@ def _maybe_end_row() -> None:
             output.append('<tr>')
         elif line.startswith(COL):
             _maybe_end_col()
-            col_buffer = line[len(COL):]
+            col_buffer = line.removeprefix(COL)
         elif col_buffer is not None:
             if line == '\n':
                 col_buffer += line
             else:
                 assert line.startswith(INDENT), line
-                col_buffer += line[len(INDENT):]
+                col_buffer += line.removeprefix(INDENT)
         else:
             raise AssertionError(line)
 
@@ -88,37 +90,70 @@ def _render_cmd(code: str) -> str:
 
 
 class Renderer(markdown_code_blocks.CodeRenderer):
-    def header(self, text: str, level: int, raw: str) -> str:
-        match = ID_RE.search(raw)
+    def link(
+        self, link: str, text: str | None, title: str | None,
+    ) -> str:
+        if link.startswith('_#'):
+            a_id = link.removeprefix('_#')
+            return f'<a id="{a_id}" href="#{a_id}">{text}</a>'
+        elif link.startswith('__#'):
+            return f'<a name="{link.removeprefix("__#")}"></a>'
+        else:
+            return super().link(link, text, title)
+
+    def heading(self, text: str, level: int) -> str:
+        match = ID_RE.search(text)
+        text = ID_RE.sub('', text)
         if match:
-            h_id = match.group(1)
+            h_id = match[1]
         else:
-            h_id = SPECIAL_CHARS_RE.sub('', raw.lower()).replace(' ', '-')
+            h_id = SPECIAL_CHARS_RE.sub('', text.lower()).replace(' ', '-')
         return (
             f'<h{level} id="{h_id}">'
-            f'    {text} <small><a href="#{h_id}">¶</a></small>'
+            f'    {text} <small><a href="#{h_id}" class="text-decoration-none">¶</a></small>'  # noqa: E501
             f'</h{level}> '
         )
 
-    def block_code(self, code: str, lang: Optional[str]) -> str:
+    def codespan(self, text: str) -> str:
+        if text.startswith('<kbd>'):
+            # we trust this content
+            return text
+        else:
+            return super().codespan(text)
+
+    def image(
+            self,
+            src: str,
+            alt: str = '',
+            title: str | None = None,
+    ) -> str:
+        return (
+            f'<img '
+            f'    src="{html.escape(src)}"'
+            f'    alt="{html.escape(alt)}"'
+            f'    class="img-fluid img-thumbnail"'
+            f'>'
+        )
+
+    def block_code(self, code: str, info: str | None = None) -> str:
         copyable = False
-        if lang is not None:
+        if info is not None:
             copyable_s = '#copyable'
-            copyable = lang.endswith(copyable_s)
-            lang, _, _ = lang.partition(copyable_s)
-        if lang == 'table':
+            copyable = info.endswith(copyable_s)
+            info, _, _ = info.partition(copyable_s)
+        if info == 'table':
             ret = _render_table(code)
-        elif lang == 'cmd':
+        elif info == 'cmd':
             ret = _render_cmd(code)
         else:
-            ret = super().block_code(code, lang)
+            ret = super().block_code(code, info)
         if copyable:
             return f'<div class="copyable">{ret}</div>'
         else:
             return ret
 
 
-def md(s: str) -> str:
+def md(s: str) -> markupsafe.Markup:
     html = markdown_code_blocks.highlight(s, Renderer=Renderer)
     # manually bless the highlighted output.
     return markupsafe.Markup(html)