Roster now carries, for every entry: kana and romaji readings, the administrative address with its reading, and the 大字 it sits in. - Kana/Romaji columns prefilled from OSM name:ja-Hira / name:ja-Latn where they exist (42 of 170); the rest are blank rather than guessed, pending the plaque readings. - Address and Address kana for all 170, from 国土地理院 reverse geocoding joined to GSI muni.js and 日本郵便 郵便番号データ. Confirms 千栄=ちさか and 穂別長和=ほべつおさわ. - District transect: the route sampled every 250 m gives 23 大字 bands with entry and exit kilometres. R274 does not pass through 字ニニウ at all — it runs 穂別福山 → 字中央 → 字日高, and both municipal boundaries fall inside tunnels (穂高 and 日高). - Fixes a real bug: duplicate-named features shared one set of coordinates, so both セイコーマート pointed at the same spot 50 km apart. 12 coordinate cells were wrong. - 沙流川 added at 105.67 km, where the road joins its valley at 右左府, rather than at its nearest point past the range end. - Kind labels normalised to English throughout. CSV and GeoJSON regenerated from the Markdown, which is now the source of truth. GeoJSON also carries the district bands as geometryless features. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
Northwich committee of magic researches songs repository
Just a collection of lyrics of songs. Probably will be managed into proper folders. Probably will have LRCs.
Publishing to the wiki
Song pages are auto-published to https://wiki.novoyuuparosk.org by the
songs pipeline in the companion repo novoyuuparosk-auto-wiki (the
"repo next door"). It triggers on push to master.
- Source-file contract (frontmatter fields, body conventions): see
pipelines/songs/SCHEMA.mdinnovoyuuparosk-auto-wiki. - Pipeline overview (branch convention, triggers, categories, LRC, etc.):
pipelines/songs/README.md.
In short: a file is published when its frontmatter has wiki.publish: true
and it isn't under wip/. The title field becomes the wiki page name.
Linking to another song page
Write an ordinary relative Markdown link. There is nothing to declare in the frontmatter:
For more behind-the-scene shenanigans, see [Dev gibberish](pulse_dev.md).
At publish time the .md target is swapped for the target file's own title,
giving a proper wikilink — so renaming a page means editing its title and
nothing else. The link keeps working in Gitea's blob view and in any editor
preview, because it is just a link.
Two things to know:
- The target must be published too (
wiki.publish: true, outsidewip/). Linking to a file does not publish it; an unresolvable link fails the CI run instead of quietly turning into plain text. - Links do not work inside a
```columnsfence — that block is verbatim by design. Put them in ordinary prose.
This replaces the old wiki.siblings frontmatter block and its ALL_CAPS
placeholders, which are gone.
Side-by-side lyrics (columns shorthand)
To lay two (or more) versions of a song next to each other — e.g. an original
and its translation — use a fenced code block tagged columns, with each
column separated by a line containing only ===:
```columns
**原題**
一行目
二行目
===
**Title**
first line
second line
```
Notes:
- Line breaks and blank lines are preserved verbatim (each column is rendered with line breaks intact).
Ncolumns ⇒N − 1===separators.- Use Markdown emphasis inside the block:
*italic*,**bold**,***bold-italic***. (No need for raw HTML.)
This is implemented entirely by the auto-wiki pipeline at publish time; the
authoritative description lives in
SCHEMA.md.
See kairo/kimito_en.md for a real example.