scaleway · bene2k1 · Oct 23, 2025 · Oct 23, 2025 · Oct 23, 2025
diff --git a/macros/console/create-account.mdx b/macros/console/create-account.mdx
@@ -4,7 +4,7 @@ macro: create-account
 1. Click **Sign Up** in the upper right corner of the page. You are redirected to the account creation page.
 2. Select an account type (Corporate, Startup, Consultant/Freelancer, or Personal project).
 3. Select a sign-up method, and follow the corresponding steps below.
-    <Tabs id="create-account">
+    <Tabs>
       <TabsTab label="Sign-up with SSO">
         1. Select the service you want to use (Google, Microsoft, or Github). Make sure the associated email address is the one you want to use for your Scaleway account.
         2. Check the box to agree to Scaleway's [Terms and Services](https://www.scaleway.com/en/contracts/), and Scaleway's [Data Protection Agreement](https://www.scaleway.com/en/contracts/).

@@ -14,7 +14,7 @@ macro: login-member
     </Message>
 4. Enter the username given to you by your Organization's Owner or administrator.
 5. Select an authentication method between **Send code** and **Enter password**.
-    <Tabs id="create-account">
+    <Tabs>
       <TabsTab label="Email code">
       1. Click **Send code** to receive a login code in your email.
       2. Enter the code you received in your email.

@@ -29,7 +29,7 @@ This page describes the different log in methods available, and what to consider
 ## How to log in as an Organization Owner
 
 1. Open your web browser and go to the [Scaleway console](https://console.scaleway.com).
-    <Tabs id="create-account">
+    <Tabs>
       <TabsTab label="Log in with SSO">
       1. Click the **Google** or the **GitHub** logo, depending on the account you want to use.
       2. Log in through the respective Google or GitHub login pages.
@@ -71,7 +71,7 @@ If you were added to a Scaleway Organization as an [IAM Member](/iam/concepts#me
     </Message>
 4. Enter the username given to you by your Organization's Owner or administrator.
 5. Select an authentication method between **Log in with SSO**, **Send code** and **Enter password**.
-    <Tabs id="create-account">
+    <Tabs>
       <TabsTab label="Log in with SSO">
       Scaleway provides Single Sign-On (SSO) options for a seamless login experience. By default, you can use your Google or Github account to log in to the console. To do so, make sure the email address associated with your Scaleway account matches the email address of your Google or Github account.
 
@@ -115,7 +115,7 @@ You can authenticate using either a:
 
 If the login information provided in any of the previous methods is valid, you will be redirected the Multifactor Authentication screen. If both MFA methods are enabled in your account, you will see the **passkey** screen by default.
 
-<Tabs id="mfa-login">
+<Tabs>
   <TabsTab label="Log in with a passkey">
   1. Click **Use passkey**. Your password manager pops-up.
   2. Follow the steps in your password manager.

@@ -56,7 +56,7 @@ Data source managed alert rules allow you to configure alerts managed by the dat
 
 Switch between the tabs below to create alerts for a Scaleway Instance, an Object Storage bucket, a Kubernetes cluster Pod, or Cockpit logs.
 
-<Tabs id="install">
+<Tabs>
   <TabsTab label="Scaleway Instance">
     The steps below explain how to create the metric selection and configure an alert condition that triggers when **your Instance consumes more than 10% of a single CPU core over the past 5 minutes.**
 

diff --git a/pages/contribute.mdx b/pages/contribute.mdx
@@ -21,7 +21,7 @@ Join the Scaleway **Write for the Community** program, an initiative for making
 
 ## Become a contributor
 
-<Tabs id="become-contributor">
+<Tabs>
 
   <TabsTab label="Before you start    ">
 

diff --git a/pages/data-warehouse/how-to/connect-applications.mdx b/pages/data-warehouse/how-to/connect-applications.mdx
@@ -37,7 +37,7 @@ To connect your deployment with BI tools, refer to the [dedicated documentation]
 
     Select the appropriate protocol, then run the displayed command in a terminal. Remember to replace the placeholders with the appropriate values, and to specify the correct path to the certificate file.
 
-        <Tabs id="data-warehouse-connect-protocols">
+        <Tabs>
             <TabsTab label="ClicHouse® CLI">
             ```bash
             clickhouse client \
@@ -73,7 +73,7 @@ To connect your deployment with BI tools, refer to the [dedicated documentation]
 
       Select the desired language, then run the code displayed to create a file that connects to your deployment, and run queries programmatically. Remember to replace the placeholders with the appropriate values, and to specify the correct path to the certificate file.
 
-        <Tabs id="data-warehouse-connect-languages">
+        <Tabs>
             <TabsTab label="Python">
             ```python
             pip install clickhouse-connect

diff --git a/pages/data-warehouse/how-to/connect-bi-tools.mdx b/pages/data-warehouse/how-to/connect-bi-tools.mdx
@@ -114,7 +114,7 @@ Your user can now access the specified database using the credentials you just d
 
 ### Connecting PowerBI to your deployment
 
-<Tabs id="power-bi-connection">
+<Tabs>
 <TabsTab label="PowerBI Desktop">
 1. Make sure you have installed [PowerBI Desktop](https://www.microsoft.com/en-us/download/details.aspx?id=58494/), and [MySQL Connector/NET](https://dev.mysql.com/downloads/connector/net/).
 

diff --git a/pages/data-warehouse/how-to/import-data.mdx b/pages/data-warehouse/how-to/import-data.mdx
@@ -53,7 +53,7 @@ You can connect to your deployment using the ClickHouse® HTTP console directly
 
 There are several ways to import data into your Data Warehouse for ClickHouse® deployment, depending on how your data is stored. One of the most common ways is to import it from an Object Storage bucket in any format supported by ClickHouse®.
 
-<Tabs id="import-data-into-data-warehouse">
+<Tabs>
 <TabsTab label="s3 table function">
 The `s3` table function reads data directly from an Object Storage bucket by specifying the URL of the bucket, the file format, and the data structure.
 ```sql

diff --git a/pages/data-warehouse/how-to/manage-storage.mdx b/pages/data-warehouse/how-to/manage-storage.mdx
@@ -38,7 +38,7 @@ The table below provides an overview of each storage policy's behavior and use c
 
 [Connect to you deployment](/data-warehouse/how-to/connect-applications/), then run the SQL query below to apply the `tiered` storage policy.
 
-<Tabs id="tiered-explicit-implicit">
+<Tabs>
   <TabsTab label="Explicit">
 
   Storage policy is explicitly defined as `tiered`.

@@ -236,7 +236,7 @@ ssacli ctrl all show config
   For more information on Smartmontools, refer to the [official documentation](https://www.smartmontools.org/wiki/TocDoc).
 </Message>
 
-<Tabs id="Smart data examples">
+<Tabs>
   <TabsTab label="HDD example">
    The example below shows SMART data for the HDD storage type:
 

@@ -43,7 +43,7 @@ The procedure for adding a customized endpoint is as follows:
 
 4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below.
 
-    <Tabs id="edge-cname">
+    <Tabs>
 
         <TabsTab label="Domains and DNS">
         The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if:

@@ -59,7 +59,7 @@ You can create [pipelines](/edge-services/concepts/#pipeline) for either Object
 
     Follow the steps below depending on whether you are creating a Load Balancer or Object Storage pipeline.<br/>
 
-    <Tabs id="edge-services-quickstart">
+    <Tabs>
       <TabsTab label="Load Balancer">
 
         <Lightbox image={image2} alt="A screenshot of the Scaleway console shows the Edge Services pipeline creation wizard. It prompts you to select an origin type (Load Balancer or Object Storage), and configure the other options described below on this page." />
@@ -134,7 +134,7 @@ If you already own a domain, you can customize an Edge Services pipeline endpoin
 
 4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below.
 
-    <Tabs id="edge-cname">
+    <Tabs>
 
         <TabsTab label="Domains and DNS">
         The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if:

@@ -12,7 +12,7 @@ In general, codes in the 2xx range indicate success, codes in the 4xx range indi
 
 If the response code is not within the 2xx range, the response will contain an error object. The structure of the error object depends on how recent the model being used is:
 
-<Tabs id="error-message">
+<Tabs>
 
   <TabsTab label="Recent models">
     Recent models, such as Mistral Small 3.2, GPT-OSS 120b and Qwen3 235b, use the following error format:

@@ -72,7 +72,7 @@ client = OpenAI(
 
 You can now create a chat completion using either the Chat Completions or Responses API, as shown in the following examples:
 
-<Tabs id="generating-chat-completion">
+<Tabs>
 
     <TabsTab label="Chat Completions API">
 
@@ -135,7 +135,7 @@ Adding such a system prompt can also help resolve issues if you receive response
 
 The following parameters will influence the output of the model:
 
-<Tabs id="model-params">
+<Tabs>
 
   <TabsTab label = "Chat Completions API">
 
@@ -197,7 +197,7 @@ for chunk in response:
 
 The service also supports asynchronous mode for any chat completion.
 
-<Tabs id="async">
+<Tabs>
 
   <TabsTab label="Chat Completions API">
 

@@ -87,7 +87,7 @@ client = OpenAI(
 
 You can now create a chat completion with reasoning, using either the Chat Completions or Responses API, as shown in the following examples:
 
-<Tabs id="generating-chat-completion">
+<Tabs>
 
     <TabsTab label="Chat Completions API">
 

@@ -98,7 +98,7 @@ We using the base code below to send our LLM a voice note transcript to structur
 
 Using [Pydantic](https://docs.pydantic.dev/latest/concepts/models/), users can define the schema as a Python class and enforce the model to return results adhering to this schema.
 
-<Tabs id="structured-output_pydantic">
+<Tabs>
     <TabsTab label="Chat Completions API">
 
     ```python

diff --git a/pages/guidelines.mdx b/pages/guidelines.mdx
@@ -255,7 +255,7 @@ Use a console icon when referring in the documentation to the equivalent icon in
 | ------------------------------------------------------------------- | ---------------------------------------------------------- |
 | ````Use the toggle <Icon name="toggle" /> to activate the feature````  | Use the toggle <Icon name="toggle" /> to activate the feature |
 
-See the [full list of available icons](https://docs-sb-storybook-staging.s3-website.fr-par.scw.cloud/?path=/docs/mdx-icon--docs).
+See the [full list of available icons](https://storybook-docs.scaleway.com/?path=/docs/mdx-icon--docs).
 
 ### Messages
 
@@ -267,7 +267,7 @@ Three types of message boxes are available, to use as follows:
 | Tip          | Information about a different way to accomplish something, or how to go further | ````<Message type="tip"> </Message>```` | <Message type="tip"> This is a tip </Message> |
 | Important    | Critical warnings and information that the user must read to avoid unwanted consequences or mistakes | ````<Message type="important"> </Message>```` | <Message type="important"> This is important </Message> |
 
-Read more about [message box components](https://docs-sb-storybook-staging.s3-website.fr-par.scw.cloud/?path=/docs/mdx-message--docs).
+Read more about [message box components](https://storybook-docs.scaleway.com/?path=/docs/mdx-message--docs).
 
 ### Tabs
 
@@ -282,7 +282,7 @@ See an example of the tabs component in action on the [How to connect to an Inst
 Tabs syntax:
 
 ```
-<Tabs id="example-tabs">
+<Tabs>
 
   <TabsTab label="Tab one">
     This is the content of tab one
@@ -301,7 +301,7 @@ Tabs syntax:
 
 Renders as:
 
-<Tabs id="example-tabs">
+<Tabs>
   <TabsTab label="Tab one">
     This is the content of tab one
   </TabsTab>
@@ -313,7 +313,7 @@ Renders as:
   </TabsTab>
 </Tabs>
 
-Read more about the [tab component](https://docs-sb-storybook-staging.s3-website.fr-par.scw.cloud/?path=/docs/mdx-tabs--docs).
+Read more about the [tab component](https://storybook-docs.scaleway.com/?path=/docs/mdx-tabs--docs).
 
 ## Grammar, syntax and typography
 
@@ -438,7 +438,7 @@ A wording handbook is available internally, with a full list of correct product
 
 ### Lightbox component
 
-Use the [Lightbox component](https://docs-sb-storybook-staging.s3-website.fr-par.scw.cloud/?path=/docs/mdx-lightbox--docs) for images, with the following syntax:
+Use the [Lightbox component](https://storybook-docs.scaleway.com/?path=/docs/mdx-lightbox--docs) for images, with the following syntax:
 
 ````
 import myImage from "./assets/myImage.webp"
@@ -482,7 +482,7 @@ categories:
 ```
 
 - **title**: The title of the page, used by external search engines and the main title that displays on the documentation page.
-- **description**: The description, used by external search engines. It should be between 120 and 160 characters, and SEO-optimized, using clear, engaging language suitable for a wide audience. Also displays on some documentation pages (e.g. when the page is linked to from a [product card](https://docs-sb-storybook-staging.s3-website.fr-par.scw.cloud/?path=/docs/mdx-card--docs)).
+- **description**: The description, used by external search engines. It should be between 120 and 160 characters, and SEO-optimized, using clear, engaging language suitable for a wide audience. Also displays on some documentation pages (e.g. when the page is linked to from a [product card](https://storybook-docs.scaleway.com/?path=/docs/mdx-card--docs)).
 - **tags**: The tags used by internal and external search engines to help users find the page
 - **dates: posted**: The date the page was originally created, in the format `yyyy-mm-dd`. This displays on the generated page.
 - **dates: validation**: The date the page was last validated, in the format `yyyy-mm-dd`. This displays on the generated page, and is used by the Documentation team when identifying documentation pages that need reviewing.

@@ -13,7 +13,7 @@ import image from './assets/scaleway-iam-users-dashboard.webp'
 
 You can view the permission sets granted to API keys (via policies) through the Scaleway console, [the API](https://www.scaleway.com/en/developers/api/iam/#path-permission-sets-list-permission-sets), and the Scaleway CLI.
 
-<Tabs id="viewpermissionsets">
+<Tabs>
   <TabsTab label="Via the console">
     <Requirements />
     - A Scaleway account logged into the [console](https://console.scaleway.com)

@@ -20,7 +20,7 @@ The Backup feature is used to back up your Instance data. It creates an image of
 
 ## Creating a backup
 
-<Tabs id="createbackup">
+<Tabs>
 
   <TabsTab label="CLI">
     Use the following commands to create a backup of your Instance using the [Scaleway CLI](/scaleway-cli/quickstart/).
@@ -69,7 +69,7 @@ The Backup feature is used to back up your Instance data. It creates an image of
 </Tabs>
 
 ## Deleting a Backup
-<Tabs id="deletebackup">
+<Tabs>
 
   <TabsTab label="CLI">
     To delete a backup, run the following command:

@@ -30,7 +30,7 @@ To do so, you need the Instance’s ID and a valid API key.
   Do **not** manually change the commercial type of **Kubernetes Kapsule nodes** using the API or CLI. Kubernetes Kapsule nodes **must be managed** through Kubernetes. Modifying node types outside of the recommended method can lead to instability or unexpected behavior.
   To change the commercial type of your nodes, create a new node pool with the desired Instance type and [migrate your workloads](/kubernetes/how-to/manage-node-pools/#how-to-migrate-existing-workloads-to-a-new-kubernets-kapsule-node-pool) to the new pool.
 </Message>
-<Tabs id="updateinstance">
+<Tabs>
   <TabsTab label="CLI">
 
     1. Stop the Instance.

@@ -91,7 +91,7 @@ In this section, we will guide you through the process of creating a new Instanc
 
 You can request routed IPs using the Scaleway API. Available IP types are IPv4 and IPv6.
 
-<Tabs id="create-ip">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ cat payloads/ip-data.json
@@ -135,7 +135,7 @@ You can request routed IPs using the Scaleway API. Available IP types are IPv4 a
 
 Run the following command to create an Instance with the previously created IP address.
 
-<Tabs id="create-instance">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ cat payloads/server-data.json
@@ -281,7 +281,7 @@ Run the following command to create an Instance with the previously created IP a
 
 First you need to create an IPv4 reservation, then create a new Instance with this public IP attached.
 
-<Tabs id="create-ipv4">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ cat payloads/ip-data.json
@@ -316,7 +316,7 @@ First you need to create an IPv4 reservation, then create a new Instance with th
 
 And now we create the Instance.
 
-<Tabs id="create-instancev4">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ cat payloads/server-data.json
@@ -469,7 +469,7 @@ Then you can create a new Instance using those IPs through the `public_ips` fiel
     Not to be confused with the `public_ip` field that only accepts *one* IP.
 </Message>
 
-<Tabs id="multiple-ips">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ cat payloads/server-data.json
@@ -638,7 +638,7 @@ Then you can create a new Instance using those IPs through the `public_ips` fiel
 
 You can use a specific server action to move an existing (legacy network) Instance to routed IPs.
 
-<Tabs id="move-instance">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ http post $API_URL/servers/$SERVER_ID/action $HEADERS action=enable_routed_ip
@@ -668,7 +668,7 @@ You can use a specific server action to move an existing (legacy network) Instan
 
 You can verify if your IP is a routed IP or a NAT IP through the `/ips` endpoint:
 
-<Tabs id="verify-ip">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ http $API_URL/ips/201f52df-3c83-4eeb-aff4-038bb15f918d $HEADERS
@@ -723,7 +723,7 @@ You can verify if your IP is a routed IP or a NAT IP through the `/ips` endpoint
 
 You can verify if your Instance is enabled for routed IPs through the `/servers` endpoint:
 
-<Tabs id="create">
+<Tabs>
     <TabsTab label="Request">
         ```json
         ❯ http $API_URL/servers/9515993f-f596-4b51-84e8-9e48f2d49eb8 $HEADERS

@@ -23,7 +23,7 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the
 - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
 - An [Instance](/instances/how-to/create-an-instance/)
 
-<Tabs id="connectinstance">
+<Tabs>
 
   <TabsTab label="Linux Instances">
 

@@ -13,7 +13,7 @@ This page shows how to create your first Scaleway Instance. An [Instance](/insta
 
 Select a tab below for instructions on how to create an Instance via either our [console](https://console.scaleway.com), our [API](https://www.scaleway.com/en/developers/api/instances/), or our [CLI](https://github.com/scaleway/scaleway-cli).
 
-<Tabs id="createinstance">
+<Tabs>
 
   <TabsTab label="Console - Linux">
 

@@ -58,7 +58,7 @@ Use this table to help identify the right Instance range for your use case and c
 
 Refer to the tabs below to compare the different Instance ranges and learn more about their key use cases:
 
-<Tabs id="comparison">
+<Tabs>
   <TabsTab label="Development Instances">
     Scaleway Development Instances are highly reliable and affordably priced, making them an ideal choice for businesses looking to balance operational flexibility, cost-efficiency, and performance.
     Designed for lightweight applications, development environments, and low-intensity workloads, these Instances offer a budget-friendly cloud solution.
-Original file line number
+Diff line change
@@ Expand Up @@
     ## Become a contributor
-    <Tabs id="become-contributor">
+    <Tabs>
       <TabsTab label="Before you start    ">
@@ Expand Down @@