restore steps component (#23)

Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>

Author: EdwardAngert

src/content/docs/pi-hole/block-allow-lists.mdx

@@ -87,7 +87,7 @@ HaGeZi already includes these as upstream sources.
 They can create duplicate entries without providing additional coverage.
 Pi-hole deduplicates during Gravity updates so it won't break anything, but it's unnecessary weight.
 
-{/* <Steps> */}
+<Steps>
 
 1. Choose one core HaGeZi list:
 
@@ -159,13 +159,13 @@ Pi-hole deduplicates during Gravity updates so it won't break anything, but it's
      https://blocklistproject.github.io/Lists/phishing.txt
      ```
 
-{/* </Steps> */}
+</Steps>
 
 ## Add Blocklists to Pi-hole
 
 To add a list:
 
-{/* <Steps> */}
+<Steps>
 
 1. Log in to the Pi-hole web interface at `https://pi-hole.local/admin`.
 1. Go to **Lists**.
@@ -178,7 +178,7 @@ To add a list:
 
    Gravity also runs automatically on a weekly schedule.
 
-{/* </Steps> */}
+</Steps>
 
 ## Add Allowlists and Domains to Pi-hole
 
@@ -194,7 +194,7 @@ There are two ways to allowlist in Pi-hole v6:
 The HaGeZi Referral Allowlist is a maintained collection of domains that blocklists commonly block but that services legitimately need.
 Adding it as a subscription prevents a large category of false positives before they happen.
 
-{/* <Steps> */}
+<Steps>
 
 1. In the Pi-hole web interface, go to **Lists**.
 1. Paste the allowlist:
@@ -212,7 +212,7 @@ Adding it as a subscription prevents a large category of false positives before
 
    Gravity also runs automatically on a weekly schedule.
 
-{/* </Steps> */}
+</Steps>
 
 ### Add an Individual Domain to the Allowlist
 
@@ -340,7 +340,7 @@ A device can be added to multiple groups at the same time and will follow the co
 
 Useful for a device where blocking breaks functionality and you can't or would rather not troubleshoot it (smart TVs, streaming sticks, Paramount+, Roku).
 
-{/* <Steps> */}
+<Steps>
 
 1. Find the device's IP address in **Tools** > **Network** or based on its traffic in the **Query Log**.
 
@@ -353,7 +353,7 @@ Useful for a device where blocking breaks functionality and you can't or would r
 
 1. Select **Add**.
 
-{/* </Steps> */}
+</Steps>
 
 The device now resolves DNS without any filtering.
 All other devices are unaffected.
@@ -363,7 +363,7 @@ All other devices are unaffected.
 Apply extra blocklists on top of the normal ones without affecting the rest of the network.
 This can be useful for a child's device or a school-issued laptop.
 
-{/* <Steps> */}
+<Steps>
 
 1. Confirm that the device's network traffic isn't being routed through a VPN.
 
@@ -399,7 +399,7 @@ This can be useful for a child's device or a school-issued laptop.
 
 1. Select **Add**.
 
-{/* </Steps> */}
+</Steps>
 
 The device is now blocked by everything in `Default` as well as the extra lists.
 Other devices that are not in the new group are unaffected.

src/content/docs/pi-hole/install-configure.mdx

@@ -37,21 +37,21 @@ brew install sdformatter raspberry-pi-imager
 This process erases everything on the SD card.
 :::
 
-{/* <Steps> */}
+<Steps>
 
 1. Insert a microSD card, then open SD Card Formatter and choose the card from the **Select card** dropdown.
 1. Select **Format** to format the card.
    - The default settings are fine: Quick format and no volume label.
 1. Exit SD Card Formatter and leave the SD card inserted.
 
-{/* </Steps> */}
+</Steps>
 
 ## Create the Pi OS Image on the SD Card
 
 Raspberry Pi Imager makes the SD card a bootable drive.
 After you set up the SD card, you'll install it in the Raspberry Pi as its primary drive.
 
-{/* <Steps> */}
+<Steps>
 
 1. Open Raspberry Pi Imager.
 1. **Select your Raspberry Pi Device**: Raspberry Pi 4.
@@ -74,7 +74,7 @@ After you set up the SD card, you'll install it in the Raspberry Pi as its prima
 1. When the write completes, remove the SD card from your computer and insert it into the Raspberry Pi.
 1. Plug in the Pi and give it a few minutes to boot.
 
-{/* </Steps> */}
+</Steps>
 
 <details>
 <summary>Rebuilds and Upgrades: Confirm Your Linux Version</summary>
@@ -92,7 +92,7 @@ PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
 
 ## Configure Raspberry Pi OS
 
-{/* <Steps> */}
+<Steps>
 
 1. Find the Pi's IP Address:
 
@@ -148,14 +148,14 @@ PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
    ip addr show eth0
    ```
 
-{/* </Steps> */}
+</Steps>
 
 #### TP-Link Omada-specific steps to find and fix the Pi's IP
 
 <details>
 <summary>Find the Pi and set a fixed IP on a TP-Link Omada controller</summary>
 
-{/* <Steps> */}
+<Steps>
 
 1. Log in and select the site's name.
 1. Select **Clients** then **Wired** to filter the table of connected clients.
@@ -165,7 +165,7 @@ PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
 
    You should still follow the steps in the [Set a Static IP](#set-a-static-ip-address) section when you get there.
 
-{/* </Steps> */}
+</Steps>
 
 ![Set fixed IP in Omada controller](./screenshots/omada-fixed-ip-address.png)
 
@@ -178,7 +178,7 @@ The non-root user that Raspberry Pi Imager created can run `sudo` commands witho
 Raspberry Pi Imager creates a configuration file to enforce passwordless `sudo`.
 Remove the file so that sudo commands require authentication.
 
-{/* <Steps> */}
+<Steps>
 
 1. Remove the configuration file:
 
@@ -193,15 +193,15 @@ Remove the file so that sudo commands require authentication.
    ssh pi-admin@pi-hole.local
    ```
 
-{/* </Steps> */}
+</Steps>
 
 ### Set Up a Firewall on Your Pi With UFW
 
 UFW (Uncomplicated Firewall) restricts which ports are accessible on the Pi.
 Pi-hole requires ports for DNS and the web interface.
 SSH is allowed for remote administration.
 
-{/* <Steps> */}
+<Steps>
 
 1. Install UFW:
 
@@ -255,7 +255,7 @@ SSH is allowed for remote administration.
    sudo ufw status
    ```
 
-{/* </Steps> */}
+</Steps>
 
 <details>
 <summary>If you plan to use Pi-hole as a DHCP server</summary>
@@ -275,7 +275,7 @@ sudo ufw allow 67/udp comment 'DHCP'
 Fail2Ban automatically bans IPs that fail too many login attempts.
 This helps minimize the risk of brute-force attacks.
 
-{/* <Steps> */}
+<Steps>
 
 1. Install Fail2Ban:
 
@@ -312,7 +312,7 @@ This helps minimize the risk of brute-force attacks.
 
    You should see the jail listed as active with 0 currently banned IPs on a fresh install.
 
-{/* </Steps> */}
+</Steps>
 
 ### Set a Static IP Address
 
@@ -323,7 +323,7 @@ These steps use `nmcli` to lock the IP.
 They set the Ethernet connection name as a temporary shell variable.
 The variable is cleared when you exit the session.
 
-{/* <Steps> */}
+<Steps>
 
 1. Set the static IP, gateway, and DNS.
 
@@ -389,7 +389,7 @@ The variable is cleared when you exit the session.
 
    Wait a few minutes before you SSH back in.
 
-{/* </Steps> */}
+</Steps>
 
 ## Checkpoint
 

src/content/docs/pi-hole/maintenance.mdx

@@ -34,12 +34,12 @@ sudo pihole -g
 
 Pi-hole's Teleporter exports your full configuration: blocklists, allowlists, custom domains, regex rules, DNS settings, and DHCP config.
 
-{/* <Steps> */}
+<Steps>
 
 1. In the Pi-hole web interface, go to **Settings** > **Teleporter**.
 1. Select **Export** to download a backup file.
 
-{/* </Steps> */}
+</Steps>
 
 To restore after a rebuild or SD card failure, use the **Import** option on the same page and select the backup file.
 
@@ -107,7 +107,7 @@ Move the database and log file to a USB drive to protect the SD card and extend
 
 ### Mount the USB drive
 
-{/* <Steps> */}
+<Steps>
 
 1. Plug in the USB drive and find its device name:
 
@@ -166,11 +166,11 @@ Move the database and log file to a USB drive to protect the SD card and extend
    sudo chown pihole:pihole /mnt/pihole-logs
    ```
 
-{/* </Steps> */}
+</Steps>
 
 ### Point Pi-hole to the USB drive
 
-{/* <Steps> */}
+<Steps>
 
 1. Back up the current `pihole.toml`:
 
@@ -226,14 +226,16 @@ Move the database and log file to a USB drive to protect the SD card and extend
    The FTL service won't start if it can't find the database file.
    DNS queries from all network devices will fail until the mount is fixed.
 
-{/* </Steps> */}
+</Steps>
 
 ### Optional: Set Pi-hole database retention
 
 By default, Pi-hole keeps 91 days of query history.
 
 If you want to change the database size:
 
+<Steps>
+
 1. Set a the number of days to keep the database in `pihole.toml`:
 
    ```toml title="pihole.toml"
@@ -246,3 +248,5 @@ If you want to change the database size:
    ```shell title="From the Pi"
    sudo systemctl restart pihole-FTL
    ```
+
+</Steps>

src/content/docs/pi-hole/network-level-blocking.mdx

@@ -40,7 +40,7 @@ Look for **DHCP**, **LAN**, or **DNS** settings.
 
 ![Omada controller DNS server settings](./screenshots/omada-dns-server-settings.png)
 
-{/* <Steps> */}
+<Steps>
 
 1. Log in to the Omada controller and select the site's name.
 1. In the sidebar, under **Configuration**, select **Network Config** > **LAN**.
@@ -51,7 +51,7 @@ Look for **DHCP**, **LAN**, or **DNS** settings.
 1. In the second box, enter `1.1.1.1` to use Cloudflare as a backup DNS server.
 1. Select **Next** to save and apply the settings.
 
-{/* </Steps> */}
+</Steps>
 
 After you save the settings, devices need to renew their DHCP lease to pick up the new DNS server.
 This happens automatically when the lease expires (typically within 24 hours, depending on your router), or immediately if you disconnect and reconnect Wi-Fi, or restart the device.
@@ -68,7 +68,7 @@ Some smart devices like Chromecast and Samsung Smart TVs ignore the DNS server y
 - **Samsung Smart TVs** may use `8.8.8.8` for some services even when a different DNS is assigned.
 - **Android and iOS** support encrypted DNS (DNS-over-HTTPS or DNS-over-TLS), which can send queries directly to Google or Cloudflare, bypassing Pi-hole completely.
 
-{/* <Steps> */}
+<Steps>
 
 1. To force traffic from these devices through the Pi-hole, add NAT rules that intercept all outbound DNS on port 53.
 
@@ -97,7 +97,7 @@ Some smart devices like Chromecast and Samsung Smart TVs ignore the DNS server y
 
    You should see two rules with `DNAT` and `to:YOUR-PI-IP` — one for `udp dpt:domain` and one for `tcp dpt:domain`.
 
-{/* </Steps> */}
+</Steps>
 
 To verify a specific device is now routing through Pi-hole, check the query log at `https://pi-hole.local/admin/queries` and filter by that device's IP.
 You should see its DNS requests appearing there.

src/content/docs/pi-hole/pihole-install.mdx

@@ -27,7 +27,7 @@ If you installed Pi-hole on an existing device or skipped to this section, these
 
 </details>
 
-{/* <Steps> */}
+<Steps>
 
 1. SSH to the Pi:
 
@@ -80,7 +80,7 @@ If you installed Pi-hole on an existing device or skipped to this section, these
 
    If you don't see the option to proceed, refresh the page.
 
-{/* </Steps> */}
+</Steps>
 
 ## Optional: Configure Unbound as Recursive DNS
 
@@ -91,7 +91,7 @@ This means no single upstream provider sees all your DNS queries.
 Pi-hole works well with Cloudflare.
 Add unbound if you prefer the additional privacy of recursive resolution.
 
-{/* <Steps> */}
+<Steps>
 
 1. Install unbound, then immediately stop it so that you can set your own configuration:
 
@@ -167,7 +167,7 @@ Add unbound if you prefer the additional privacy of recursive resolution.
    You should see a `NOERROR` status.
    The first query may be slow as unbound builds its cache.
 
-{/* </Steps> */}
+</Steps>
 
 :::caution["port 53: Address in use"]
 If you install unbound and don't stop it right away, it will self-assign port 53 and conflict with the Pi-hole.
@@ -191,7 +191,7 @@ It shows query rate, cache hits, blocked domains, and FTL status alongside syste
 The Pi-hole web interface already shows DNS stats.
 Add Netdata if you want system-level metrics alongside your Pi-hole data.
 
-{/* <Steps> */}
+<Steps>
 
 1. Install Netdata:
 
@@ -238,7 +238,7 @@ Add Netdata if you want system-level metrics alongside your Pi-hole data.
 
    The **Fail2Ban** section will appear in the dashboard showing currently banned IPs and active failures for each jail.
 
-{/* </Steps> */}
+</Steps>
 
 ## Checkpoint