Feat/node 22

.github/workflows/build.yml

@@ -16,7 +16,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v3
         with:
-          node-version: 20
+          node-version: 22
       - name: Cache dependencies
         uses: actions/cache@v3
         with:

.github/workflows/build_and_deploy.yml

@@ -22,7 +22,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v3
         with:
-          node-version: 20
+          node-version: 22
 
       - name: Cache dependencies
         uses: actions/cache@v3

.github/workflows/build_and_staging.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v3
         with:
-          node-version: 20
+          node-version: 22
 
       - name: Cache dependencies
         uses: actions/cache@v3

.nvmrc

@@ -1 +1 @@
-v18
+v22

blog/2026-01-22-introducing-docs-blog.md

@@ -17,7 +17,7 @@ it was somewhat hard to distill the various aspects and goals of SCS though.
 With the end of the funded project, we split the activities into different organizations
 with distinct goals:
 
-1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/network/) is
+1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/) is
    responsible for governing the standardization process. While it pulls significant input
    from the various software projects that belong to the SCS ecosystem, it is neutral towards
    them beyond the preference for standards compliance. This reflects that there can and
@@ -41,8 +41,8 @@ it assembles documentation from various places. Unlike the Forum, it does not ne
 to prioritize neutrality as top priority, but benefits and prefers those projects
 that contribute useful content to it.
 
-We have decided to use docusaurus' blog feature to publish blog articles
-[here](https://docs.scs.community/blog/). We appreciate contributions.
+We have decided to use docusaurus' blog feature to publish
+[blog articles](https://docs.scs.community/blog/). We appreciate contributions.
 
 ## Old blog content
 

community/cloud-resources/cloud-resources.md

@@ -34,7 +34,7 @@ Once the PR has been accepted, [configure your VPN access by following the steps
 
 ### SCS Hardware Landscape Usage
 
-More information on how to use the Hardware Landscape can be found [here](hardware-landscape.md).
+Here is [more information on how to use the Hardware Landscape](hardware-landscape.md).
 
 ## SCS2 @ plusserver
 
@@ -44,7 +44,7 @@ To apply for a new project, please create a pull request against this document (
 
 ### SCS2 Usage
 
-A brief guide on how to use the resources provided by plusserver GmbH can be found [here](plusserver-gx-scs.md).
+Here is a [brief guide on how to use the resources provided by plusserver GmbH](plusserver-gx-scs.md).
 
 ### SCS2 Users
 
@@ -101,7 +101,7 @@ To apply for a new project, please create a pull request against this document (
 
 ### Wavestack Usage
 
-A brief guide on how to use the resources provided by Wavecon GmbH can be found [here](wavestack.md).
+Here is [a brief guide on how to use the resources provided by Wavecon GmbH](wavestack.md).
 
 ### Wavestack Service Users
 

community/contribute/adding-docs-guide.md

@@ -10,7 +10,7 @@ Determine the type of your documentation and click to continue.
 2. [Operational documentation](#2-operational-documentation)
 3. [Community documentation](#3-community-documentation)
 
-If unsure don't hestitate to ask us at [Matrix](https://github.com/SovereignCloudStack/docs/blob/main/community/communication/matrix.md)
+If unsure don't hestitate to ask us at [Matrix](https://docs.scs.community/community/tools/matrix)
 
 ## 1. Technical Documentation
 
@@ -53,7 +53,7 @@ File a Pull Request within the [docs](https://github.com/SovereignCloudStack/doc
 
 Once it is approved and merged, a postinstall script will be triggered within the build process. This initiates downloading, copy and distilling which results in this static generated [documentation](https://docs.scs.community) page – now with your content.
 
-An explanation on how the sync & distill workflow and a guide on how to test it in a local development environment you will find [here](https://github.com/SovereignCloudStack/docs/blob/main/community/contribute/docs-workflow-explanation.md).
+Here is an explanation on how the [sync & distill workflow works and a guide on how to test it in a local development environment](https://github.com/SovereignCloudStack/docs/blob/main/community/contribute/docs-workflow-explanation.md).
 
 ## 2. Operational documentation
 
@@ -68,6 +68,6 @@ File a Pull Request within the [docs](https://github.com/SovereignCloudStack/doc
 
 ## 3. Community documentation
 
-Your doc files contain knowledge regarding our community? Choose the right directory. If unsure don't hestitate to ask us at [Matrix](https://github.com/SovereignCloudStack/docs/blob/main/community/communication/matrix.md).
+Your doc files contain knowledge regarding our community? Choose the right directory. If unsure don't hestitate to ask us at [Matrix](https://docs.scs.community/community/tools/matrix).
 
 File a Pull Request within the `docs` repository and add your markdown files to the fitting directory.

community/contribute/styleguides/ansible_styleguide.md

@@ -15,7 +15,7 @@ disable the package_latest rule.
 
 ## Key Order
 
-To check the key order we use our own rule. This can be found [here](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/files).
+To check the key order we use our [own rule](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/).
 
 ### Positioning and use of the become directive
 

community/tools/zuul.md

@@ -8,16 +8,18 @@ use Zuul as our main pipeline solution.
 
 ### How to make a repo use Zuul
 
-- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul_deployment)
+Note: This needs to be updated!
+
+- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul-scs-jobs)
 - Create a file _.zuul.yaml_
-  - An example can be found [here](https://github.com/SovereignCloudStack/zuul-sandbox/blob/main/.zuul.yaml)
+  - Here is [an example](https://github.com/SovereignCloudStack/zuul-config/)
   - You can have a job section containing _self-defined_ jobs which you need to write on your own
   - You have to have a project section containing
     - the default-branch name
     - the merge-mode which should be used to auto-merge
     - the jobs to run in each pipeline (gh_check, gh_gate, gh_post, gh_tag)
-    - these pipelines are triggered by events which can be looked up [here](https://github.com/SovereignCloudStack/zuul_config/blob/main/zuul.d/gh_pipelines.yaml)
-    - some default jobs can be found [here](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks)
+    - these [pipelines](https://github.com/SovereignCloudStack/zuul-config/blob/main/zuul.d/) are triggered by events
+    - ihere are [some default jobs](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks)
 - If you have _self-defined_ jobs, you need to create a folder _.playbooks_
   - this folder containers ansible playbooks which will be triggered