Use page bundles for multilingual articles

content/en/post/self-hosting/index.md

@@ -28,7 +28,7 @@ In fact, for many years, one could almost think that for an advertising company,
 But one day, an advertising engineer had an idea: if we could know what kind of person is searching, we would be able to send them directly to the most appropriate site.
 A few developments later, here is what the biggest data vacuum cleaner you can imagine was:
 
-![The GMail interface](/post/self-hosting/gmail.png)
+![The GMail interface](gmail.png)
 
 Contacts, message contents, order forms, newsletters, ... This is how to subtly direct someone to one site rather than another.
 This is very good when we are in a hurry, but instead of opening us up to the world in general, it locks us into an information bubble.

content/en/post/use-additional-ipv6-blocks-from-isp/index.md

@@ -24,7 +24,7 @@ This is possible because the router regularly transmits information about the su
 
 For our experiment, let's take the following lab:
 
-![The basic infrastructure that we will use for our experiments](/post/use-additional-ipv6-blocks-from-isp/lab.png)
+![The basic infrastructure that we will use for our experiments](lab.png)
 
 We have all our equipment connected to the box and a series of virtual machines hosted on one of the network machines.
 
@@ -42,7 +42,7 @@ The main interest of this segmentation would be to avoid that all this little wo
 
 We could therefore want to segment our network like this:
 
-![Example of segmentation by splitting the /64 block into two /65 blocks](/post/use-additional-ipv6-blocks-from-isp/lab-segmente.png)
+![Example of segmentation by splitting the /64 block into two /65 blocks](lab-segmente.png)
 
 We would reserve half of the /64 block for real network equipment and allocate the other half to our virtual machines located on a server/Raspberry Pi.
 

content/en/post/use-ipv6-in-docker/index.md

@@ -15,7 +15,7 @@ In fact, for the same reason we saw in [the introductory article]({{< relref "us
 
 The same phenomenon can be observed with IPv4: each container has an IPv4 in a subnet separate from the one in which our host machine is located.
 
-![Illustration of a classic IPv4 home network](/post/use-ipv6-in-docker/common-network-with-docker.png)
+![Illustration of a classic IPv4 home network](common-network-with-docker.png)
 
 In order for the containers to have access to the Internet under these conditions, in IPv4 NAT is implemented:
 
@@ -72,7 +72,7 @@ On the Freebox, the window for setting additional prefixes is in "Paramètres de
 
 It looks like this:
 
-![Freebox IPv6 prefix delegation settings window](/post/use-ipv6-in-docker/freebox-ipv6-refix-delegation.png)
+![Freebox IPv6 prefix delegation settings window](freebox-ipv6-refix-delegation.png)
 
 Always leave the first field empty, otherwise the box will not offer you IPv6 on the main network.
 
@@ -85,7 +85,7 @@ That's all! The hardest part is over. Now let's see the Docker configuration.
 
 We will not use the range to which our machine is connected. We are going to use a whole /64 range, the one for which we have given the local IP of our machine to the box.
 
-![Our prefix delegation correctly set up on the Freebox](/post/use-ipv6-in-docker/freebox-ipv6-delegation-filled.png)
+![Our prefix delegation correctly set up on the Freebox](freebox-ipv6-delegation-filled.png)
 
 According to the previous screenshot, our configuration file `/etc/docker/daemon.json` should look like: