✨ Improve code blocks, update admonitions

.gitattributes

@@ -1,2 +1,3 @@
 theme/* linguist-vendored
+scripts/* linguist-vendored
 *.md linguist-detectable

README.md

@@ -18,14 +18,6 @@ You can install them all at once by running the appropiate installer script in
 the `install` with your shell:
 
 ```console
-sh ./install
-```
-
-```powershell
-powershell .\install
-```
-
-```console
-nu ./install
+./install
 ```
 

book.toml

@@ -8,7 +8,7 @@ src = "src"
 
 [preprocessor.admonish]
 command = "mdbook-admonish"
-assets_version = "2.0.1" # do not edit: managed by `mdbook-admonish install`
+assets_version = "3.0.0" # do not edit: managed by `mdbook-admonish install`
 
 [preprocessor.toc]
 command = "mdbook-toc"
@@ -17,7 +17,8 @@ renderer = ["html"]
 [preprocessor.webinclude]
 
 [output.html]
-additional-css = ["./theme/mdbook-admonish.css"]
+additional-css = ["./theme/mdbook-admonish.css", "./theme/mdbook-admonish.css", "./theme/codeblockplus.css"]
+additional-js = ["./scripts/codeblockplus.js"]
 curly-quotes = true
 default-theme = "coal"
 preferred-dark-theme = "coal"

install

@@ -1,4 +1,8 @@
+#!/usr/bin/env sh
+
 cargo install --force --version 0.4.35 mdbook
-cargo install --force --version 1.12.1 mdbook-admonish
+cargo install --force --version 1.13.0 mdbook-admonish
 cargo install --force --version 0.14.1 mdbook-toc
 cargo install --force --version 0.1.0 mdbook-webinclude
+echo $(curl -sS https://raw.githubusercontent.com/phoenixr-codes/mdbook-code-block-plus/master/codeblockplus.css) > theme/codeblockplus.css
+echo $(curl -sS https://raw.githubusercontent.com/phoenixr-codes/mdbook-code-block-plus/master/codeblockplus.min.js) > scripts/codeblockplus.js

src/README.md

@@ -55,14 +55,14 @@ control and generation.
 allay add templating
 ```
 
-```erb
+```erb,lang=mcfunction
 <%# using erb %>
 <% 10.times do |i| %>
 scoreboard objectives add position<%= i %>
 <% end %>
 ```
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts"
 pre = [

src/dev/scripts/configuration.md

@@ -10,8 +10,7 @@ Most programming languages a capable of reading arguments provided in the
 command-line. Rust uses these method to allow users to provide options
 specific to a script in the configuration file.
 
-```python
-# FILE: helloworld.py
+```python,filepath=scripts/helloworld.py
 from argparse import ArgumentParser
 
 parser = ArgumentParser()
@@ -25,7 +24,7 @@ One can then provide arguments in their configuration file like this:
 
 ```toml
 [scripts]
-# ...
+base-path = "scripts"
 pre = [
   { run = "helloworld.py", with = "python", args = ["John Doe", "42"] }
 ]
@@ -51,9 +50,7 @@ Another less recommended approach is the usage of the
 file. It is designed to be used by external programs but parsing TOML is less
 supported than parsing command-line arguments in many programming languages.
 
-```python
-# FILE: helloworld.py
-
+```python,filepath=scripts/helloworld.py
 import os
 from pathlib import Path
 import tomllib

src/example-project/README.md

@@ -7,21 +7,17 @@ a behavior pack as well as an resource pack.
 
 ## Step 1: Initialize the project
 
-> **Bash**
-> 
-> ```bash
-> mkdir lost-sword
-> cd lost-sword
-> allay init
-> ```
-
-> **PowerShell**
->
-> ```powershell
-> New-Item -Path . -Name "lost-sword" -ItemType "directory"
-> Set-Location -Path '.\lost-sword'
-> allay init
-> ```
+```bash
+mkdir lost-sword
+cd lost-sword
+allay init
+```
+
+```powershell
+New-Item -Path . -Name "lost-sword" -ItemType "directory"
+Set-Location -Path '.\lost-sword'
+allay init
+```
 
 
 ## Step 2: Configure the World Template

src/reference/configuration.md

@@ -28,7 +28,7 @@ scripts as well.
 The name of the project which will be used for the individual add-ons as well
 unless overridden with `pack.*.name` where `*` is one of `bp`, `rp`, `sp` or `wt`.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project.name]
 de-de = "Hallo Welt"
 en-us = "Hello World"
@@ -40,7 +40,7 @@ The description of the project which will be used for the individual add-ons as
 well unless overridden with `pack.*.description` where `*` is one of `bp`, `rp`,
 `sp` or `wt`.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project.description]
 de-de = "Das ist mein tolles Projekt."
 en-us = "This is my amazing project."
@@ -53,7 +53,7 @@ en-us = "This is my amazing project."
 The version of the project of the form `n.n.n` where `n` is any natural number or
 zero.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project]
 # ...
 version = "0.1.0"
@@ -66,7 +66,7 @@ Specifies whether the project is currently in development. This has impact on th
 build process and maybe some scripts. This behavior can be overridden with
 `allay build --release`.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project]
 # ...
 development = true
@@ -88,7 +88,7 @@ An array of people that are considered the "authors" of the project. An optional
 email address may be included within angled brackets at the end of each author
 entry.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project]
 # ...
 authors = ["John Doe", "Joana Doe <[email protected]>"]
@@ -100,7 +100,7 @@ authors = ["John Doe", "Joana Doe <[email protected]>"]
 The name of the license(s). You might want to include a `LICENSE.txt` file in the
 root of your project which contains the content of the license.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project]
 # ...
 license = "MIT OR Apache-2.0"
@@ -111,7 +111,7 @@ license = "MIT OR Apache-2.0"
 
 The URL to a site that is the home page for your project.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [project]
 # ...
 url = "https://github.com/allay-mc/example"

src/scripts/README.md

@@ -7,7 +7,7 @@ used to convert between file types such as [JSON5](https://json5.org/) to
 
 Scripts are executed in order how they are specified in the configuration file.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts/"
 pre = [
@@ -41,7 +41,7 @@ project
 
 Then you can refer to the scripts like this in your configuration file.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts"
 pre = [

src/scripts/conditional.md

@@ -4,7 +4,7 @@ There are often cases where one want to execute simple commands such as
 [`tsc`](https://www.typescriptlang.org/docs/handbook/compiler-options.html) to
 transpile TypeScript along with dynamic arguments such as environment variables.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts/"
 pre = [
@@ -33,7 +33,7 @@ Get-ChildItem * -Include *.ts -Recurse | Remove-Item  # remove TypeScript files
 
 The configuration would then look like this:
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts/"
 pre = [
@@ -107,7 +107,7 @@ first or chained and modified with the following operators:
 
 Conditions can be wrapped in parentheses to group them:
 
-```
+```text
 (condition1 & condition2) | condition3
 ```
 

src/scripts/executables.md

@@ -1,6 +1,6 @@
 # Running Executables
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 # ...
 pre = [

src/scripts/options.md

@@ -3,7 +3,7 @@
 Some scripts might accept additional options which can be set with the `args`
 field.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts/"
 pre = [
@@ -23,7 +23,7 @@ the command-line. Note that arguments are not pre-processed like shells do meani
 you cannot use [glob patterns](https://en.wikipedia.org/wiki/Glob_(programming)) or
 environment variables.
 
-```toml
+```toml,icon=gear,filepath=allay.toml
 [scripts]
 base-path = "scripts/"
 pre = [