Convert the remaining Serveex and recycled articles to steps

content/en/3.serveex/7.files/1.file-browser-quantum.md

@@ -5,18 +5,10 @@ description: Install File Browser Quantum, a modernized fork of File Browser, to
 
 
 :ellipsis{left=0px width=40rem top=10rem blur=140px zIndex=60}
-# File Browser Quantum
-
-::note
-🎯 __Objectives:__
-
-- Install File Browser Quantum
-- Expose File Browser Quantum using Swag
-::
 
 [File Browser Quantum](https://github.com/gtsteffaniak/filebrowser) is a community fork of [File Browser](/recycled/deprecated/file-browser), rewritten for better performance (indexed search, lower memory use) and configured through a single `config.yaml` file instead of a database-only setup.
 
-If you're already using File Browser and it fits your needs, there's no need to switch. The two are independent projects with their own configuration and can't share data directly.
+![file-browser-quantum](/img/serveex/filebrowser-quantum.png)
 
 ## Installation
 
@@ -33,6 +25,9 @@ tree:
 ---
 ::
 
+::steps{level="3"}
+### Create the config file
+
 Create the data folder:
 
 ```bash [Terminal]
@@ -61,6 +56,8 @@ server:
 
 Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
 
+### Deploy the stack
+
 Open Dockge, click on `compose`, name the stack `filebrowser-quantum`, then copy and paste the following:
 
 ```yaml [compose.yaml]
@@ -98,6 +95,9 @@ Mount every folder you listed under `sources` in `config.yaml` at the same path
 
 Deploy the container and go to `http://yourserverip:8020`. Log in with the default `admin` / `admin` credentials, then immediately change the password in your profile settings.
 
+### Done !
+::
+
 ::caution
 
 __If it doesn't work:__ check your firewall rules.
@@ -112,11 +112,14 @@ File Browser Quantum does not support multi-factor authentication. Exposing it p
 
 You may want to access File Browser Quantum remotely from all your devices. To do that, we'll expose it through Swag.
 
-::note
+::note{icon=""}
 
-__Pre-requisite:__ We assume you've already created a subdomain like `fbq.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).
+📋 __Pre-requisite:__ We assume you've already created a subdomain like `fbq.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 Quantum's network to SWAG
+
 In Dockge, go to the SWAG stack and edit the compose file to add File Browser Quantum's network:
 
 ```yaml [compose.yaml]
@@ -143,6 +146,8 @@ Here, we assume the network name for File Browser Quantum is `filebrowser-quantu
 
 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 `fbq.subdomain.conf`.
 
 ```bash [Terminal]
@@ -199,6 +204,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 Quantum is now exposed.
 
 ## Protecting File Browser Quantum with TinyAuth

content/en/3.serveex/7.files/2.pingvin.md

@@ -77,7 +77,7 @@ __If it fails:__ check your firewall rules.
 ## Exposing Pingvin with Swag
 The whole point of a solution like this is being able to access it remotely, from all your devices. To do this, we'll expose Pingvin through Swag.
 
-::note
+::note{icon=""}
 📋 __Prerequisite:__ <br/><br/>
 We assume you have the subdomain `pingvin.mydomain.com` with a `CNAME` pointing to `mydomain.com` in your [DNS zone](/general/networking/dns). And of course, [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), port `443` on your router is forwarded to port `443` on your server via [NAT rules](/general/networking/nat).
 ::