Merge #186: feat: add blog post about submitting trackers to newTrackon

20e825c feat: add blog post about submitting trackers to newTrackon (Jose Celano)

Pull request description:

  ## Summary

  Adds a new blog post: **Submitting Trackers to newTrackon**.

  Closes #185

  ## What's in the post

  - **Introduction** — what newTrackon is and why independent uptime monitoring matters
  - **Prerequisites** — all 5 checks newTrackon performs before accepting a tracker (including announce interval 300–10800 s)
  - **One tracker per IP constraint** — how newTrackon deduplicates by IP, not just URL
  - **Solution: Floating IPs** — how we use Hetzner floating IPs to list UDP and HTTP/S endpoints independently
  - **BEP34 DNS configuration** — TXT record syntax and our setup for each domain
  - **Submitting to newTrackon** — step-by-step walkthrough
  - **Troubleshooting: Tracker Shows as Down** — four sub-sections:
    - IPv6 routing with Docker and floating IPs (ip6tables, DNAT/SNAT)
    - Using `newtrackon.com/raw` to inspect probe results
    - Running a local copy of newTrackon
    - Using the Torrust Tracker console client

  ## Other changes

  - `static/blogMetadata.json` — regenerated to include the new post
  - `.github/skills/add-blog-post/SKILL.md` — updated step 5 to document SEO-friendly cover image naming convention
  - Cover image: `static/images/posts/submitting-trackers-to-newtrackon/submitting-bittorrent-tracker-to-newtrackon.webp`

  ## Checklist

  - [x] `npm run check` — 0 errors, 0 warnings
  - [x] `npm run lint` — all files pass Prettier + ESLint
  - [x] Pre-commit hook — all checks passed
  - [x] Cover image added with SEO-friendly filename
  - [x] `blogMetadata.json` regenerated

ACKs for top commit:
  josecelano:
    ACK 20e825c

Tree-SHA512: 3fd15031222f898c598c8edff4b03d7f538742ae2e5f18a040178ec72e2cc0a51c8028be1d425264c1a768c7ebd3327565780578b2b6c0464ce334c19940d987

Author: josecelano

.github/skills/add-blog-post/SKILL.md

@@ -329,10 +329,22 @@ Never invent names like `bp.md`, `bp.lg`, `bp.sm` — they will cause a Sass com
 
 ### 5. Add a cover image
 
-Place the cover image at:
+Place the cover image under `static/images/posts/<post-slug>/`. Use an **SEO-friendly filename** — a descriptive kebab-case name that reflects the post topic, not a generic name like `cover.webp`:
 
 ```
-static/images/posts/<post-slug>/cover.webp
+static/images/posts/<post-slug>/descriptive-kebab-case-name.webp
+```
+
+For example, for a post about submitting trackers to newTrackon:
+
+```
+static/images/posts/submitting-trackers-to-newtrackon/submitting-bittorrent-tracker-to-newtrackon.webp
+```
+
+Update `coverImage` in `metadata.ts` to match the exact filename you chose:
+
+```typescript
+coverImage: '/images/posts/<post-slug>/descriptive-kebab-case-name.webp',
 ```
 
 - Preferred format: WebP

src/routes/blog/submitting-trackers-to-newtrackon/+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 };
+};