feat(blog): add deployer-based tracker deployment article

src/routes/blog/deploying-torrust-to-production/+page.svelte

@@ -26,6 +26,18 @@
 		<div class="wrapper">
 			<Toc class="toc" />
 			<div id="toc-contents" class="content-preview">
+				<Callout type="info">
+					<strong>Update (April 2026):</strong> We now have the
+					<a href="/blog/deploying-torrust-tracker-with-the-deployer">Torrust Tracker Deployer</a>,
+					a tool that automates most of the steps described in this guide. If you are starting a new
+					deployment, we recommend reading
+					<a href="/blog/deploying-torrust-tracker-with-the-deployer"
+						>Deploying the Torrust Tracker Demo with the Torrust Tracker Deployer</a
+					>
+					instead. This guide remains useful as a reference for understanding what the deployer does under
+					the hood, or for deploying on providers the deployer does not yet support.
+				</Callout>
+
 				<h2 id="introduction">Introduction</h2>
 				<p>
 					Welcome to our guide on deploying a BitTorrent Index and Tracker. We&#39;ll walk you

src/routes/blog/deploying-torrust-tracker-with-the-deployer/+page.server.ts

@@ -0,0 +1,14 @@
+import { getMetadata } from '$lib/data/metadata';
+import type { PageServerLoad } from './$types';
+
+export const load: PageServerLoad = async ({ url }) => {
+	const slug = url.pathname.split('/').filter(Boolean).pop();
+	if (!slug) throw new Error('Slug could not be determined.');
+
+	const metadata = await getMetadata();
+	const currentPost = metadata.find((post) => post.slug === slug);
+
+	if (!currentPost) throw new Error(`Post not found: ${slug}`);
+
+	return { currentPost, allPosts: metadata };
+};