docs(blk): reuse concepts from Instances doc MTA-6210 (#5174)

SamyOubouaziz · jcirinosclwy · web-flow · commit e365b225ff2b · 2025-06-24T16:06:43.000+02:00
* docs(blk): reuse concepts from Instances doc MTA-6210

* docs(blk): fix missing tuto index

* docs(blk): fix missing tuto index

* docs(blk): make more macros

* docs(blk): fix

* Update macros/concepts/availability-zone.mdx

Co-authored-by: Jessica &lt;113192637+jcirinosclwy@users.noreply.github.com&gt;

* Apply suggestions from code review

Co-authored-by: Jessica &lt;113192637+jcirinosclwy@users.noreply.github.com&gt;

---------

Co-authored-by: Jessica &lt;113192637+jcirinosclwy@users.noreply.github.com&gt;
diff --git a/macros/concepts/availability-zone.mdx b/macros/concepts/availability-zone.mdx
@@ -0,0 +1,7 @@
+---
+macro: availability-zone
+---
+
+An Availability Zone refers to an isolated location within a specific region. Each Availability Zone provides its own services and infrastructure. For example, `fr-par-1`, `fr-par-2`, and `fr-par-3` are Availability Zones within the Paris region.
+
+For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/).
diff --git a/macros/concepts/block-snapshot.mdx b/macros/concepts/block-snapshot.mdx
@@ -0,0 +1,5 @@
+---
+macro: block-snapshot
+---
+
+A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/block-storage/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance.
diff --git a/macros/concepts/block-volumes.mdx b/macros/concepts/block-volumes.mdx
@@ -0,0 +1,5 @@
+---
+macro: block-volumes
+---
+
+Block volumes provide network-attached storage you can plug in/out of Instances like a virtual hard drive. From a user's point of view, block volumes behave like regular disks and can be used to increase the storage of an Instance.
diff --git a/macros/concepts/local-volumes.mdx b/macros/concepts/local-volumes.mdx
@@ -0,0 +1,5 @@
+---
+macro: local-volumes
+---
+
+The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block). In any case, it is always possible to increase the storage of an Instance by adding extra block volumes.
diff --git a/macros/concepts/region.mdx b/macros/concepts/region.mdx
@@ -0,0 +1,7 @@
+---
+macro: region
+---
+
+A region is a geographical area such as France (Paris: fr-par), the Netherlands (Amsterdam: nl-ams), or Poland (Warsaw: pl-waw) in which Scaleway products and resources are located. Each region contains multiple Availability Zones.
+
+For an extensive list of which regions and AZs a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/).
diff --git a/macros/concepts/volumes.mdx b/macros/concepts/volumes.mdx
@@ -0,0 +1,9 @@
+---
+macro: volumes
+---
+
+Volumes are the storage space of your Instances. Two types of volumes exist:
+
+* **[Local volumes](/local-storage/)**: The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](/instances/concepts/#boot-on-block).
+
+* **[Block volumes](/block-storage/)**: Block volumes provide network-attached storage you can plug in and out of Instances like a virtual hard drive. Block volumes behave like regular disks and can be used to increase the storage of an Instance.
diff --git a/pages/block-storage/concepts.mdx b/pages/block-storage/concepts.mdx
@@ -14,9 +14,17 @@ categories:
   - storage
 ---
 
-## Block device
+## Availability Zone
 
-A block device is a storage volume on a network-connected storage system that is exposed to the guest operating system as if it were a physical disk.
+<Macro id="availability-zone" />
+
+## Block volumes
+
+<Macro id="block-volumes" />
+
+## Boot-on-block
+
+<Macro id="storage-boot-on-block" />
 
 ## IOPS
 
@@ -29,7 +37,15 @@ Scaleway Block Storage Low Latency offers two IOPS limits:
 
 ## Local volume
 
-The local volume of an Instance is an all SSD-based storage solution, using a RAID array for redundancy and performance, that is hosted on the local hypervisor.
+<Macro id="local-volumes" />
+
+## Region
+
+<Macro id="region" />
+
+## Snapshot
+
+<Macro id="block-snapshot" />
 
 ## Storage Area Networks (SANs)
 
diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx
@@ -14,13 +14,11 @@ categories:
 
 ## Availability Zone
 
-An Availability Zone refers to an isolated location within a specific region. Each Availability Zone provides its own services and infrastructure. For example, `fr-par-1`, `fr-par-2`, and `fr-par-3` are Availability Zones within the Paris region.
-
-For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/)
+<Macro id="availability-zone" />
 
 ## Block volumes
 
