Convert the remaining Serveex and recycled articles to steps

content/en/3.serveex/8.development/1.code-server.md

@@ -38,6 +38,9 @@ tree:
 ---
 ::
 
+::steps{level="3"}
+### Deploy the stack
+
 Open Dockge, click on `compose`, name the stack `code-server`, and paste the following:
 
 ```yaml [compose.yaml]
@@ -73,6 +76,8 @@ services:
     ```
 ::
 
+### Set your environment variables
+
 Choose a password and generate its hash:
 
 ```bash [Terminal]
@@ -100,6 +105,9 @@ __Note:__ Make sure to wrap the hash in single quotes `'`
 
 Deploy the container and go to `http://yourserverip:8443`. Voilà, your code-server instance is up and running in the browser!
 
+### Done !
+::
+
 ::caution
 
 __If it fails:__ check your firewall rules.
@@ -126,6 +134,9 @@ The whole point of such a solution is to access it remotely from any device. To
 __Preliminary:__ We assume you’ve created a subdomain like `code.yourdomain.com` with a `CNAME` pointing to `yourdomain.com` in your [DNS zone](/general/networking/dns). Unless you're using [Cloudflare Zero Trust](/serveex/security/cloudflare), we also assume you’ve forwarded port `443` from your router to port `443` on your server using [NAT rules](/general/networking/nat).
 ::
 
+::steps{level="3"}
+### Add code-server's network to SWAG
+
 In Dockge, go to the SWAG stack and edit the compose file to add code-server’s network:
 
 ```yaml [compose.yaml]
@@ -152,6 +163,8 @@ We assume the network name is `code-server_default`. You can verify that the con
 
 Redeploy the stack by clicking “deploy” and wait until SWAG is fully operational.
 
+### Create the subdomain.conf file
+
 Inside the Swag config folders, create the file `code.subdomain.conf`.
 
 ::tip{icon=""}
@@ -216,6 +229,9 @@ server {
 
 Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
 
+### Done !
+::
+
 That’s it! code-server is now exposed!
 
 ## Protecting code-server with TinyAuth