Make most of the links relative

hugo/config.toml

@@ -65,7 +65,7 @@ enableRobotsTXT = true
   # (Optional, default false) Set HTMl <base> to .Site.BaseURL if enabled. It might be required
   # if a subdirectory is used within Hugos BaseURL.
   # See https://developer.mozilla.org/de/docs/Web/HTML/Element/base.
-  geekdocOverwriteHTMLBase = true
+  # geekdocOverwriteHTMLBase = true
 
   # (Optional, default false) Auto-decrease brightness of images and add a slightly grayscale to avoid
   # bright spots while using the dark mode.

hugo/content/docs/_index.md

@@ -2,4 +2,4 @@
 title: "Documentation"
 weight: 0
 ---
-<meta http-equiv="refresh" content="0; url=/docs/introduction/"/>
+<meta http-equiv="refresh" content="0; url=./docs/introduction/"/>

hugo/content/docs/introduction/_index.md

@@ -8,18 +8,18 @@ Langium is an open source language engineering tool with first-class support for
 
 ### Features
 
-If you need a more detailed list of Langium features, you can find them in the [features section](/docs/features).
+If you need a more detailed list of Langium features, you can find them in the [features section](./features).
 
 ### Try it out
 
-If you want to see Langium in action, you can follow the [showcases](/showcase) or even the [playground](/playground).
+If you want to see Langium in action, you can follow the [showcases](../../showcase) or even the [playground](../../playground).
 
 ### Learn Langium
 
-If you are convinced by Langium and want to learn more about it, you can start with the [learn section](/docs/learn).
+If you are convinced by Langium and want to learn more about it, you can start with the [learn section](../learn).
 
 ### More details
 
-If you are looking for more details about Langium, you can find them in the [reference section](/docs/reference).
+If you are looking for more details about Langium, you can find them in the [reference section](../reference).
 
-If you are searching for a certain guide or recipe, you can find them in the [recipes section](/docs/recipes).
+If you are searching for a certain guide or recipe, you can find them in the [recipes section](../recipes).

hugo/content/docs/introduction/features.md

@@ -1,7 +1,8 @@
 ---
 title: "Features"
 weight: 200
-url: /docs/features
+aliases:
+    - /docs/features
 ---
 Designing programming languages from the ground up is hard, independent of whether your language is a "simple" domain specific language or a full-fledged general-purpose programming language.
 Not only do you have to keep up with the requirements of your domain experts, but you have to deal with all the technical complexity that comes with building a language, including questions such as:
@@ -14,20 +15,20 @@ This is the point where Langium comes into play. Langium aims to lower the barri
 
 In this chapter, you'll get a closer look at the requirements developers usually have to implement by themselves when building a programming language:
 
