Convert the remaining Serveex and recycled articles to steps

content/en/6.recycled/1.deprecated/1.wireguard-14.md

@@ -1,18 +1,10 @@
 ---
 title: Wireguard 14
+description: Archived guide to installing WireGuard VPN using linuxserver.io's older wireguard image, kept for reference only.
 ---
 
 
 :ellipsis{left=0px width=40rem top=10rem blur=140px zIndex=60}
-# Wireguard
-
-::note
-🎯 __Goals:__
-
-  - Install Wireguard
-  - Configure clients
-  - Access the secure network
-::
 
 ## Introduction
 Using a VPN allows remote access to a server’s local resources without exposing them to the internet. It’s a clean and secure way to access services like SSH without exposing the port publicly. With a VPN, you can securely connect to your network from anywhere and make devices on different networks communicate.
@@ -74,6 +66,9 @@ tree:
 
 The container runs in `HOST` mode, meaning it uses the host’s network stack directly.
 
+::steps{level="3"}
+### Deploy the stack
+
 Open Dockge, click `compose`, and name the stack `wg_easy`.
 
 Paste the following configuration:
@@ -139,6 +134,9 @@ IPS=
 
 Deploy the stack.
 
+### Done !
+::
+
 ### Enable Forwarding on Host
 
 To allow communication between VPN clients, enable:
@@ -180,6 +178,9 @@ tree:
 ---
 ::
 
+::steps{level="3"}
+### Create the config folder
+
 Create the folder `/docker/wireguard/config/wg_confs`:
 
 ::tip{icon=""}
@@ -190,6 +191,8 @@ Create the folder `/docker/wireguard/config/wg_confs`:
 sudo mkdir -p /docker/wireguard/config/wg_confs
 ```
 
+### Copy the configuration file
+
 Copy the `wg0.conf` file downloaded earlier:
 
 ::tip{icon=""}
@@ -200,6 +203,8 @@ sudo cp ~/wg0.conf /docker/wireguard/config/wg_confs
 ```
 ::
 
+### Deploy the container
+
 Create `compose.yaml` in `/docker/wireguard`:
 
 ```bash [Terminal]
@@ -240,6 +245,9 @@ sudo docker compose up -d
 Repeat for each client
 ::
 
+### Done !
+::
+
 ## Other Devices
 
 - **Phone:** Install Wireguard and scan the QR code from the web UI (`http://your-server-ip:51821`)

content/en/6.recycled/1.deprecated/2.file-browser.md

@@ -5,20 +5,16 @@ description: Install File Browser to browse and manage your server files from a
 
 
 :ellipsis{left=0px width=40rem top=10rem blur=140px zIndex=60}
-# File Browser
-
-::note
-🎯 __Objectives:__
-
-- Install File Browser
-- Expose File Browser using Swag
-::
 
 [File Browser](https://github.com/filebrowser/filebrowser) is a web-based interface that lets you access and edit the files on your server.
 
 ![File Browser](/img/serveex/filebrowser.png)
 
 ## Installation
+
+::steps{level="3"}
+### Deploy the stack
+
 Open Dockge, click on `compose`, name the stack `filebrowser`, then copy and paste the following:
 
 ```yaml [compose.yaml]
@@ -49,6 +45,9 @@ services:
 
 Deploy the container and go to `http://yourserverip:8010`. That’s it! Your File Browser web UI is up and running!
 
+### Done !
+::
+
 ::caution
 
 __If it doesn’t work:__ check your firewall rules.
@@ -68,6 +67,9 @@ You may want to access File Browser remotely from all your devices. To do that,
 __Pre-requisite:__ We assume you've already created a subdomain like `files.yourdomain.com` in your [DNS zone](/general/networking/dns) pointing to `yourdomain.com` with a `CNAME`. Unless you're using Cloudflare Zero Trust, we also assume you've already forwarded port `443` on your router to port `443` on your server using [NAT rules](/general/networking/nat).
 ::
 
+::steps{level="3"}
+### Add File Browser's network to SWAG
+
 In Dockge, go to the SWAG stack and edit the compose file to add File Browser’s network:
 
 ```yaml [compose.yaml]
@@ -94,6 +96,8 @@ Here, we assume the network name for File Browser is `filebrowser_default`. You
 
 Restart the stack by clicking "deploy" and wait for SWAG to fully initialize.
 
+### Create the subdomain.conf file
+
 In the Swag folders, create the file `files.subdomain.conf`.
 
 ```bash [Terminal]
@@ -154,6 +158,9 @@ server {
 
 Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
 
+### Done !
+::
+
 That’s it! File Browser is now exposed!
 
 ## Protecting File Browser with TinyAuth