<?xml version="1.0" encoding="UTF-8"?>
<!--
  metalign.org: the four pages, all of them.

  EVERY <loc> IS THAT PAGE'S OWN <link rel="canonical">, character for character. That is the
  rule this file is kept by, because when the two disagree a search engine picks one and
  neither of us knows which. It is also why the URLs are production's on a tree dev serves
  too: the canonicals already are, and dev's basic_auth gate means nothing there ever reads
  this. robots.txt carries the full reasoning, and states why it is ASCII where this is not.

  NO <lastmod>. It would be hand-maintained or nothing — this repo has no build step to stamp
  it — and a date that quietly stops being true is worse than an absent one, because an
  unreliable lastmod is a signal a crawler learns to discount for the whole site. Four pages
  get crawled on their own merits regardless. If it is ever wanted, it is one
  <lastmod>YYYY-MM-DD</lastmod> per url, and from then on a thing to remember on every copy
  edit, including the ones that only move a comma.

  NO <priority> and NO <changefreq>. Both are self-reported wishes rather than facts, Google
  stopped reading them in 2023, and four URLs do not need ranking against each other.

  THE LEGAL PAGES ARE LISTED. They are real pages a reader may look for by name, and § 5 DDG
  wants the Impressum leicht erkennbar; hiding it from search would be an odd reading of
  that. Listing them is not what decides whether they rank. It is what makes sure they are
  not missed.

  EVERY <loc> MUST BE A PAGE THAT ACTUALLY SHIPS, or this hands a crawler a 404, and the
  reverse holds too. Neither is left to anybody's memory: dev-deploy.yml's pre-flight asks
  both directions — a <loc> that would not ship, and a served page with no canonical in here
  — so adding a page fails the build until it is listed below. This file was written on `dev`
  while `main` was still the holding page, which is why it listed handbook.html before that
  page had ever been live: the two had to ship together, and the pre-flight is what checked
  that they did.

  A NOTE ON THE TENSE, because it is the reason the paragraph above was rewritten. What stood
  here said the handbook "does not exist on `main` today" — true when written, false from the
  first push that carried it, and served to anyone who fetches this file. The <lastmod>
  argument two paragraphs up applies to comments as much as to elements: a sentence about
  what is true this week does not belong in a file nobody rereads.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://metalign.org/</loc></url>
  <url><loc>https://metalign.org/handbook.html</loc></url>
  <url><loc>https://metalign.org/impressum.html</loc></url>
  <url><loc>https://metalign.org/datenschutz.html</loc></url>
</urlset>
