docs/manual: convert release notes to markdown

docs/manual/default-configs/maximal.md

@@ -6,6 +6,8 @@ $ nix shell github:notashelf/neovim-flake#maximal test.nix
 
 It is the same fully configured neovim as with the [Nix](#sec-default-nix) config, but with every supported language enabled.
 
-::: note
+:::{.note}
+
 Running the maximal config will download _a lot_ of packages as it is downloading language servers, formatters, and more.
+
 :::

docs/manual/hacking/guidelines.md

@@ -15,7 +15,10 @@ Most, if not all, changes warrant changes to the documentation. Module options s
 [Nixpkgs-flavoured Markdown](https://nixos.org/manual/nixpkgs/unstable/#sec-contributing-markup), albeit with exceptions.
 
 :::{.note}
-As of v0.6, neovim-flake is itself documented using full markdown in both module options and the manual.
+
+As of v0.5, neovim-flake is itself documented using full markdown in both module options and the manual. With
+v0.6, this manual has also been converted to markdown in full.
+
 :::
 
 The HTML version of this manual containing both the module option descriptions and the documentation of neovim-flake
@@ -44,9 +47,9 @@ a pull request should make sense both on its own and in general context. That is
 an issue that is introduced in an earlier commit. In particular, you will be asked to amend any commit that
 introduces syntax errors or similar problems even if they are fixed in a later commit.
 
-The commit messages should follow the {seven-rules}[seven rules], except for "Capitalize the subject line".
-We also ask you to include the affected code component or module in the first line.
-A commit message ideally, but not necessarily, follow the given template from home-manager's own documentation
+The commit messages should follow the [seven rules](https://chris.beams.io/posts/git-commit/#seven-rule),
+except for "Capitalize the subject line". We also ask you to include the affected code component or module in
+the first line. A commit message ideally, but not necessarily, follow the given template from home-manager's own documentation
 
 ```
   {component}: {description}
@@ -57,11 +60,11 @@ A commit message ideally, but not necessarily, follow the given template from ho
 where `{component}` refers to the code component (or module) your change affects, `{description}` is a very brief
 description of your change, and `{long description}` is an optional clarifying description. As a rare exception, if
 there is no clear component, or your change affects many components, then the `{component}` part is optional.
-See <<ex-commit-message>> for a commit message that fulfills these requirements.
+See [example commit message](#sec-guidelines-ex-commit-message) for a commit message that fulfills these requirements.
 
 ## Example Commit {#sec-guidelines-ex-commit-message}
 
-The commit {example-commit-message}[69f8e47e9e74c8d3d060ca22e18246b7f7d988ef] contains the commit message
+The commit [69f8e47e9e74c8d3d060ca22e18246b7f7d988ef](https://github.com/nix-community/home-manager/commit/69f8e47e9e74c8d3d060ca22e18246b7f7d988ef) contains the commit message
 
 ```
 

docs/manual/hacking/keybinds.md

@@ -1,13 +1,11 @@
 # Keybinds {#sec-keybinds}
 
 As of 0.4, there exists an API for writing your own keybinds and a couple of useful utility functions are available in
-the https://github.com/NotAShelf/neovim-flake/tree/main/lib[extended standard library]. The following section contains
+the [extended standard library](https://github.com/NotAShelf/neovim-flake/tree/main/lib). The following section contains
 a general overview to how you may utilize said functions.
 
 ## Custom Key Mappings Support for a Plugin {#sec-custom-key-mappings}
 
-:maps: https://notashelf.github.io/neovim-flake/options.html#opt-vim.maps.command._name_.action
-
 To set a mapping, you should define it in `vim.maps.<<mode>>`.
 The available modes are:
 
@@ -37,7 +35,9 @@ An example, simple keybinding, can look like this:
 }
 ```
 
-There are many settings available in the options. Please refer to the {maps}[documentation] to see a list of them.
+There are many settings available in the options. Please refer to the
+[documentation](https://notashelf.github.io/neovim-flake/options.html#opt-vim.maps.command._name_.action)
+to see a list of them.
 
 `neovim-flake` provides a list of helper commands, so that you don't have to write the mapping attribute sets every
 time:

docs/manual/manual.md

@@ -20,3 +20,7 @@ hacking.md
 ```{=include=} appendix html:into-file=//options.html
 options.md
 ```
+
+```{=include=} appendix html:into-file=//release-notes.html
+release-notes/release-notes.md
+```