chore: rename DoGe -> vim-doge; update CHANGELOG; add ToC in all MD files

Author: kkoomen

.github/ISSUE_TEMPLATE/bug_report.md

@@ -35,7 +35,7 @@ generate documentation.
 **Settings**
 
 <!--
-If applicable, describe your custom DoGe settings like so:
+If applicable, describe your custom vim-doge settings like so:
 
 ```vim
 let g:doge_mapping = '<Leader>f'

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,12 +1,12 @@
 # Prelude
 
-Thank you for helping out DoGe!
+Thank you for helping out vim-doge!
 
 <!--
 Replace [ ] with [x] with those you agree with.
 -->
 
-By contributing to DoGe you agree to the following statements:
+By contributing to vim-doge you agree to the following statements:
 
 - [ ] I have read and understood the [Contribution Guidelines](https://github.com/kkoomen/vim-doge/blob/master/CONTRIBUTING.md).
 - [ ] I have read and understood the [Code of Conduct](https://github.com/kkoomen/vim-doge/blob/master/CODE_OF_CONDUCT.md).

CHANGELOG.md

@@ -1,3 +1,40 @@
+## [4.0.0](https://github.com/kkoomen/vim-doge/compare/v3.22.0...v4.0.0)
+
+In v4 a new custom [vim-doge-helper](./helper/) has been created, completely
+developed in Rust from scratch, being a replacement for the old NodeJS version
+that vim-doge had in v3.
+
+This new version resolves the following problems that existed prior to v4:
+- Failing Windows builds due to node-gyp build problems
+- Templating limitations: v4 contained basic templating functionality that
+  was customly written, as opposed to v4 that uses
+  [Tera](https://tera.netlify.app/docs)
+- Limited platform builds: v3 required due to NodeJS that binaries were created
+  on the target machine itself that it was eventually used for. Windows builds
+  had to be created on a windows runner and support for Apple Silicon had to be
+  build on arm64 machines, but v4 can use the power of cross-compilation of Rust
+  (through LLVM) to make builds for any platform we want, all on a single
+  machine.
+- Tree-sitter language limitations: v3 required parsers to be published on NPM,
+  but these packages weren't maintained that well. If there was no package of a
+  certain parser on NPM, then we simply can't implement the language. With v4 we
+  can use the tree-sitter GitHub source to be included in Cargo.toml that can
+  link everything properly from C to Rust and we don't need any third-party
+  package manager anymore in-between vim-doge and tree-sitter.
+- Vimscript logic: v3 contained docblock generating logic that should actually
+  not be managed in vim. For example, It used plain regex to do some additional
+  pre/post-processing rather than using tree-sitter. In v4 all the logic has
+  been moved to the [vim-doge-helper](./helper/) and all the vimscript code is
+  only a bridge between the user and the vim-doge-helper.
+- Speed: v4 allows docblocks to be generated with the blink of an eye, as
+  opposed to v3 where users had to wait a bit, and even worse, the first
+  docblock genereration you did in v3 after you've downloaded the vim-doge
+  binary, did require NodeJS to start the runtime which would take a second or
+  two.
+
+
+Besides the above being resolved,
+
 ## [3.22.0](https://github.com/kkoomen/vim-doge/compare/v3.21.0...v3.22.0) (2023-06-10)
 
 ### Features

CONTRIBUTING.md

@@ -11,21 +11,18 @@ When contributing make sure you have read and understood the
 
 - [Contribution Guidelines](#contribution-guidelines)
 - [Table of Contents](#table-of-contents)
-- [How does DoGe work?](#how-does-doge-work)
+- [How does vim-doge work?](#how-does-vim-doge-work)
 - [Topics](#topics)
-  - [Linting](#linting)
-  - [Documentation](#documentation)
-  - [Doc standard](#doc-standard)
-  - [Filetype / language](#filetype--language)
-  - [Configurable setting](#configurable-setting)
-  - [Code](#code)
-  - [Tests](#tests)
+  * [Linting](#linting)
+  * [Documentation](#documentation)
+  * [Doc standard](#doc-standard)
+  * [Filetype / language](#filetype--language)
+  * [Configurable setting](#configurable-setting)
+  * [Code](#code)
+  * [Tests](#tests)
 - [Tips](#tips)
-  - [Writing your first pattern](#writing-your-first-pattern)
-    - [Additional token formatting](#additional-token-formatting)
-      - [Creating TODO placeholders](#creating-todo-placeholders)
-      - [Default value](#default-value)
-      - [Conditional rendering](#conditional-rendering)
+  * [Parsers](#parsers)
+    + [Doc standards templating](#doc-standards-templating)
 
 # How does vim-doge work?
 

helper/README.md

@@ -2,7 +2,14 @@
 
 Helper extension for the [vim-doge](https://github.com/kkoomen/vim-doge)
 plugin that parses code in order to generate docblocks using
-[tree-sitter](https://github.com/tree-sitter/tree-sitter).
+[tree-sitter](https://github.com/tree-sitter/tree-sitter), written in Rust.
+
+# Table of Contents
+- [vim-doge-helper](#vim-doge-helper)
+- [Table of Contents](#table-of-contents)
+- [Installation](#installation)
+- [Usage](#usage)
+- [Contributing](#contributing)
 
 # Installation
 

plugin/doge.vim

@@ -62,7 +62,7 @@ if !exists('g:doge_mapping')
   ""
   " (Default: '<Leader>d')
   "
-  " The mapping to trigger DoGe. The mapping accepts a count, to select a
+  " The mapping to trigger vim-doge. The mapping accepts a count, to select a
   " specific doc standard, if more than one is defined.
   let g:doge_mapping = '<Leader>d'
 endif

test/options/doge_buffer_mappings.vader

@@ -15,7 +15,7 @@ Do (trigger doge):
   \<Tab>
   Lorem ipsum
 
-# Trigger an additional <Tab> to deactivate DoGe.
+# Trigger an additional <Tab> to deactivate vim-doge.
   \<Tab>
 
 Then (all buffer mappings should not exists anymore):