Convert the remaining Serveex and recycled articles to steps

content/en/3.serveex/8.development/2.forgejo.md

@@ -5,17 +5,12 @@ description: Install Forgejo, a lightweight self-hosted Git service to manage yo
 
 
 :ellipsis{left=0px width=40rem top=10rem blur=140px zIndex=60}
-# Forgejo
 
-::note
-🎯 __Goals:__
-
-- Install Forgejo
-- Expose Forgejo using Swag
-::
 
 [Forgejo](https://forgejo.org/) is a self-hosted DevOps platform that allows you to manage repositories much like GitHub, but on your own infrastructure. It's a community-driven fork of Gitea.
 
+![forgejo](/img/serveex/forgejo.png)
+
 ## Installation
 
 ::file-tree
@@ -30,6 +25,9 @@ tree:
 ---
 ::
 
+::steps{level="3"}
+### Deploy the stack
+
 Open Dockge, click on `compose`, name the stack `forgejo`, and paste the following content:
 
 ```yaml [compose.yaml]
@@ -55,6 +53,8 @@ services:
       - 222:22
 ```
 
+### Set your environment variables
+
 Fill out the `.env` file with the required information, for example:
 
 ```properties [.env]
@@ -64,6 +64,9 @@ GID=1000
 
 Deploy the container and go to `http://yourserverip:3333`. Your Forgejo instance is now up and running!
 
+### Done !
+::
+
 ::caution
 
 __If it fails:__ check your firewall rules.
@@ -77,6 +80,9 @@ The benefit of this setup is being able to access it remotely from any of your d
 __Prerequisite:__ We assume you have created a subdomain such as `forgejo.yourdomain.com` in your [DNS zone](/general/networking/dns) with `CNAME` pointing to `yourdomain.com`, and [unless you're using Cloudflare Zero Trust](/serveex/security/cloudflare), you have already forwarded port `443` from your router to your server’s port `443` in the [NAT rules](/general/networking/nat).
 ::
 
+::steps{level="3"}
+### Add Forgejo's network to SWAG
+
 In Dockge, go to the SWAG stack and edit the compose file by adding Forgejo's network:
 
 ```yaml [compose.yaml]
@@ -103,6 +109,8 @@ We assume the Forgejo network name is `forgejo_default`. You can verify connecti
 
 Redeploy the stack by clicking "Deploy" and wait until SWAG is fully operational.
 
+### Create the subdomain.conf file
+
 Inside the Swag folders, create the file `forgejo.subdomain.conf`.
 
 ::tip{icon=""}
@@ -173,6 +181,8 @@ server {
 
 Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
 
+### Configure Forgejo's domain
+
 Now open the `app.ini` file from the container's file system:
 
 ```bash [Terminal]
@@ -190,6 +200,9 @@ ROOT_URL = https://forgejo.yourdomain.com/
 
 Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit, then restart the container.
 
+### Done !
+::
+
 And that’s it! Forgejo is now exposed to the web.
 
 ## Protecting Forgejo with Pocket ID