feat(gen): use cases visual (#5491)

Author: ldecarvalho-doc

changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx

@@ -0,0 +1,13 @@
+---
+title: Windows Images - Network configuration now uses DHCP. Serial console enabled
+status: changed
+date: 2025-08-25
+category: compute
+product: instances
+---
+
+Windows Server 2022 and Windows Server 2022 Core images now use DHCP for network configuration by default, consistent with all existing Instance OS images.
+
+For running Instances, no network configuration changes are needed unless you modify the public IPv4 address.
+
+If you change the public IPv4 address, the Instance will retain its existing static configuration and continue using the previous address. To enable DHCP for your Instance, follow our [dedicated documentation](/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022/) before updating the public IPv4 address.

changelog/august2025/2025-08-27-kubernetes-added-dns-service-ip-and-pod-and-service-cid.mdx

@@ -0,0 +1,13 @@
+---
+title: DNS Service IP and Pod & Service CIDR are now customizable
+status: added
+date: 2025-08-27
+category: containers
+product: kubernetes
+---
+
+The following parameters can be set when creating a cluster:
+- `service-dns-ip`: IP used for the DNS Service (cannot be changes later)
+- `pod-cidr`: Subnet used for the Pod CIDR (cannot be changed later)
+- `service-cidr`: Subnet used for the Service CIDR (cannot be changed later)
+

changelog/august2025/2025-08-28-containers-added-custom-domains-now-supports-websockets.mdx

@@ -0,0 +1,10 @@
+---
+title: Custom domains now supports WebSockets
+status: added
+date: 2025-08-28
+category: serverless
+product: containers
+---
+
+Serverless Containers configured with custom domains are now compatible with WebSockets.
+

changelog/august2025/2025-08-28-functions-added-custom-domains-now-supports-websockets.mdx

@@ -0,0 +1,10 @@
+---
+title: Custom domains now support WebSockets
+status: added
+date: 2025-08-28
+category: serverless
+product: functions
+---
+
+Serverless Functions configured with custom domains are now compatible with WebSockets.
+

changelog/august2025/2025-08-29-instances-deprecated-ent1-instances-are-now-deprecated.mdx

@@ -0,0 +1,11 @@
+---
+title: ENT1 Instances are now deprecated
+status: deprecated
+date: 2025-08-29
+category: compute
+product: instances
+---
+
+ENT1 Instances are now deprecated and unavailable for new deployments. Existing ENT1 Instances will soon be automatically migrated to their POP2 equivalent, as announced recently through our emails & ticket communication.
+[POP2 Instances](/instances/reference-content/general-purpose/#pop2-instances), which share the same hardware specifications as ENT1 Instances, provide access to the latest features, ensuring your infrastructure remains current with evolving technology and demands. 
+

changelog/september2025/2025-09-01-key-manager-changed-key-manager-is-now-in-general-avail.mdx

@@ -0,0 +1,10 @@
+---
+title: Key Manager is now in General Availability 
+status: changed
+date: 2025-09-01
+category: security-identity
+product: key-manager
+---
+
+[Key Manager](/key-manager/) is now in General Availability. Secure your production applications and start managing your keys today.
+

macros/ai/chat-comp-vs-responses-api.mdx

@@ -0,0 +1,17 @@
+---
+macro: chat-comp-vs-responses-api
+---
+
+Both the [Chat Completions API](https://www.scaleway.com/en/developers/api/generative-apis/#path-chat-completions-create-a-chat-completion) and the [Responses API](https://www.scaleway.com/en/developers/api/generative-apis/#path-responses-beta-create-a-response) are OpenAI-compatible REST APIs that can be used for generating and manipulating conversations. The Chat Completions API is focused on generating conversational responses, while the Responses API is a more general REST API for chat, structured outputs, tool use, and multimodal inputs.
+
+The **Chat Completions** API was released in 2023, and is an industry standard for building AI applications, being specifically designed for handling multi-turn conversations. It is stateless, but allows users to manage conversation history by appending each new message to the ongoing conversation. Messages in the conversation can include text, images and audio extracts. The API supports `function` tool-calling, allowing developers to define functions that the model can choose to call. If it does so, it returns the function name and arguments, which the developer's code must execute and feed back into the conversation.
+
+The **Responses** API was released in 2025, and is designed to combine the simplicity of Chat Completions with the ability to do more agentic tasks and reasoning. It supports statefulness, being able to maintain context without needing to resend the entire conversation history. It offers tool-calling by built-in tools (e.g. web or file search) that the model is able to execute itself while generating a response. 
+
+<Message type="note">
+Scaleway's support for the Responses API is currently at beta stage. Support of the full feature set will be incremental: currently statefulness and tools other than `function` calling are not supported. 
+</Message>
+
+Most supported Generative API models can be used with both Chat Completions and Responses API. For the **`gtp-oss-120b` model, use of the Responses API is recommended, as it will allow you to access all of its features, especially tool-calling.
+
+For full details on the differences between these APIs, see the [official OpenAI documentation](https://platform.openai.com/docs/guides/migrate-to-responses).

macros/compute/instances-block-bandwidth-overview.mdx

@@ -38,17 +38,6 @@ Bandwidth impacts how your applications perform and interact with other systems.
 | DEV1-L                | 400 Mbit/s          | 200 MiB/s       |
 | DEV1-XL               | 500 Mbit/s          | 250 MiB/s       |
 
-## ENT1 range
-
-|   Instance Type      |   Internet Bandwidth (up to)  |   Block Bandwidth (up to)  |
-|-----------------------|-------------------------|---------------------|
-| ENT1-XXS              | 400 Mbit/s              | 400 MiB/s         |
-| ENT1-XS               | 800 Mbit/s              | 800 MiB/s         |
-| ENT1-S                | 1.6 Gbit/s             | 1.56 GiB/s         |
-| ENT1-M                | 3.2 Gbit/s             | 3.12 GiB/s         |
-| ENT1-L                | 6.4 Gbit/s             | 6.25 GiB/s         |
-| ENT1-XL               | 12.8 Gbit/s            | 12.5 GiB/s         |
-
 ## GP1 range
 
 |   Instance Type      |   Internet Bandwidth (up to)  |   Block Bandwidth (up to)  |

macros/compute/instances.mdx

@@ -2,4 +2,4 @@
 macro: compute-instances
 ---
 
-An Instance is a computing unit, either virtual or physical, that provides resources to run your applications on. Currently Scaleway offers the following Instance types: [General Purpose](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [Development](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [GPU](/instances/concepts/#gpu-instance), [Stardust](/instances/reference-content/learning/#learning-range-stardust-instances) and [Enterprise](/instances/reference-content/production-optimized/#production-optimized-range-ent1-instances).
+An Instance is a computing unit, either virtual or physical, that provides resources to run your applications on. Currently Scaleway offers the following Instance types: [General Purpose](/instances/reference-content/general-purpose/), [Development](/instances/reference-content/development/), [GPU](/instances/concepts/#gpu-instance), and [Specialized](/instances/reference-content/specialized/).

menu/mainLinks.json

@@ -10,6 +10,11 @@
       "label": "Tutorials",
       "slug": "tutorials"
     },
+    {
+      "icon": "UseCaseCategoryIcon",
+      "label": "Use cases",
+      "slug": "use-cases"
+    },
     {
       "icon": "BillingCategoryIcon",
       "label": "Troubleshooting Hub",