17 lines
1.2 KiB
Markdown
17 lines
1.2 KiB
Markdown
# Tip #11 — Broken-Link-Checker
|
|
|
|
**Date:** 2026-06-22
|
|
**Category:** data
|
|
**Source:** MC-Survival Wiki Daily Tip (backfilled from state.json)
|
|
**Note:** *Title was truncated in the original state.json log. Body matches the 'Search-Synonyms alias table' variant of the same idea.*
|
|
|
|
## Broken-Link-Checker
|
|
|
|
A scheduled server function that walks every recipe and tab, extracts the internal links from their content, and reports the ones that no longer resolve to a live page. It solves the silent-link-rot problem: when a recipe slug is renamed, every old link in body text becomes a 404 that nobody notices until a user complains. The signal is operational: the wiki has grown enough that renames happen regularly, and a weekly broken-link report is the cheapest way to keep the link graph healthy. Running weekly rather than daily is intentional — the data barely changes in 24 hours, and admins have time to act on the report without it becoming noise.
|
|
|
|
## Implementation tips
|
|
|
|
1. Scheduled server function (cron-like) that fetches all recipe/tab slugs, checks each link in their content.
|
|
2. Return a list of broken links; admins see a dashboard widget '23 broken links across 18 pages'.
|
|
3. Run weekly — not daily. The data barely changes.
|