Remove migration tooling and documentation

The import is verified and content/ is now the source of truth, so the
one-shot WordPress importer under tools/ and MIGRATION.md are no longer
needed. Also drops the remaining references to the old site from the
README, config comments and data-file headers.

Build is unchanged: 38 pages, 718 internal links, none broken.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -5,8 +5,6 @@ Static website of the Motorradclub Giebelwald e.V., built with [Hugo](https://go
 - Development: <https://mcg.luxick.de>
 - Production: <https://motorradclub-giebelwald.de>
 
-Migrated from WordPress in July 2026 — see [MIGRATION.md](MIGRATION.md).
-
 ## Requirements
 
 Hugo **0.164.0**. The *non-extended* build is sufficient: the site uses plain CSS,
@@ -46,7 +44,7 @@ it the first image in the folder is used.
 
 ### Add or change a Termin
 
-Edit `data/termine.yaml`. Newest year is shown expanded, older years collapse:
+Edit `data/termine.yaml`. The newest year is shown expanded, older years collapse:
 
 ```yaml
 "2027":
@@ -74,6 +72,23 @@ Put the PDF in `static/dokumente/` and link it from `content/downloads.md`:
 | `{{< figure "bild.jpg" "Bildunterschrift" >}}` | Single image with caption |
 | `{{< pdf "datei.pdf" "Titel" >}}` | Download link with file size |
 
+## Site structure
+
+```
+content/
+  _index.md              Startseite
+  aktuelles/             News section (RSS enabled)
+  archiv/                Rückblicke auf frühere Fahrten
+  termine.md             uses layouts/termine.html + data/termine.yaml
+  downloads.md
+  impressum.md
+data/                    termine, members, memoriam
+assets/                  css/main.css, img/ (logo, banner, portraits)
+static/dokumente/        PDFs
+layouts/                 baseof, home, list, page, termine
+  _partials/  _shortcodes/  _markup/
+```
+
 ## Deployment
 
 `.gitea/workflows/deploy.yml` builds with Hugo and rsyncs `public/` over SSH.
@@ -99,17 +114,3 @@ Set these in the Gitea repository settings:
 rsync runs with `--delete`, so each `DEPLOY_PATH_*` must point at a directory
 owned solely by this site. The workflow refuses to deploy if the path is unset,
 too shallow, or if the build produced no `index.html`.
-
-## Migration tooling
-
-`tools/` holds the one-shot WordPress importer, kept so the import stays
-reproducible and reviewable. It is not part of the build.
-
-```sh
-python tools/fetch_media.py       # download uploads from the live WP host
-python tools/build_data.py        # termine / members / memoriam
-python tools/wp2hugo.py           # content bundles (won't overwrite; --force to do so)
-python tools/verify_migration.py  # inventory + link checks (run after `hugo`)
-```
-
-Requires Python 3.11+ and Pillow.