Fix mobile overflow and broken images; host Hidora logo locally

assets/scss/_oss_health.scss

@@ -176,6 +176,20 @@
       color: #fff;
     }
   }
+
+  // Three 7rem buttons don't fit on phones and push the page sideways.
+  @include media-breakpoint-down(lg) {
+    display: flex;
+    max-width: 100%;
+    width: 100%;
+
+    &__button {
+      flex: 1 1 0;
+      min-width: 0;
+      padding-left: 0.5rem;
+      padding-right: 0.5rem;
+    }
+  }
 }
 
 .oss-health-grid {

assets/scss/_page.scss

@@ -86,3 +86,9 @@
     }
   }
 }
+
+// Long URLs and inline-code links in docs and blog posts must wrap,
+// otherwise they overflow the viewport on mobile.
+.td-content a {
+  overflow-wrap: anywhere;
+}

assets/scss/blocks/_hero.scss

@@ -3,8 +3,10 @@
 @include td-box-height-modifiers(".td-hero-block");
 
 .hero-gitops {
-  margin-left: -15px;
-  margin-right: -15px;
+  // Match Bootstrap 5 gutter (0.75rem). The old -15px was the Bootstrap 4 value
+  // and made the page 3px wider than the viewport (horizontal scroll).
+  margin-left: -0.75rem;
+  margin-right: -0.75rem;
 
   @include media-breakpoint-down(md) {
     padding: 0 15px;

content/de/support.md

@@ -4,7 +4,7 @@ date: 2025-03-02T15:45:07+04:00
 draft: false
 type: "page"
 weight: 50
-source_digest: "sha256:2cacdfc9855cebb5b4df0c21de9b889985cba9754a72581f10f1cd5ea6a0c286"
+source_digest: "sha256:de998fb26d73dc851cf18a0437e5f7d1397e551876c7d8742e14f7816ae57ac8"
 translation_status: current
 l10n: mt
 ---
@@ -13,4 +13,4 @@ l10n: mt
 | Organisation | Kontakt | Leistungsbeschreibung |
 | ------------ | ------- | ------------------ |
 | <img src="/img/logos/aenix.png" alt="Aenix logo" width="200"/> | [Website](https://aenix.io/contact/) [LinkedIn](https://www.linkedin.com/company/aenix-io)| Wir bieten jede Art von Unterstützung: Beratung, Entwicklung fehlender Funktionen, Design sowie Hilfe bei Installation und Integration. |
-| <img src="https://hikube.cloud/hs-fs/hubfs/image%20-%202025-07-23T133743.819.png" alt="Hidora" width="200"/>  | [Website](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| Wir übernehmen die Installation, bieten laufenden Support und Managed Services rund um die Uhr (24/7). |
+| <img src="/img/logos/hidora.svg" alt="Hidora" width="200"/>  | [Website](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| Wir übernehmen die Installation, bieten laufenden Support und Managed Services rund um die Uhr (24/7). |

content/en/blog/2025-12-17-talm-v0-17-built-in-age-encryption-for-secrets.md

@@ -4,8 +4,6 @@ slug: talm-v0-17-built-in-age-encryption-for-secrets
 date: 2025-12-17
 author: "Andrei Kvapil (Ænix)"
 description: "Talm v0.17 introduces built-in age encryption for secure secrets management, making it easier to store sensitive configuration files in Git repositories while maintaining security best practices."
-images:
-  - "https://cdn-images-1.medium.com/max/800/0*encryption.png"
 article_types:
   - release
 topics:
@@ -18,8 +16,6 @@ topics:
 
 The latest release of [Talm](https://github.com/cozystack/talm), the configuration manager for Talos Linux, introduces a powerful new feature: built-in encryption using the [age](https://age-encryption.org/) encryption tool. This enhancement allows you to securely store sensitive configuration files like `secrets.yaml`, `talosconfig`, and `kubeconfig` in Git repositories while following security best practices.
 
-![](https://cdn-images-1.medium.com/max/800/0*encryption.png)
-
 ### Why Age Encryption?
 
 Managing secrets in Git repositories has always been a challenge. While storing configuration files in version control is convenient for GitOps workflows, sensitive data like API keys, certificates, and cluster credentials should never be committed in plain text. Traditional solutions like `git-crypt` or external secret management systems add complexity and dependencies.

content/en/docs/next/operations/oidc/identity_providers/google.md

@@ -10,19 +10,19 @@ aliases:
 ## Configure Google
 
 - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project.
-![1](/img/oidc/identity_providers/google/1.jpeg)
+![1](/img/OIDC/identity_providers/google/1.jpeg)
 
 - Click on "New Project" to proceed.
-![2](/img/oidc/identity_providers/google/2.jpeg)
+![2](/img/OIDC/identity_providers/google/2.jpeg)
 
 - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create"
-![3](/img/oidc/identity_providers/google/3.jpeg)
+![3](/img/OIDC/identity_providers/google/3.jpeg)
 
 - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step.
-![4](/img/oidc/identity_providers/google/4.jpeg)
+![4](/img/OIDC/identity_providers/google/4.jpeg)
 
 - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create".
-![5](/img/oidc/identity_providers/google/5.jpeg)
+![5](/img/OIDC/identity_providers/google/5.jpeg)
 
 - After this, we will be redirected to pages where we will have to configure different things
     - Application type: Public
@@ -32,16 +32,16 @@ aliases:
     - Application Privacy Policy link: Your application privacy policy link
 
 - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID".
-![6](/img/oidc/identity_providers/google/6.jpeg)
+![6](/img/OIDC/identity_providers/google/6.jpeg)
 
 - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this
 ```bash
 https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint
 ```
-![7](/img/oidc/identity_providers/google/7.jpeg)
+![7](/img/OIDC/identity_providers/google/7.jpeg)
 
 - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it.
-![8](/img/oidc/identity_providers/google/8.jpeg)
+![8](/img/OIDC/identity_providers/google/8.jpeg)
 
 ## Configure Keycloak Identity Provider
 Create a `KeycloakRealmIdentityProvider` resource with the following configuration:

content/en/docs/v0/operations/oidc/identity_providers/google.md

@@ -12,19 +12,19 @@ aliases:
 ## Configure Google
 
 - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project.
-![1](/img/oidc/identity_providers/google/1.jpeg)
+![1](/img/OIDC/identity_providers/google/1.jpeg)
 
 - Click on "New Project" to proceed.
-![2](/img/oidc/identity_providers/google/2.jpeg)
+![2](/img/OIDC/identity_providers/google/2.jpeg)
 
 - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create"
-![3](/img/oidc/identity_providers/google/3.jpeg)
+![3](/img/OIDC/identity_providers/google/3.jpeg)
 
 - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step.
-![4](/img/oidc/identity_providers/google/4.jpeg)
+![4](/img/OIDC/identity_providers/google/4.jpeg)
 
 - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create".
-![5](/img/oidc/identity_providers/google/5.jpeg)
+![5](/img/OIDC/identity_providers/google/5.jpeg)
 
 - After this, we will be redirected to pages where we will have to configure different things
     - Application type: Public
@@ -34,16 +34,16 @@ aliases:
     - Application Privacy Policy link: Your application privacy policy link
 
 - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID".
-![6](/img/oidc/identity_providers/google/6.jpeg)
+![6](/img/OIDC/identity_providers/google/6.jpeg)
 
 - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this
 ```bash
 https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint
 ```
-![7](/img/oidc/identity_providers/google/7.jpeg)
+![7](/img/OIDC/identity_providers/google/7.jpeg)
 
 - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it.
-![8](/img/oidc/identity_providers/google/8.jpeg)
+![8](/img/OIDC/identity_providers/google/8.jpeg)
 
 ## Configure Keycloak Identity Provider
 Create a `KeycloakRealmIdentityProvider` resource with the following configuration:

content/en/docs/v1.0/operations/oidc/identity_providers/google.md

@@ -10,19 +10,19 @@ aliases:
 ## Configure Google
 
 - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project.
-![1](/img/oidc/identity_providers/google/1.jpeg)
+![1](/img/OIDC/identity_providers/google/1.jpeg)
 
 - Click on "New Project" to proceed.
-![2](/img/oidc/identity_providers/google/2.jpeg)
+![2](/img/OIDC/identity_providers/google/2.jpeg)
 
 - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create"
-![3](/img/oidc/identity_providers/google/3.jpeg)
+![3](/img/OIDC/identity_providers/google/3.jpeg)
 
 - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step.
-![4](/img/oidc/identity_providers/google/4.jpeg)
+![4](/img/OIDC/identity_providers/google/4.jpeg)
 
 - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create".
-![5](/img/oidc/identity_providers/google/5.jpeg)
+![5](/img/OIDC/identity_providers/google/5.jpeg)
 
 - After this, we will be redirected to pages where we will have to configure different things
     - Application type: Public
@@ -32,16 +32,16 @@ aliases:
     - Application Privacy Policy link: Your application privacy policy link
 
 - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID".
-![6](/img/oidc/identity_providers/google/6.jpeg)
+![6](/img/OIDC/identity_providers/google/6.jpeg)
 
 - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this
 ```bash
 https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint
 ```
-![7](/img/oidc/identity_providers/google/7.jpeg)
+![7](/img/OIDC/identity_providers/google/7.jpeg)
 
 - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it.
-![8](/img/oidc/identity_providers/google/8.jpeg)
+![8](/img/OIDC/identity_providers/google/8.jpeg)
 
 ## Configure Keycloak Identity Provider
 Create a `KeycloakRealmIdentityProvider` resource with the following configuration:

content/en/docs/v1.1/operations/oidc/identity_providers/google.md

@@ -10,19 +10,19 @@ aliases:
 ## Configure Google
 
 - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project.
-![1](/img/oidc/identity_providers/google/1.jpeg)
+![1](/img/OIDC/identity_providers/google/1.jpeg)
 
 - Click on "New Project" to proceed.
-![2](/img/oidc/identity_providers/google/2.jpeg)
+![2](/img/OIDC/identity_providers/google/2.jpeg)
 
 - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create"
-![3](/img/oidc/identity_providers/google/3.jpeg)
+![3](/img/OIDC/identity_providers/google/3.jpeg)
 
 - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step.
-![4](/img/oidc/identity_providers/google/4.jpeg)
+![4](/img/OIDC/identity_providers/google/4.jpeg)
 
 - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create".
-![5](/img/oidc/identity_providers/google/5.jpeg)
+![5](/img/OIDC/identity_providers/google/5.jpeg)
 
 - After this, we will be redirected to pages where we will have to configure different things
     - Application type: Public
@@ -32,16 +32,16 @@ aliases:
     - Application Privacy Policy link: Your application privacy policy link
 
 - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID".
-![6](/img/oidc/identity_providers/google/6.jpeg)
+![6](/img/OIDC/identity_providers/google/6.jpeg)
 
 - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this
 ```bash
 https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint
 ```
-![7](/img/oidc/identity_providers/google/7.jpeg)
+![7](/img/OIDC/identity_providers/google/7.jpeg)
 
 - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it.
-![8](/img/oidc/identity_providers/google/8.jpeg)
+![8](/img/OIDC/identity_providers/google/8.jpeg)
 
 ## Configure Keycloak Identity Provider
 Create a `KeycloakRealmIdentityProvider` resource with the following configuration:

content/en/docs/v1.2/operations/oidc/identity_providers/google.md

@@ -10,19 +10,19 @@ aliases:
 ## Configure Google
 
 - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project.
-![1](/img/oidc/identity_providers/google/1.jpeg)
+![1](/img/OIDC/identity_providers/google/1.jpeg)
 
 - Click on "New Project" to proceed.
-![2](/img/oidc/identity_providers/google/2.jpeg)
+![2](/img/OIDC/identity_providers/google/2.jpeg)
 
 - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create"
-![3](/img/oidc/identity_providers/google/3.jpeg)
+![3](/img/OIDC/identity_providers/google/3.jpeg)
 
 - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step.
-![4](/img/oidc/identity_providers/google/4.jpeg)
+![4](/img/OIDC/identity_providers/google/4.jpeg)
 
 - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create".
-![5](/img/oidc/identity_providers/google/5.jpeg)
+![5](/img/OIDC/identity_providers/google/5.jpeg)
 
 - After this, we will be redirected to pages where we will have to configure different things
     - Application type: Public
@@ -32,16 +32,16 @@ aliases:
     - Application Privacy Policy link: Your application privacy policy link
 
 - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID".
-![6](/img/oidc/identity_providers/google/6.jpeg)
+![6](/img/OIDC/identity_providers/google/6.jpeg)
 
 - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this
 ```bash
 https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint
 ```
-![7](/img/oidc/identity_providers/google/7.jpeg)
+![7](/img/OIDC/identity_providers/google/7.jpeg)
 
 - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it.
-![8](/img/oidc/identity_providers/google/8.jpeg)
+![8](/img/OIDC/identity_providers/google/8.jpeg)
 
 ## Configure Keycloak Identity Provider
 Create a `KeycloakRealmIdentityProvider` resource with the following configuration:

content/en/docs/v1.3/operations/oidc/identity_providers/google.md

@@ -10,19 +10,19 @@ aliases:
 ## Configure Google
 
 - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project.
-![1](/img/oidc/identity_providers/google/1.jpeg)
+![1](/img/OIDC/identity_providers/google/1.jpeg)
 
 - Click on "New Project" to proceed.
-![2](/img/oidc/identity_providers/google/2.jpeg)
+![2](/img/OIDC/identity_providers/google/2.jpeg)
 
 - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create"
-![3](/img/oidc/identity_providers/google/3.jpeg)
+![3](/img/OIDC/identity_providers/google/3.jpeg)
 
 - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step.
-![4](/img/oidc/identity_providers/google/4.jpeg)
+![4](/img/OIDC/identity_providers/google/4.jpeg)
 
 - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create".
-![5](/img/oidc/identity_providers/google/5.jpeg)
+![5](/img/OIDC/identity_providers/google/5.jpeg)
 
 - After this, we will be redirected to pages where we will have to configure different things
     - Application type: Public
@@ -32,16 +32,16 @@ aliases:
     - Application Privacy Policy link: Your application privacy policy link
 
 - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID".
-![6](/img/oidc/identity_providers/google/6.jpeg)
+![6](/img/OIDC/identity_providers/google/6.jpeg)
 
 - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this
 ```bash
 https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint
 ```
-![7](/img/oidc/identity_providers/google/7.jpeg)
+![7](/img/OIDC/identity_providers/google/7.jpeg)
 
 - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it.
-![8](/img/oidc/identity_providers/google/8.jpeg)
+![8](/img/OIDC/identity_providers/google/8.jpeg)
 
 ## Configure Keycloak Identity Provider
 Create a `KeycloakRealmIdentityProvider` resource with the following configuration: