Add section summary pages and make single-link admonitions clickable

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

@@ -20,9 +20,9 @@ description: Install code-server to run VS Code in your browser from your homela
 ![code-server](https://github.com/coder/code-server/raw/main/docs/assets/screenshot-2.png)
 
 ## Installation
-::note
+::note{to="https://docs.linuxserver.io/images/docker-code-server/"}
 
-For this setup, we’ll use the [image maintained by LinuxServer.io](https://docs.linuxserver.io/images/docker-code-server/).
+For this setup, we’ll use the **image maintained by LinuxServer.io**.
 ::
 
 ::file-tree
@@ -167,8 +167,8 @@ Redeploy the stack by clicking “deploy” and wait until SWAG is fully operati
 
 Inside the Swag config folders, create the file `code.subdomain.conf`.
 
-::tip{icon=""}
-✨ __Tip:__ You can use [File Browser Quantum](/serveex/files/file-browser-quantum) to navigate and edit your files instead of using terminal commands.
+::tip{icon="" to="/serveex/files/file-browser-quantum"}
+✨ __Tip:__ You can use **File Browser Quantum** to navigate and edit your files instead of using terminal commands.
 ::
 
 ```bash [Terminal]
@@ -304,9 +304,9 @@ server {
 }
 ```
 
-::note
+::note{to="/serveex/security/tinyauth#exposing-tinyauth-with-swag"}
 
-The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from [exposing TinyAuth itself](/serveex/security/tinyauth#exposing-tinyauth-with-swag). If you run into an error, double-check SWAG's compose file still has that network attached.
+The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from **exposing TinyAuth itself**. If you run into an error, double-check SWAG's compose file still has that network attached.
 ::
 
 ::tip{icon=""}