-Block volumes provide network-attached storage you can plug in/out of Instances like a virtual hard drive. From a user's point of view, block volumes behave like regular disks and can be used to increase the storage of an Instance.
+<Macro id="block-volumes" />
 
 ## Boot-on-block
 
@@ -88,7 +86,7 @@ With IP mobility, there are no NAT IPs anymore. The public IP is entirely routed
 
 ## Local volumes
 
-The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block). In any case, it is always possible to increase the storage of an Instance by adding additional block volumes.
+<Macro id="local-volumes" />
 
 ## Placement groups
 
@@ -128,9 +126,7 @@ Public IP addresses are routed on the internet. You can enter the public IP addr
 
 ## Region
 
-A region is a geographical area such as France (Paris: fr-par), the Netherlands (Amsterdam: nl-ams), or Poland (Warsaw: pl-waw) in which Scaleway products and resources are located. Each region contains multiple Availability Zones.
-
-For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/)
+<Macro id="region" />
 
 ## Rescue mode
 
@@ -154,7 +150,7 @@ Security groups allow you to [create rules to drop or allow public traffic comin
 
 ## Snapshot
 
-A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/block-storage/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance.
+<Macro id="block-snapshot" />
 
 ## Snapshot type
 
@@ -178,8 +174,4 @@ Tags allow you to organize, sort, filter, and monitor your cloud resources using
 
 ## Volumes
 
-Volumes are the storage space of your Instances. Two types of volumes exist:
-
-* **[Local volumes](/local-storage/)**: The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block).
-
-* **[Block volumes*](/block-storage/)**: Block volumes provide network-attached storage you can plug in and out of Instances like a virtual hard drive. Block volumes behave like regular disks and can be used to increase the storage of an Instance.
+<Macro id="volumes" />
diff --git a/pages/local-storage/concepts.mdx b/pages/local-storage/concepts.mdx
@@ -14,15 +14,15 @@ categories:
 
 ## Block volumes
 
-Block volumes provide network-attached storage you can plug in and out of Instances like a virtual hard drive. From a user's point of view, block volumes behave like regular disks and can be used to increase the storage of an Instance.
+<Macro id="block-volumes" />
 
-## Boot-on-Block
+## Boot-on-block
 
-Some Instance types do not use local volumes and instead boot directly on block volumes.
+<Macro id="storage-boot-on-block" />
 
 ## Local volumes
 
-The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block). In any case, it is always possible to increase the storage of an Instance by adding additional block volumes.
+<Macro id="local-volumes" />
 
 ## Power-off mode
 
@@ -34,7 +34,4 @@ Standby mode is a way to stop an Instance temporarily. When you put an Instance
 
 ## Volumes
 
-Volumes are the storage space of your Instances. Two types of volumes exist:
-
-- **[Local volumes](/local-storage/)**: The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block).
-- **[Block volumes](/block-storage/)**: Block volumes provide network-attached storage you can plug in and out of Instances like a virtual hard drive. Block volumes behave like regular disks and can be used to increase the storage of an Instance.
+<Macro id="volumes" />

-Original file line number
+Diff line change
@@ @@ -0,0 +1,5 @@ @@
 +---
 +macro: block-snapshot
 +---
++
 +A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/block-storage/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance.