diff --git a/docs/database/ftl.md b/docs/database/ftl.md index 7787bc4..db4d2f7 100644 --- a/docs/database/ftl.md +++ b/docs/database/ftl.md @@ -215,5 +215,3 @@ posteo.de|130243 ``` showing the domain and the number of times it was found in the long-term database. Note that such a request might take a very long time for computation as the entire history of queries has to be processed for this. - -{!abbreviations.md!} diff --git a/docs/database/gravity/index.md b/docs/database/gravity/index.md index 081b8cf..4f78291 100644 --- a/docs/database/gravity/index.md +++ b/docs/database/gravity/index.md @@ -80,5 +80,3 @@ Label | Type | Uniqueness enforced | Content `id` | integer | Yes | Unique ID for database operations `domain` | text | Yes | Domain `date_added` | integer | No | Unix timestamp when domain was added - -{!abbreviations.md!} diff --git a/docs/database/gravity/recovery.md b/docs/database/gravity/recovery.md index 678bab3..29e3f52 100644 --- a/docs/database/gravity/recovery.md +++ b/docs/database/gravity/recovery.md @@ -32,5 +32,3 @@ Run: ```bash pihole -g -r recover force ``` - - {!abbreviations.md!} diff --git a/docs/database/index.md b/docs/database/index.md index 4015ddf..dea18ea 100644 --- a/docs/database/index.md +++ b/docs/database/index.md @@ -4,5 +4,3 @@ Details concerning the databases, their contained tables and exemplary SQL comma - [Query database `/etc/pihole/pihole-FTL.db`](ftl.md) - [Domain database `/etc/pihole/gravity.db`](gravity/index.md) - -{!abbreviations.md!} diff --git a/docs/ftldns/blockingmode.md b/docs/ftldns/blockingmode.md index f3883ad..a643b17 100644 --- a/docs/ftldns/blockingmode.md +++ b/docs/ftldns/blockingmode.md @@ -108,4 +108,3 @@ A blocked query would look like the following: **Advantages & Disadvantages:** This mode is similar to `NXDOMAIN` blocking mode. Clients might have a better acceptance of `NODATA` replies compared to `NXDOMAIN` replies. -{!abbreviations.md!} diff --git a/docs/ftldns/cache_dump.md b/docs/ftldns/cache_dump.md index eb8f1f3..b79d264 100644 --- a/docs/ftldns/cache_dump.md +++ b/docs/ftldns/cache_dump.md @@ -194,5 +194,3 @@ _sip._tcp.pcscf2.ims.telekom.d 100 10 5062 pspcscfhost2.ims.telekom.de VF ``` The `address` field lists the priority (`100` in the example), the weight (`10`), and the SRV port (`5062`), followed by the target (`pspcscfhost2.ims.telekom.de`). - -{!abbreviations.md!} diff --git a/docs/ftldns/compatibility.md b/docs/ftldns/compatibility.md index 8625833..84a3f8d 100644 --- a/docs/ftldns/compatibility.md +++ b/docs/ftldns/compatibility.md @@ -20,5 +20,3 @@ We tested *FTL*DNS on the following devices: Devices we do not officially support include MIPS and `armv5` (or lower) devices. You may, however, be successful with building binaries yourself from the source code, but we do not provide pre-built binaries for these targets. - -{!abbreviations.md!} diff --git a/docs/ftldns/compile.md b/docs/ftldns/compile.md index e8e3bcf..317bdaa 100644 --- a/docs/ftldns/compile.md +++ b/docs/ftldns/compile.md @@ -94,5 +94,3 @@ sudo service pihole-FTL restart While most people think of [Docker](https://www.docker.com/) as a deployment environment, it's also a wonderful tool to create and maintain build environments. Pi-hole provides `ftl-build` containers composed of everything needed to build FTL for various architectures on your `x86_64` hosts. Check out [Docker Hub `pi-hole/ftl-build`](https://hub.docker.com/r/pihole/ftl-build/tags) for the available build containers as well as the [Releases overview](https://github.com/pi-hole/docker-base-images/releases/) for a detailed changelog. The `ftl-build` containers can, for instance, easily be used as [`devcontainers`](https://code.visualstudio.com/docs/devcontainers/containers) with Visual Studio Code's [`remote-containers`](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension. The necessary `devcontainer.json` is provided in the FTL repository. See the description of the extension for further details. Note that `./build.sh install` would only install FTL in the container in this case. Instead, you have to copy the FTL binary generated inside the container yourself to the final destination on your installation target. - -{!abbreviations.md!} diff --git a/docs/ftldns/configfile.md b/docs/ftldns/configfile.md index af7f231..dc4afd9 100644 --- a/docs/ftldns/configfile.md +++ b/docs/ftldns/configfile.md @@ -399,6 +399,3 @@ If neither `BLOCK_IPV6` nor `LOCAL_IPV6` are set, this setting is used to set bo *This option is deprecated as FTL does not write any port file anymore. Please parse `pihole-FTL.conf` if you need to check if a custom API port is set.* The file containing the port FTL's API is listening on. - - -{!abbreviations.md!} diff --git a/docs/ftldns/debugging.md b/docs/ftldns/debugging.md index ed520b2..d5e88e5 100644 --- a/docs/ftldns/debugging.md +++ b/docs/ftldns/debugging.md @@ -23,5 +23,3 @@ Once you are used to it, you can skip most of the steps. Debugging *FTL*DNS is q 3. When `pihole-FTL` has crashed, copy & paste the terminal output into a (new) issue. Also, type `backtrace` and include its output. We might ask for additional information in order to isolate your particular issue. - -{!abbreviations.md!} diff --git a/docs/ftldns/dns-cache.md b/docs/ftldns/dns-cache.md index cd8cf32..e2ed3bd 100644 --- a/docs/ftldns/dns-cache.md +++ b/docs/ftldns/dns-cache.md @@ -37,5 +37,3 @@ This information may also be queried using `dig +short chaos txt insertions.bind The number of cache entries that had to be removed although the corresponding entries were **not** expired. Old cache entries get removed if the cache is full to make space for more recent domains. The cache size should be increased when this number is larger than zero. This information may also be queried using `dig +short chaos txt evictions.bind` - -{!abbreviations.md!} diff --git a/docs/ftldns/dns-resolver.md b/docs/ftldns/dns-resolver.md index 0142439..78b7863 100644 --- a/docs/ftldns/dns-resolver.md +++ b/docs/ftldns/dns-resolver.md @@ -24,5 +24,3 @@ The DNS forward destination determination algorithm in *FTL*DNS's is modified to We keep the exceptions, i.e., we try all possible forward destinations if `SERVFAIL` or `REFUSED` is received or if a timeout occurs. Overall, this change has proven to greatly reduce the number of actually performed queries in typical Pi-hole environments. It may even be understood as being preferential in terms of privacy (as we send queries much less often to all servers). This has been implemented in commit [d1c163e](https://github.com/pi-hole/FTL/commit/d1c163e499a5cd9f311610e9da1e9365bbf81e89). - -{!abbreviations.md!} diff --git a/docs/ftldns/in-depth.md b/docs/ftldns/in-depth.md index 7d06026..e021f83 100644 --- a/docs/ftldns/in-depth.md +++ b/docs/ftldns/in-depth.md @@ -40,5 +40,3 @@ We specifically add the following capabilities to `pihole-FTL`: - `CAP_NET_ADMIN`: modify routing tables and other network-related operations (to allow for handling DHCP requests) Users that cannot use Linux capabilities for various reasons (lacking kernel or file system support) can modify the startup scripts of `pihole-FTL` to ensure the daemon is started as `root`. However, be aware that you do so on your own risk (although we don't expect problems to arise). - -{!abbreviations.md!} diff --git a/docs/ftldns/index.md b/docs/ftldns/index.md index bd8c627..8fb9b0e 100644 --- a/docs/ftldns/index.md +++ b/docs/ftldns/index.md @@ -6,5 +6,3 @@ *FTL*DNS[™](https://pi-hole.net/trademark-rules-and-brand-guidelines/) (`pihole-FTL`) offers DNS services within the Pi-hole[®](https://pi-hole.net/trademark-rules-and-brand-guidelines/) project. It provides blazing fast DNS and DHCP services. It can also provide TFTP and more as the resolver part based on the popular `dnsmasq`. Furthermore, FTL offers an interactive API where extensive network analysis data and statistics may be queried. - -{!abbreviations.md!} diff --git a/docs/ftldns/interfaces.md b/docs/ftldns/interfaces.md index 05c03b0..c57edab 100644 --- a/docs/ftldns/interfaces.md +++ b/docs/ftldns/interfaces.md @@ -64,5 +64,3 @@ except-interface=nonexisting ``` is used. We add this option to disable any possible `local-service` settings in other config files. - -{!abbreviations.md!} diff --git a/docs/ftldns/package_dump.md b/docs/ftldns/package_dump.md index 1319e4f..5b69149 100644 --- a/docs/ftldns/package_dump.md +++ b/docs/ftldns/package_dump.md @@ -30,5 +30,3 @@ If you just want to record everything and later filter this in Wireshark you can dumpfile=/etc/pihole/dump.pcap dumpmask=0x00ff ``` - -{!abbreviations.md!} diff --git a/docs/ftldns/privacylevels.md b/docs/ftldns/privacylevels.md index d6ba102..73a4177 100644 --- a/docs/ftldns/privacylevels.md +++ b/docs/ftldns/privacylevels.md @@ -38,5 +38,3 @@ This setting disables - Clients over time - Query Log - Long-term database logging - -{!abbreviations.md!} diff --git a/docs/ftldns/signals.md b/docs/ftldns/signals.md index 4a58eae..65331ac 100644 --- a/docs/ftldns/signals.md +++ b/docs/ftldns/signals.md @@ -74,5 +74,3 @@ Re-resolve all clients and forward destination hostnames. This forces refreshing ## Real-time signal 5 (SIG39) Re-parse ARP/neighbour-cache now to update the Network table now - -{!abbreviations.md!} diff --git a/docs/ftldns/telnet-api.md b/docs/ftldns/telnet-api.md index 621644f..53cf00c 100644 --- a/docs/ftldns/telnet-api.md +++ b/docs/ftldns/telnet-api.md @@ -279,5 +279,3 @@ Column definitions are: 7. Associated IPv6 addresses The default interface (the one connected to the gateway) will always be the first. The sum will always be the last one - even if you have (for whatever reason) an interface called sum. Regarding the link speed: It won't work for most WiFi interfaces as the speed is not known at the kernel level. Instead, the drivers manage them dynamically depending on package loss, signal strength, etc. - in this case, you'll see link speed -1 as well - -{!abbreviations.md!} diff --git a/docs/ftldns/valgrind.md b/docs/ftldns/valgrind.md index e232760..2f90829 100644 --- a/docs/ftldns/valgrind.md +++ b/docs/ftldns/valgrind.md @@ -217,5 +217,3 @@ As forking relies on [copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write ==2681688== by 0x4AF1292: clone (clone.S:95) ``` - -{!abbreviations.md!} diff --git a/docs/guides/misc/benchmark.md b/docs/guides/misc/benchmark.md index c1d4ec1..af281fb 100644 --- a/docs/guides/misc/benchmark.md +++ b/docs/guides/misc/benchmark.md @@ -46,5 +46,3 @@ time dig -f domains.list +noall +answer > /dev/null ``` for mass querying the domains from your list. This will show you how much time it takes to query the number of domains you extracted from the database. - -{!abbreviations.md!} diff --git a/docs/guides/vpn/wireguard/client.md b/docs/guides/vpn/wireguard/client.md index 3bf2769..87bdc3d 100644 --- a/docs/guides/vpn/wireguard/client.md +++ b/docs/guides/vpn/wireguard/client.md @@ -236,5 +236,3 @@ peer: F+80gbmHVlOrU+es13S18oMEX2g= ⬅ Your peer's public key will be differen You should run a DNS leak test on [www.dnsleaktest.com](https://www.dnsleaktest.com) to ensure your WireGuard tunnel does not leak DNS requests (so all are processed by your Pi-hole). The expected outcome is that you should only see DNS servers belonging to the upstream DNS destination you selected in Pi-hole. If you configured [Pi-hole as All-Around DNS Solution](/guides/dns/unbound/), you should only see the public IP address of your WireGuard server and no other DNS server. See also [What is a DNS leak and why should I care?](https://www.dnsleaktest.com/what-is-a-dns-leak.html) (external link). - -{!abbreviations.md!} diff --git a/docs/guides/vpn/wireguard/overview.md b/docs/guides/vpn/wireguard/overview.md index b24eefe..a8b1a61 100644 --- a/docs/guides/vpn/wireguard/overview.md +++ b/docs/guides/vpn/wireguard/overview.md @@ -26,5 +26,3 @@ Via this VPN, you can: - reroute your entire Internet traffic through your Pi-hole (*optional*) from everywhere around the globe. - -{!abbreviations.md!} diff --git a/docs/guides/vpn/wireguard/route-everything.md b/docs/guides/vpn/wireguard/route-everything.md index 760b2a7..3c87c77 100644 --- a/docs/guides/vpn/wireguard/route-everything.md +++ b/docs/guides/vpn/wireguard/route-everything.md @@ -45,5 +45,3 @@ AllowedIPs = 0.0.0.0/0, ::/0 That's all you need to do. You should use an online check (e.g. www.wieistmeineip.de) to check if your IP changed to the public IP address of your WireGuard server after this change. It is possible to add this change only for a few clients, leaving the others without a full tunnel for all traffic (e.g., where this is not necessary or not desired). - -{!abbreviations.md!} diff --git a/docs/guides/vpn/wireguard/server.md b/docs/guides/vpn/wireguard/server.md index 599ebf9..7d8a9a3 100644 --- a/docs/guides/vpn/wireguard/server.md +++ b/docs/guides/vpn/wireguard/server.md @@ -237,5 +237,3 @@ Your public key will be different from ours. This is expected (you just created On your [Settings page (tab DNS)](http://pi.hole/admin/settings.php?tab=dns), ensure you set the listing mode of your Pi-hole to one of the `Listen of all interfaces` settings. The top one is preferred as it adds a bit of additional safety. Your WireGuard peers/clients will be correctly recognized as being only one hop away. You can now continue to add clients. - -{!abbreviations.md!} diff --git a/docs/index.md b/docs/index.md index 53e7842..de85e7a 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,7 +1,6 @@ --- title: Overview of Pi-hole description: Brief overview of Pi-hole -last_updated: Thur May 02 01:00:00 2019 UTC ---

@@ -57,5 +56,3 @@ We welcome _everyone_ to contribute to issue reports, suggest new features, and If you have something to add - anything from a typo through to a whole new feature, we're happy to check it out! Just make sure to fill out our template when submitting your request; the questions that it asks will help the volunteers quickly understand what you're aiming to achieve. You'll find that the [install script](https://github.com/pi-hole/pi-hole/blob/master/automated%20install/basic-install.sh) and the [debug script](https://github.com/pi-hole/pi-hole/blob/master/advanced/Scripts/piholeDebug.sh) have an abundance of comments, which will help you better understand how Pi-hole works. They're also a valuable resource to those who want to learn how to write scripts or code a program! We encourage anyone who likes to tinker to read through it, and submit a pull request for us to review. - -{!abbreviations.md!} diff --git a/docs/main/basic-install.md b/docs/main/basic-install.md index 9bb92bd..3604670 100644 --- a/docs/main/basic-install.md +++ b/docs/main/basic-install.md @@ -31,5 +31,3 @@ sudo bash basic-install.sh ### Alternative 3: Use Docker to deploy Pi-hole Please refer to the [Pi-hole docker repo](https://github.com/pi-hole/docker-pi-hole) to use the Official Docker Images. - -{!abbreviations.md!} diff --git a/docs/main/faq.md b/docs/main/faq.md index 95b81ce..efa659f 100644 --- a/docs/main/faq.md +++ b/docs/main/faq.md @@ -105,5 +105,3 @@ Restart the web server: ```bash sudo service lighttpd restart ``` - -{!abbreviations.md!} diff --git a/docs/main/origins.md b/docs/main/origins.md index d899a83..8acd918 100644 --- a/docs/main/origins.md +++ b/docs/main/origins.md @@ -15,4 +15,3 @@ Pi-hole being a **advertising-aware DNS/Web server**, makes use of the following While quite outdated at this point, [this original blog post about Pi-hole](https://jacobsalmela.com/2015/06/16/block-millions-ads-network-wide-with-a-raspberry-pi-hole-2-0/) goes into **great detail** about how Pi-hole was originally set up and how it works. Syntactically, it's no longer accurate, but the same basic principles and logic still apply to Pi-hole's current state. -{!abbreviations.md!} diff --git a/docs/main/post-install.md b/docs/main/post-install.md index b984fe6..1f29d85 100644 --- a/docs/main/post-install.md +++ b/docs/main/post-install.md @@ -18,5 +18,3 @@ Pi-hole will not be used by the host automatically after installation. To have t ```code static domain_name_servers=127.0.0.1 ``` - -{!abbreviations.md!} diff --git a/docs/main/prerequisites.md b/docs/main/prerequisites.md index d629f46..3f89ecf 100644 --- a/docs/main/prerequisites.md +++ b/docs/main/prerequisites.md @@ -150,5 +150,3 @@ IPv6 (include above IPv4 rules): ```bash ufw allow 546:547/udp ``` - -{!abbreviations.md!} diff --git a/docs/main/uninstall.md b/docs/main/uninstall.md index 614de14..4eacf06 100644 --- a/docs/main/uninstall.md +++ b/docs/main/uninstall.md @@ -4,5 +4,3 @@ Pi-hole can be uninstalled using: !!! warning If you are unsure whether a package should be removed during uninstalling, we'd recommend leaving it installed, as required system packages may be among them! - -{!abbreviations.md!} diff --git a/docs/main/update.md b/docs/main/update.md index 749a8c9..cf0da44 100644 --- a/docs/main/update.md +++ b/docs/main/update.md @@ -1,5 +1,3 @@ Updating is as simple as running the following command: `pihole -up` - -{!abbreviations.md!} diff --git a/docs/regex/approximate.md b/docs/regex/approximate.md index b0485b0..1846f39 100644 --- a/docs/regex/approximate.md +++ b/docs/regex/approximate.md @@ -92,6 +92,3 @@ This sets the cost of an insertion to two, a deletion to one, a substitution to Example 2: `{+2-5#6, 2i + 1d + 2s < 5 }` This sets the cost of an insertion to two, a deletion to one, a substitution to two, and the maximum cost to five. Furthermore, it allows only up to 2 insertions (coming at a total cost of 4), five deletions and up to 6 substitutions. As six substitutions would come at a cost of `6*2 = 12`, exceeding the total allowed costs of 5, they cannot all be realized. - - -{!abbreviations.md!} diff --git a/docs/regex/overview.md b/docs/regex/overview.md index 1e1d135..70bc19d 100644 --- a/docs/regex/overview.md +++ b/docs/regex/overview.md @@ -41,5 +41,3 @@ Once the debugging mode is enabled, each match will be logged to `/var/log/pihol The given DB ID corresponds to the ID of the corresponding row in the `domainlist` database table. Note that validation is only done on the first occurrence of a domain to increase the computational efficiency of *FTL*DNS. The result of this evaluation is stored in an internal DNS cache that is separate from `dnsmasq`'s own DNS cache. This allows us to only flush this special cache when modifying the black- and whitelists *without* having to flush the entire DNS cache collected so far. - -{!abbreviations.md!} diff --git a/docs/regex/pi-hole.md b/docs/regex/pi-hole.md index a30107c..b1691ee 100644 --- a/docs/regex/pi-hole.md +++ b/docs/regex/pi-hole.md @@ -180,5 +180,3 @@ Furthermore, there are two shortcuts for some character classes: - `\d` - Digit character (equivalent to `[[:digit:]]`) - `\D` - Non-digit character (equivalent to `[^[:digit:]]`) - -{!abbreviations.md!} diff --git a/docs/regex/testmode.md b/docs/regex/testmode.md index 7211af6..9b0e28a 100644 --- a/docs/regex/testmode.md +++ b/docs/regex/testmode.md @@ -15,5 +15,3 @@ pihole-FTL regex-test doubleclick.net "(^|\.)double" (test `doubleclick.net` against the CLI-provided regex `(^|\.)double`. You do NOT need to be `sudo` for this, any arbitrary user should be able to run this command. The test returns `0` on match and `1` on no match and errors, hence, it may be used for scripting. - -{!abbreviations.md!} diff --git a/docs/regex/tutorial.md b/docs/regex/tutorial.md index c478b1b..d876634 100644 --- a/docs/regex/tutorial.md +++ b/docs/regex/tutorial.md @@ -140,5 +140,3 @@ Expression | Meaning | Example `[^]`| Negation | `[^0-9]` matches any character *except* `0` to `9` `{ }` | Matches a specified number of occurrences of the previous | `[0-9]{3}` matches any three-digit number like `315` but not `31`;
`[0-9]{2,4}` matches two- to four-digit numbers like `12`, `123`, and `1234` but not `1` or `12345`;
`[0-9]{2,}` matches any number with two or more digits like `1234567`, `123456789`, but not `1` `\` | Used to escape a special character not inside `[]` | `google\.com` matches `google.com` - -{!abbreviations.md!} diff --git a/docs/routers/asus.md b/docs/routers/asus.md index eb16c46..6dfb949 100644 --- a/docs/routers/asus.md +++ b/docs/routers/asus.md @@ -3,5 +3,3 @@ ASUS was so kind to set up a FAQ how to configure their routers together with Pi They offer two kinds of setup depending on your router's firmware version. On newer firmware they recommend setting Pi-hole as DNS server for the `WAN` connection and on older versions for `LAN` connections. However, we recommend to setup Pi-hole always as DNS server for your `LAN`! If you do so, Pi-hole's IP is distributed as DNS server via DHCP to your network clients. Each client will directly send their queries to Pi-hole and will be shown individually in Pi-hole's web interface. Additionally, you can use the group management features. You can find the FAQ here: [https://www.asus.com/support/FAQ/1046062/](https://www.asus.com/support/FAQ/1046062/) - -{!abbreviations.md!} diff --git a/mkdocs.yml b/mkdocs.yml index 1a6708e..2cd2676 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -43,13 +43,20 @@ theme: markdown_extensions: # Code highlighting in ``` ``` blocks - - codehilite: - guess_lang: true + # https://squidfunk.github.io/mkdocs-material/setup/extensions/python-markdown-extensions/#highlight + - pymdownx.highlight: + - pymdownx.superfences + - pymdownx.inlinehilite # Table of Contents + # https://python-markdown.github.io/extensions/toc/ - toc: permalink: true # block-styled side content + # https://squidfunk.github.io/mkdocs-material/reference/admonitions/ - admonition + # https://squidfunk.github.io/mkdocs-material/setup/extensions/python-markdown-extensions/#details + - pymdownx.details + # linkifies URL and email links without having to wrap them in Markdown syntax. Also, allows shortens repository issue, pull request, and commit links. - pymdownx.magiclink # Task lists (https://facelessuser.github.io/pymdown-extensions/extensions/tasklist/) @@ -62,22 +69,21 @@ markdown_extensions: # This extension is a convenience extension which includes many pymdownx extensions # (https://facelessuser.github.io/pymdown-extensions/extensions/extra/) - pymdownx.extra - # (https://facelessuser.github.io/pymdown-extensions/extensions/details/) - - pymdownx.details + # Tabbed provides a syntax to easily add tabbed Markdown content. # https://facelessuser.github.io/pymdown-extensions/extensions/tabbed/ - pymdownx.tabbed: alternate_style: true - # Adds syntax for defining footnotes in Markdown documents (https://python-markdown.github.io/extensions/footnotes/) + # Adds syntax for defining footnotes in Markdown documents (https://squidfunk.github.io/mkdocs-material/reference/footnotes/) - footnotes - # Adds the ability to define abbreviations + # Adds the ability to define abbreviations (https://squidfunk.github.io/mkdocs-material/reference/tooltips/) - abbr - # Include files in other documents like {!some/dir/in/docs/filename.md!} - - markdown_include.include: - base_path: docs - # Metadata support in pages - # (https://squidfunk.github.io/mkdocs-material/extensions/metadata/) - - meta + - attr_list + - pymdownx.snippets: + # auto_append abbreviations.md to every file + # https://squidfunk.github.io/mkdocs-material/reference/tooltips/#adding-a-glossary + auto_append: + - docs/abbreviations.md nav: - Overview: index.md diff --git a/requirements.txt b/requirements.txt index 8c3150f..0398f2d 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,4 +1,3 @@ -markdown-include==0.8.0 mkdocs==1.4.2 mkdocs-git-revision-date-localized-plugin==1.1.0 mkdocs-material==8.5.11