zaphosting · fgalz · Oct 22, 2025 · Oct 17, 2025 · Oct 22, 2025 · Oct 22, 2025
diff --git a/anchor.js b/anchor.js
@@ -0,0 +1,55 @@
+const fs = require("fs");
+const path = require("path");
+
+// Hauptordner
+const rootDir = "./docs";
+
+// Sprachverzeichnisse laut deiner Docusaurus-Konfiguration
+const locales = ["en", "de", "es", "fr", "ar", "pt", "th", "pl", "ja"];
+
+function walkDir(dir, callback) {
+  if (!fs.existsSync(dir)) return;
+  for (const file of fs.readdirSync(dir)) {
+    const full = path.join(dir, file);
+    const stat = fs.statSync(full);
+    if (stat.isDirectory()) walkDir(full, callback);
+    else if (file.endsWith(".md") || file.endsWith(".mdx")) callback(full);
+  }
+}
+
+function cleanFile(filePath) {
+  let content = fs.readFileSync(filePath, "utf8");
+  const original = content;
+
+  // 1. Entfernt Anker in Links auf Markdown-Dateien
+  //    z. B. (guide.md#anchor) → (guide.md)
+  content = content.replace(/\(([\w./-]+\.mdx?(#[^)]+))\)/gi, match =>
+    match.replace(/#.*(?=\))/, "")
+  );
+
+  // 2. Entfernt reine lokale Anker-Links
+  //    z. B. [section](#section) → section
+  content = content.replace(/\[([^\]]+)\]\(#([\w.-]+)\)/gi, "$1");
+
+  if (content !== original) {
+    fs.writeFileSync(filePath, content, "utf8");
+    console.log("Bereinigt:", filePath);
+  }
+}
+
+function processDir(baseDir) {
+  if (!fs.existsSync(baseDir)) return;
+  console.log("Starte:", baseDir);
+  walkDir(baseDir, cleanFile);
+}
+
+// Standard-Dokumentation
+processDir(rootDir);
+
+// i18n-Sprachen
+for (const locale of locales) {
+  const localeDocs = path.join("i18n", locale, "docusaurus-plugin-content-docs", "current");
+  processDir(localeDocs);
+}
+
+console.log("Fertig.");
diff --git a/docs/contribution-blogs-guidelines.md b/docs/contribution-blogs-guidelines.md
@@ -11,10 +11,10 @@ In order to ensure that all ZAP-Hosting Blog Posts are consistent in quality and
 
 Our blog contribution guidelines can be split into a few major sections, which are:
 
-- [Structure](#structure)
-- [Style](#style)
-- [Formatting](#formatting)
-- [Terminology](#terminology)
+- Structure
+- Style
+- Formatting
+- Terminology
 
 ## Structure
 

diff --git a/docs/contribution-blogs.md b/docs/contribution-blogs.md
@@ -61,7 +61,7 @@ During this step, you will be writing a new blog post based on the agreed-upon i
 Currently, we accept content using both **Markdown** and **HTML5** styling options.
 
 :::tip
-We can **highly recommend** using the Markdown tool **[StackEdit](https://stackedit.io/app#)** to write your content whilst maintaining all the awesome functionality of Markdown. Alternatively, we can also recommend **[HTML5 Editor](https://html5-editor.net/)** if you prefer to style using HTML5. You could then directly export this to your Google Drive or any file-sharing application and receive a link that you can share with us. You can learn more about Markdown styling via our Blog [Guidelines](contribution-blogs-guidelines.md#formatting)guide.
+We can **highly recommend** using the Markdown tool **[StackEdit](https://stackedit.io/app#)** to write your content whilst maintaining all the awesome functionality of Markdown. Alternatively, we can also recommend **[HTML5 Editor](https://html5-editor.net/)** if you prefer to style using HTML5. You could then directly export this to your Google Drive or any file-sharing application and receive a link that you can share with us. You can learn more about Markdown styling via our Blog [Guidelines](contribution-blogs-guidelines.md)guide.
 :::
 
 :::note

diff --git a/docs/contribution-guides-guidelines.md b/docs/contribution-guides-guidelines.md
@@ -11,18 +11,18 @@ In order to ensure that the content on our ZAP-Docs always remains consistent in
 
 Our guides contribution guidelines are split into the following sections:
 
-- [Structure](#structure)
-- [Style](#style)
-- [Formatting](#formatting)
-- [Terminology](#terminology)
+- Structure
+- Style
+- Formatting
+- Terminology
 
 We recommend browsing these sections at least once before proceeding with writing any content. It is also a useful place to refer to if you are in doubt of how to approach something during the creation process.
 
 ## Structure
 
 All of our guides across our ZAP-Docs follow a relatively consistent structure which begins with an short introduction along with any prerequisites or preparation steps, followed by the main content and a short conclusion.
 
-The structure can be altered occassionally depending on the type of guide produced. This can be discussed with the ZAP-Docs Team within your initial suggestion. You can view how to utilise headings via the [headers](#headers) section, it done through regular traditional Markdown.
+The structure can be altered occassionally depending on the type of guide produced. This can be discussed with the ZAP-Docs Team within your initial suggestion. You can view how to utilise headings via the headers section, it done through regular traditional Markdown.
 
 The structure that we typically expect to see would have the following headings:
 

diff --git a/docs/contribution-guides.md b/docs/contribution-guides.md
@@ -167,7 +167,7 @@ Once you have performed your changes, use the **Commit changes...** button which
 
 ![](https://screensaver01.zap-hosting.com/index.php/s/2iQCZzzAHsHS2rt/preview)
 
-Enter a useful commit message that explains what you have done and an extended description where appropriate. Finally, commit the changes. This will commit it to your fork of the docs. You may now head over to the **[Submitting Content](#step-3-submitting-content)** section to create a Pull Request to submit the content to our main ZAP-Docs Repository.
+Enter a useful commit message that explains what you have done and an extended description where appropriate. Finally, commit the changes. This will commit it to your fork of the docs. You may now head over to the **Submitting Content** section to create a Pull Request to submit the content to our main ZAP-Docs Repository.
 
 </TabItem>
 
@@ -259,10 +259,10 @@ Once you are finished with the changes to your guide, the last step of the entir
 
 ![](https://screensaver01.zap-hosting.com/index.php/s/tFdrLknnXn62sZc/preview)
 
-You may now head over to the **[Submitting Content](#step-3-submitting-content)** section to create a Pull Request to submit the content to our ZAP-Docs Repository.
+You may now head over to the **Submitting Content** section to create a Pull Request to submit the content to our ZAP-Docs Repository.
 
 :::tip
-We recommend that you also read the optional **[Testing build locally](#optional-testing-build-locally)** section, as you can pair this section with testing locally to create an optimal workflow where changes are updated on your local build on-the-go which is proven to be very useful. However, this is not necessary.
+We recommend that you also read the optional **Testing build locally** section, as you can pair this section with testing locally to create an optimal workflow where changes are updated on your local build on-the-go which is proven to be very useful. However, this is not necessary.
 :::
 
 </TabItem>

diff --git a/docs/dedicated-linux-databases.md b/docs/dedicated-linux-databases.md
@@ -55,7 +55,7 @@ First of all, you need to ensure that the latest MariaDB version is being instal
 curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash
 ```
 
-After installing the repo, update your package manager cache by following the steps provided in the [preparation step](#preparation) section.
+After installing the repo, update your package manager cache by following the steps provided in the preparation step section.
 
 :::info
 The MariaDB repo installation (step above) can be safely ignored in modern operating systems like Ubuntu 22.04 or Debian 11.
@@ -142,7 +142,7 @@ sudo yum install epel-release
 sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
 ```
 
-After installing the repo, update your package manager cache by following the steps in the [preparation step](#preparation) section.
+After installing the repo, update your package manager cache by following the steps in the preparation step section.
 
 :::info
 If your operating system is not listed above, then you can avoid this step.

diff --git a/docs/dedicated-linux-dnsserver.md b/docs/dedicated-linux-dnsserver.md
diff --git a/docs/dedicated-linux-docker.md b/docs/dedicated-linux-docker.md
@@ -94,7 +94,7 @@ To verify that your installation is successful, try running the **hello-world**
 sudo docker run hello-world
 ```
 
-Upon success, you should see a useful hello message in chat with some basic information. If you are facing `Permission Denied` errors, please ensure that you enabled the **Docker Compatibility** option on your web interface and restarted the server as described in the [preparation](#preparation) section.
+Upon success, you should see a useful hello message in chat with some basic information. If you are facing `Permission Denied` errors, please ensure that you enabled the **Docker Compatibility** option on your web interface and restarted the server as described in the preparation section.
 
 ![](https://screensaver01.zap-hosting.com/index.php/s/tzJwpYRYb9Mmryo/preview)
 

diff --git a/docs/dedicated-linux-lamp-stack.md b/docs/dedicated-linux-lamp-stack.md
@@ -152,7 +152,7 @@ With the installation of each LAMP dependency now complete, we will now create a
 
 In this example, we will create a small to-do list website via PHP which will fetch and return to-do entries. This will be stored on a MySQL database table and will be served through Apache.
 
-We will also be using a test domain of `zapdocs.example.com` throughout, since in a real-world scenario you would likely utilise a domain. You **must** setup an `A` type DNS record for the domain which points at the IP Address of your server. If you require help with this, please browse our [Domain Records](domain-records.md#a-records) guide.
+We will also be using a test domain of `zapdocs.example.com` throughout, since in a real-world scenario you would likely utilise a domain. You **must** setup an `A` type DNS record for the domain which points at the IP Address of your server. If you require help with this, please browse our [Domain Records](domain-records.md) guide.
 
 :::note
 You can choose not to use a domain and replace mentions of `[your_domain]` with a regular name. You would then access the website via the IP address. However, do note that when creating the virtual host file later on, you should remove the `ServerName` parameter.
@@ -346,7 +346,7 @@ You should now be able to access the website via the domain (using `http`/port 8
 
 ## Conclusion
 
-Congratulations, you have successfully installed and setup the LAMP stack! As the next step, we **highly recommend** setting up a domain and **SSL certificate** to ensure that data is transmitted securely to your websites. Please view our [Certbot guide](vserver-linux-certbot.md#webroot-plugin) with a focus on the **Apache Plugin** and follow the interactive setup to quickly and easily setup a certificate for your chosen domain.
+Congratulations, you have successfully installed and setup the LAMP stack! As the next step, we **highly recommend** setting up a domain and **SSL certificate** to ensure that data is transmitted securely to your websites. Please view our [Certbot guide](vserver-linux-certbot.md) with a focus on the **Apache Plugin** and follow the interactive setup to quickly and easily setup a certificate for your chosen domain.
 
 For further questions or assistance, please don't hesitate to contact our support team, which is available daily to assist you! 🙂
 

diff --git a/docs/dedicated-linux-lemp-stack.md b/docs/dedicated-linux-lemp-stack.md
@@ -142,7 +142,7 @@ With the installation of each LEMP dependency now complete, we will now create a
 
 In this example, we will create a small to-do list website via PHP which will fetch and return to-do entries. This will be stored on a MySQL database table and will be served through Nginx.
 
-We will also be using a test domain of `zapdocs.example.com` throughout, since in a real-world scenario you would likely utilise a domain. You **must** setup an `A` type DNS record for the domain which points at the IP Address of your server. If you require help with this, please browse our [Domain Records](domain-records.md#a-records) guide.
+We will also be using a test domain of `zapdocs.example.com` throughout, since in a real-world scenario you would likely utilise a domain. You **must** setup an `A` type DNS record for the domain which points at the IP Address of your server. If you require help with this, please browse our [Domain Records](domain-records.md) guide.
 
 :::note
 You can choose not to use a domain and replace mentions of `[your_domain]` with a regular name. You would then access the website via the IP address. However, do note that when creating the server block file later on, you should remove the `server_name` parameter.
@@ -356,7 +356,7 @@ You should now be able to access the website via the domain (using `http`/port 8
 
 ## Conclusion
 
-Congratulations, you have successfully installed and setup the LEMP stack! As the next step, we **highly recommend** setting up a domain and **SSL certificate** to ensure that data is transmitted securely to your websites. Please view our [Certbot guide](vserver-linux-certbot.md#webroot-plugin) with a focus on the **Nginx Plugin** and follow the interactive setup to quickly and easily setup a certificate for your chosen domain.
+Congratulations, you have successfully installed and setup the LEMP stack! As the next step, we **highly recommend** setting up a domain and **SSL certificate** to ensure that data is transmitted securely to your websites. Please view our [Certbot guide](vserver-linux-certbot.md) with a focus on the **Nginx Plugin** and follow the interactive setup to quickly and easily setup a certificate for your chosen domain.
 
 For further questions or assistance, please don't hesitate to contact our support team, which is available daily to assist you! 🙂
 

diff --git a/docs/dedicated-linux-wordpress.md b/docs/dedicated-linux-wordpress.md
@@ -229,7 +229,7 @@ And just like that, upon successful login you will now be on your WordPress pane
 
 ## Conclusion
 
-Congratulations, you have successfully installed and configured WordPress! As the next step, we **highly recommend** setting up a domain and **SSL certificate** to ensure that data is transmitted securely and make the WordPress panel easier to access. Please view our [Certbot guide](dedicated-linux-certbot.md#webroot-plugin) with a focus on the **Apache Plugin** and follow the interactive setup to quickly and easily setup a certificate for your chosen domain.
+Congratulations, you have successfully installed and configured WordPress! As the next step, we **highly recommend** setting up a domain and **SSL certificate** to ensure that data is transmitted securely and make the WordPress panel easier to access. Please view our [Certbot guide](dedicated-linux-certbot.md) with a focus on the **Apache Plugin** and follow the interactive setup to quickly and easily setup a certificate for your chosen domain.
 
 For future reading and further setup, we highly recommend having a browse through our [WordPress Plugins](webspace-wordpress-plugins.md) and [WordPress Elementor](webspace-wordpress-elementor.md) guides which explore the process of installing plugins and using a popular user-friendly page builder named Elementor.
 

diff --git a/docs/dedicated-windows-fs-25.md b/docs/dedicated-windows-fs-25.md
@@ -32,7 +32,7 @@ You cannot use the same license key as the one you are playing the game on, ther
 :::info Steam Game License
 It is possible to use a Steam game license to host your dedicated server, however this can be very inconvenient as it would mean that you are forced to run the Steam client at all times in the background. This will also mean that you cannot play any other game on any other system using the same Steam account due to the limitations of Steam. Therefore, we highly recommend you purchase a standalone key directly on the website instead to avoid this hassle.
 
-However, if you do plan to use a **Steam** license, you should instead install the files through Steam as usual and skip to the [**Dedicated Server Setup**](#dedicated-server-setup) section of the guide.
+However, if you do plan to use a **Steam** license, you should instead install the files through Steam as usual and skip to the **Dedicated Server Setup** section of the guide.
 :::
 
 Once you have purchased a digital version from the website, you will receive a product code via the email address that you provided during checkout. You will need this license key in the following section to access the game download and also to validate your dedicated server during setup.

diff --git a/docs/dedicated-windows-javascript.md b/docs/dedicated-windows-javascript.md
@@ -70,7 +70,7 @@ Once finished, you can simply press `Finish` on the final page and start using N
 
 ### Update Node.js to latest version
 
-Running `node -v` will show you the installed version of Node.js. From time to time, you should check that you're running the latest LTS version. To update Node.js, you need to follow the provided [Install JavaScript](dedicated-windows-javascript.md#installing-nodejs-runtime) guide section again.
+Running `node -v` will show you the installed version of Node.js. From time to time, you should check that you're running the latest LTS version. To update Node.js, you need to follow the provided [Install JavaScript](dedicated-windows-javascript.md) guide section again.
 
 ### Running Node.js & npm
 

diff --git a/docs/gameserver-gameswitch.md b/docs/gameserver-gameswitch.md
@@ -46,7 +46,7 @@ In order to install a new game to your game server, select the **Available Games
 
 ![](https://screensaver01.zap-hosting.com/index.php/s/iN7rNje3zaBPMgf/preview)
 
-Under this section, you can also find the **More Games** drop down menu. Across our wide game selection, certain games may have differing slot prices, which can mean that you are unable to install the selected game without additional cost. To resolve this, you will have to pay a surcharge to increase your slot price. See the [Change Slot Price](#change-slot-price) section of the guide for more information.
+Under this section, you can also find the **More Games** drop down menu. Across our wide game selection, certain games may have differing slot prices, which can mean that you are unable to install the selected game without additional cost. To resolve this, you will have to pay a surcharge to increase your slot price. See the Change Slot Price section of the guide for more information.
 
 :::info Minimum Slot Count
 Certain games in our game collection require a specific minimum amount of slots before you can install them to your game server. In such cases, hover over the warning icon to learn more. You should utilise the upgrade/downgrade functionality to upgrade your server based on the information.

diff --git a/docs/minecraft-commands.md b/docs/minecraft-commands.md
@@ -30,7 +30,7 @@ This character is only used to be able to distinguish between a normal chat mess
 
 ### Rights / Permissions
 
-To be able to use commands, the necessary rights are required. In Minecraft-Vanilla or Forge there is no real permission system that can be used by plugins like in Spigot. Here only the level system of the OP-rights can be used. Here you can find a tutorial about the OP-rights system:  [OP Permissions](minecraft-addop.md#rights-level)
+To be able to use commands, the necessary rights are required. In Minecraft-Vanilla or Forge there is no real permission system that can be used by plugins like in Spigot. Here only the level system of the OP-rights can be used. Here you can find a tutorial about the OP-rights system:  [OP Permissions](minecraft-addop.md)
 
 If a permission system has been installed and it is desired to assign rights to certain Minecraft commands, the respective permissions can be assigned as described below.
-Original file line number
+Diff line change
@@ Expand Up @@
     Currently, we accept content using both **Markdown** and **HTML5** styling options.
     :::tip
-    We can **highly recommend** using the Markdown tool **[StackEdit](https://stackedit.io/app#)** to write your content whilst maintaining all the awesome functionality of Markdown. Alternatively, we can also recommend **[HTML5 Editor](https://html5-editor.net/)** if you prefer to style using HTML5. You could then directly export this to your Google Drive or any file-sharing application and receive a link that you can share with us. You can learn more about Markdown styling via our Blog [Guidelines](contribution-blogs-guidelines.md#formatting)guide.
+    We can **highly recommend** using the Markdown tool **[StackEdit](https://stackedit.io/app#)** to write your content whilst maintaining all the awesome functionality of Markdown. Alternatively, we can also recommend **[HTML5 Editor](https://html5-editor.net/)** if you prefer to style using HTML5. You could then directly export this to your Google Drive or any file-sharing application and receive a link that you can share with us. You can learn more about Markdown styling via our Blog [Guidelines](contribution-blogs-guidelines.md)guide.
     :::
     :::note
@@ Expand Down @@