-- [Language Parsing](#language-parsing)
-- [Semantic Models](#semantic-models)
-- [Cross References and Linking](#cross-references-and-linking)
-- [Workspace Management](#workspace-management)
-- [Editing Support](#editing-support)
-- [Try it out](#try-it-out)
+- [Language Parsing](/docs/introduction/features#language-parsing)
+- [Semantic Models](/docs/introduction/features#semantic-models)
+- [Cross References and Linking](/docs/introduction/features#cross-references-and-linking)
+- [Workspace Management](/docs/introduction/features#workspace-management)
+- [Editing Support](/docs/introduction/features#editing-support)
+- [Try it out](/docs/introduction/features#try-it-out)
 
 Langium provides out-of-the-box solutions for these problems, with the ability to fine-tune every part of it to fit your domain requirements.
 
 ---
 
 ## Language Parsing
 
-Programming languages and domain specific languages (DSLs) cannot be parsed using simple regular expressions (RegExp). Instead they require a more sophisticated parsing strategy. To define a custom language in Langium, you interact with a high level representation of your context-free grammar using the [Langium grammar language](/docs/reference/grammar-language), in a similar fashion to EBNF.
+Programming languages and domain specific languages (DSLs) cannot be parsed using simple regular expressions (RegExp). Instead they require a more sophisticated parsing strategy. To define a custom language in Langium, you interact with a high level representation of your context-free grammar using the [Langium grammar language](../reference/grammar-language), in a similar fashion to EBNF.
 
 Based on the grammar, Langium is then able to construct a parser which transforms an input string into a semantic model representation. Just as the name suggests, this model captures the essential structure to describe your language.
 
@@ -101,4 +102,4 @@ The LSP includes commonly used language features, such as code completion, custo
 
 You can try out most of these features using our [showcase](/showcase/) and [playground](/playground/). The languages shown there are written using Langium and integrated in the monaco-editor.
 
-If you're interested in Langium, you can check out our [learning](/docs/learn/workflow) page next. There you'll learn how to get started writing your first language, and to learn more about how Langium can help you achieve your language designing goals.
+If you're interested in Langium, you can check out our [learning](../learn/workflow) page next. There you'll learn how to get started writing your first language, and to learn more about how Langium can help you achieve your language designing goals.

hugo/content/docs/introduction/playground.md

@@ -2,4 +2,4 @@
 title: "Try it out!"
 weight: 400
 ---
-<meta http-equiv="refresh" content="0; url=/playground"/>
+<meta http-equiv="refresh" content="0; url=../playground"/>

hugo/content/docs/learn/_index.md

@@ -1,6 +1,5 @@
 ---
 title: "Learn Langium"
 weight: 0
-url: /docs/learn
 ---
 <meta http-equiv="refresh" content="0; url=/docs/learn/workflow/"/>

hugo/content/docs/learn/minilogo/_index.md

@@ -19,4 +19,4 @@ By working through each of these tutorials, you'll be learning about:
 
 By the end of this series, you should be equipped to start working on your own language, and also have a pretty good idea for how you can integrate Langium into other projects as well.
 
-With that being said, hop on in to the first guide on [Writing a Grammar in Langium](/docs/learn/minilogo/writing_a_grammar)!
+With that being said, hop on in to the first guide on [Writing a Grammar in Langium](./writing_a_grammar)!

hugo/content/docs/learn/minilogo/building_an_extension/_index.md

@@ -7,11 +7,11 @@ aliases:
 
 {{< toc format=html >}}
 
-In this tutorial we'll be going over how to build a VSIX extension (VSCode extension) for your Langium-based language. This will allow providing LSP support in VSCode for your language. We'll assume that you've already looked at the previous tutorial, and have had time to read the [guide on bundling](/docs/recipes/code-bundling), so that you're ready to build an extension. At this point we assume that your language is also working, and there are no issues running `npm run langium:generate` or `npm run build`. If there are, you'll want to correct those first.
+In this tutorial we'll be going over how to build a VSIX extension (VSCode extension) for your Langium-based language. This will allow providing LSP support in VSCode for your language. We'll assume that you've already looked at the previous tutorial, and have had time to read the [guide on bundling](../../../recipes/code-bundling), so that you're ready to build an extension. At this point we assume that your language is also working, and there are no issues running `npm run langium:generate` or `npm run build`. If there are, you'll want to correct those first.
 
 ## Setting up the Scripts
 
-To get started, you'll want to have a language expressed in Langium, such as [Lox](https://github.com/langium/langium-lox) or [MiniLogo](https://github.com/langium/langium-minilogo). If you have been following along with these tutorials, you should already have something ready. If you don't you can also use the default language generated by the yeoman generator for Langium, presented in the [workflow](/docs/learn/workflow/) section.
+To get started, you'll want to have a language expressed in Langium, such as [Lox](https://github.com/langium/langium-lox) or [MiniLogo](https://github.com/langium/langium-minilogo). If you have been following along with these tutorials, you should already have something ready. If you don't you can also use the default language generated by the yeoman generator for Langium, presented in the [workflow](../../workflow/) section.
 
 Regardless of what you're working with, you'll want to make sure you have the following scripts in your **package.json**.
 
@@ -89,4 +89,4 @@ And that's it, at this point you have an extension for your language that you ca
 
 As a quick aside, it's important to keep the extensions that your language recognizes synchronized in both your **package.json** and your **langium-config.json**. If you do make changes to your extensions, it's a good idea to double check that these are both synced up, and to do a full rebuild to get those changes into your extension.
 
-And that's it for building an extension. In the next tutorial, we'll be setting up [Langium + Monaco in the web](/docs/learn/minilogo/langium_and_monaco/).
+And that's it for building an extension. In the next tutorial, we'll be setting up [Langium + Monaco in the web](../langium_and_monaco/).

hugo/content/docs/learn/minilogo/customizing_cli.md

@@ -7,7 +7,7 @@ aliases:
 
 {{< toc format=html >}}
 
-In this tutorial, we'll be talking about customizing the command line interface for your language. We recommend reading through previous tutorials about [writing a grammar](/docs/learn/minilogo/writing_a_grammar) and [validation](/docs/learn/minilogo/validation). Once you have a good grasp on those concepts, then you should be all set for setting up a CLI. We will also continue to use the [MiniLogo](https://github.com/langium/langium-minilogo) language as a motivating example.
+In this tutorial, we'll be talking about customizing the command line interface for your language. We recommend reading through previous tutorials about [writing a grammar](./writing_a_grammar) and [validation](./validation). Once you have a good grasp on those concepts, then you should be all set for setting up a CLI. We will also continue to use the [MiniLogo](https://github.com/langium/langium-minilogo) language as a motivating example.
 
 ## Overview
 
@@ -17,7 +17,7 @@ Once you have a grammar and some validation in place, you may want to start conf
 
 If you've been using a language built with the yeoman generator for Langium, you should be able to find your CLI defined in **src/cli/index.ts**. This file describes the general layout of your languages's command line interface, and lets you register specific commands. By default, you're provided with a single command for your CLI, the **generate** command.
 
-Much like the command implies, it allows you to take a program written in your DSL, parse it, and traverse the AST to produce some sort of generated output. We won't talk about the generator itself in this tutorial (that will come in the [next tutorial on generation](/docs/learn/minilogo/generation)). Instead we'll focus on a simple example for parsing and validating a program, which allows learning more about the CLI itself.
+Much like the command implies, it allows you to take a program written in your DSL, parse it, and traverse the AST to produce some sort of generated output. We won't talk about the generator itself in this tutorial (that will come in the [next tutorial on generation](./generation)). Instead we'll focus on a simple example for parsing and validating a program, which allows learning more about the CLI itself.
 
 ## Adding a Parse and Validate Action
 
@@ -150,4 +150,4 @@ Running the CLI again should show that this program has an error, and better yet
 
 This is perfect, as we didn't have to implement too much more logic to get validation in our CLI. Since we already hooked up our validation service before, the CLI just handles the interaction with an external program. This separation of concerns makes for a very flexible implementation that is easy to adapt over time.
 
-That sums up how to add basic CLI functionality. [In the next tutorial, we will be talking about generation in more detail](/docs/learn/minilogo/generation), specifically about techniques that you can use to traverse your AST and produce a generated output.
+That sums up how to add basic CLI functionality. [In the next tutorial, we will be talking about generation in more detail](./generation), specifically about techniques that you can use to traverse your AST and produce a generated output.

hugo/content/docs/learn/minilogo/generation.md

@@ -7,7 +7,7 @@ aliases:
 
 {{< toc format=html >}}
 
-In this tutorial we'll be showing how to implement basic generation for your language. When we're talking about generation, we're talking about transforming an AST from your Langium-based language into some output target. This could be another language of similar functionality (transpilation), a lower level language (compilation), or generating some artifacts/data that will be consumed by another application. If you haven't already, make sure to go back over and check out the [tutorial on customizing your CLI](/docs/learn/minilogo/customizing_cli), as it touches on details about how to implement endpoints for your application (like generation).
+In this tutorial we'll be showing how to implement basic generation for your language. When we're talking about generation, we're talking about transforming an AST from your Langium-based language into some output target. This could be another language of similar functionality (transpilation), a lower level language (compilation), or generating some artifacts/data that will be consumed by another application. If you haven't already, make sure to go back over and check out the [tutorial on customizing your CLI](./customizing_cli), as it touches on details about how to implement endpoints for your application (like generation).
 
 Per usual, we'll be using the MiniLogo language as a motivating example here.
 
@@ -377,4 +377,4 @@ If you're looking at the implementation of [MiniLogo that we've already written
 
 We could continue to extend on this with new features, and generate new sorts of output using a given input language. In this tutorial, we're able to take a MiniLogo program and convert it into some simple JSON drawing instructions that can be consumed by another program. This opens the door for us to write such a program in another language, such as Python or Javascript, and draw with these results. In later tutorials, we'll be talking about how to run Langium in the web with generation, so that we can immediately verify our results by drawing on an HTML5 canvas.
 
-We recommend that you next read [the guide on bundling your language with Langium to reduce its size](/docs/recipes/code-bundling), before moving onto the tutorial about [bundling an extension](/docs/learn/minilogo/building_an_extension). This is an important step before deployment as an extension for VSCode, and also if you're planning to later deploy your language in the web.
+We recommend that you next read [the guide on bundling your language with Langium to reduce its size](../../recipes/code-bundling), before moving onto the tutorial about [bundling an extension](./building_an_extension). This is an important step before deployment as an extension for VSCode, and also if you're planning to later deploy your language in the web.

hugo/content/docs/learn/minilogo/generation_in_the_web.md

@@ -83,15 +83,15 @@ shared.workspace.DocumentBuilder.onBuildPhase(DocumentState.Validated, documents
 
 And that's it for setting up the onBuildPhase listener itself. We still need to address the usage of `generateMiniLogoCmds`, which is tied to the LS implementation.
 
-Based on the work done in previous tutorials, we already have set up a working generator with MinLogo. If you haven't already set this up you can go back to the [tutorial on generation](/docs/learn/minilogo/generation) and give it a look over. Ideally, we'll already have setup our `generateStatements` function for MiniLogo, meaning so long as the imported module doesn't have any modules that are browser incompatible, we should be able to use it as is. Based on the previous setup however, we should have a **generator.js** file that is free of such conflicts, as much of them should be separated into the cli directly.
+Based on the work done in previous tutorials, we already have set up a working generator with MinLogo. If you haven't already set this up you can go back to the [tutorial on generation](./generation) and give it a look over. Ideally, we'll already have setup our `generateStatements` function for MiniLogo, meaning so long as the imported module doesn't have any modules that are browser incompatible, we should be able to use it as is. Based on the previous setup however, we should have a **generator.js** file that is free of such conflicts, as much of them should be separated into the cli directly.
 
 This saves us quite a bit of time, since we don't need to handle setting up & dispatching a document for validation, we simply tap into the existing workflow and collect the result when it's ready. This is a great example of how Langium's architecture allows us to easily extend existing functionality, and add new features without having to rewrite existing code.
 
 As a concluding note for this section, don't forget to rebuild your language server bundle! It might not be a bad idea to clean as well, just to be sure everything is working as expected at this step.
 
 ## Listening for Notifications in the Client
 
-The next step we need to make is to actually listen for these notifications from the client's end. This takes us back to the [Langium + Monaco](/docs/learn/minilogo/langium_and_monaco) setup in the previous tutorial.
+The next step we need to make is to actually listen for these notifications from the client's end. This takes us back to the [Langium + Monaco](./langium_and_monaco) setup in the previous tutorial.
 
 After starting the wrapper successfully, we want to retrieve the MonacoLanguageClient instance (a wrapper around the language client itself) and listen for `browser/DocumentChange` notifications.
 

hugo/content/docs/learn/minilogo/langium_and_monaco.md

@@ -618,4 +618,4 @@ npm run serve
 
 You should be greeted with a page that contains a working Monaco instance and a small MiniLogo program in the editor. This editor has the highlighting we would expect, and also is fully connected to the language server for our language. This means we have full LSP support for operations that we would expect to have in a native IDE, such as VSCode.
 
-And that's it, we have successfully implemented Langium + Monaco in the web for our language. It's not doing much at this time besides presenting us with an editor, but in the next tutorial we'll talk about [using the same setup to add generation in the web](/docs/learn/minilogo/generation_in_the_web). Since our generation has already been configured natively in prior tutorials, we can use what we've written to quickly implement a web application that translates MiniLogo programs into drawing instructions for an HTML5 canvas.
+And that's it, we have successfully implemented Langium + Monaco in the web for our language. It's not doing much at this time besides presenting us with an editor, but in the next tutorial we'll talk about [using the same setup to add generation in the web](./generation_in_the_web). Since our generation has already been configured natively in prior tutorials, we can use what we've written to quickly implement a web application that translates MiniLogo programs into drawing instructions for an HTML5 canvas.