@@ -4,7 +4,7 @@ For the development of the extended JaMoPP, we base the workflow on the Gitflow
 
 1. While the `main` branch hosts the source code of all releases with Git tags, all changes are primarily merged into the (default) `develop` branch.
 1. For every bug, feature, release, and other issue, a [GitHub issue](https://github.com/MDSD-Tools/TheExtendedJavaModelParserAndPrinter/issues) needs to be created.
-1. For the resolution of an issue (except releases), there should be a separate feature branch, usually branched from the current `develop` branch, with the name `<issue number>_<meaningful_short_issue_description_with_words_separated_by_underscores>`. Please consider the `CHANGELOG.md` and this documentation, and update them if necessary.
+1. For the resolution of an issue (except releases), there should be a separate feature branch, usually branched from the current `develop` branch, with the name `<issue_number>_<meaningful_short_issue_description_with_words_separated_by_underscores>`. Please consider the `CHANGELOG.md` and this documentation, and update them if necessary.
 1. If the changes are ready for merging, a pull request needs to be created for meging the feature branch into the `develop` branch. It is reviewed by at least one person. After all comments and issues within the pull request are resolved and the pull request is approved, it is merged, closing the pull request and corresponding GitHub issue.
 1. For a release:
    1. The following parts should be adapted on the `develop` branch:
 
@@ -159,7 +159,7 @@ classDiagram
 
 Compared to the first visualization without the `calc` method, the model now includes the method. As a consequence, the parameters, return type (`typeReference` in the actual model), and the statements of the method are also represented with corresponding model elements. In particular, the `AdditiveExpression` for the addition of `a` and `b` contains `IdentifierReference` elements signaling that identifiers are present at this position in the Java code. The actual referenced elements (the method parameters) can be accessed via the `target` EMF reference.
 
-:::caution
+:::warning
 The term `Reference` has a double meaning here:
 
 1. It refers to identifiers (referencing types, fields, methods, ...) in Java code which are usually represented by `Reference` elements in the Java meta-model.
 
@@ -7,7 +7,7 @@ sidebar_label: First Steps
 
 This document provides a minimal tutorial on how to use the extended JaMoPP to create your first models from Java code.
 
-:::caution
+:::warning
 This tutorial assumes that you are familiar with the Eclipse Modeling Framework (EMF). In case you want more information about EMF or Eclipse, we provide a [list of external resources and tutorials](./resources).
 :::
 
@@ -65,7 +65,7 @@ packageElement.getNamespaces().add(packageName);
 cu.getClassifiers().get(0).setPackage(packageElement);
 ```
 
-:::caution
+:::warning
 The created package element must be contained within a `Resource`. For simplicity, we left this part out.
 :::
 
 
@@ -21,7 +21,7 @@ Additionally, there is the following nightly P2 update site which provides artif
 
 * [Nightly P2 Update Site](https://updatesite.mdsd.tools/extended-java-model-parser-and-printer/nightly/)
 
-:::caution
+:::warning
 
 The nightly update site can have different requirements (e.g., on the minimum Java version) compared to the latest release. So, before using it, please check the [`CHANGELOG` on the `develop` branch](https://github.com/MDSD-Tools/TheExtendedJavaModelParserAndPrinter/blob/develop/CHANGELOG.md) for the latest changes.
 
 
@@ -17,6 +17,6 @@ void print(JavaRoot root, Path file);
 
 The first method prints the source code for the given root element into the `OutputStream`. Similarly, the second method prints the source code for an arbitrary model element into an `OutputStream`. At last, the third method prints the source code for a root element into a file, given by a `Path`. The printed source code is not pretty printed.
 
-:::caution
+:::warning
 The printer assumes that the given models are valid.
 :::
@@ -11,7 +11,7 @@ The extended JaMoPP provides three variants to resolve the references between di
 
 Due to technical issues, the first variant is currently not available.
 
-:::caution
+:::warning
 The corresponding class (`JaMoPPJDTParser`) is still included in the artifacts. However, it only returns empty models.
 :::
 
@@ -29,7 +29,7 @@ When using the [`JaMoPPJDTSingleFileParser`](./parsing.md), the second variant i
 
 During parsing, the second variant creates a proxy object for every reference. The generated proxy URI has the format &lt;`Base URI`&gt;`/EMFTEXT_INTERNAL_URI_FRAGMENT_`&lt;`counter`&gt;`_`&lt;`identifier`&gt; where `Base URI` equals the URI of the model in which the proxy object is located, `counter` is the value of a proxy object counter incremented for every proxy object, and `identifier` is the identifier in the Java source code pointing to the actual Java element. In addition, the second variant stores the context of the proxy object independently from the models, including, for instance, the container of the proxy object or the reference for which the proxy object is set.
 
-:::caution
+:::warning
 If Java models with proxy objects are saved on disk, the proxy objects' context is not stored. As a result, if such models are loaded again in a new process, the context is not available, and the proxy objects can potentially be not resolved.
 :::
 
 
@@ -1,8 +1,9 @@
 // @ts-check
 // Note: type annotations allow type checking and IDEs autocompletion
 
-const lightCodeTheme = require('prism-react-renderer/themes/github');
-const darkCodeTheme = require('prism-react-renderer/themes/dracula');
+const { themes } = require('prism-react-renderer');
+const lightCodeTheme = themes.github;
+const darkCodeTheme = themes.dracula;
 
 /** @type {import('@docusaurus/types').Config} */
 const config = {
@@ -14,19 +15,22 @@ const config = {
   url: 'https://mdsd-tools.github.io',
   // Set the /<baseUrl>/ pathname under which your site is served
   // For GitHub pages deployment, it is often '/<projectName>/'
-  baseUrl: '/',
+  baseUrl: '/TheExtendedJavaModelParserAndPrinter/',
 
   // GitHub pages deployment config.
   // If you aren't using GitHub pages, you don't need these.
   organizationName: 'MDSD-Tools', // Usually your GitHub org/user name.
   projectName: 'TheExtendedJavaModelParserAndPrinter', // Usually your repo name.
 
   onBrokenLinks: 'throw',
-  onBrokenMarkdownLinks: 'warn',
 
   markdown: {
-    mermaid: true
+    mermaid: true,
+    hooks: {
+      onBrokenMarkdownLinks: 'warn'
+    }
   },
+  trailingSlash: false,
   themes: ['@docusaurus/theme-mermaid'],
 
   // Even if you don't use internalization, you can use this field to set useful
@@ -92,15 +96,6 @@ const config = {
       footer: {
         style: 'dark',
         links: [
-          {
-            title: 'Docs',
-            items: [
-              {
-                label: 'Documentation',
-                to: '/docs/intro',
-              },
-            ],
-          },
           {
             title: 'More',
             items: [
@@ -115,7 +110,7 @@ const config = {
             ],
           },
         ],
-        copyright: `Copyright © 2023 Modelling for Continuous Software Engineering (MCSE) group, Institute of Information Security and Dependability (KASTEL), Karlsruhe Institute of Technology (KIT).`,
+        copyright: `Copyright © 2023-2025 Modelling for Continuous Software Engineering (MCSE) group, Institute of Information Security and Dependability (KASTEL), Karlsruhe Institute of Technology (KIT).`,
       },
       prism: {
         theme: lightCodeTheme,