mikkeli
c7e24949cc
Two places where the sung order did not follow the carriageway. 楓駐車帯 moves up one line, between 千紫橋 and 万紅橋. It sits at km 57.08, between their 56.60 and 57.25 — it was sung after 万紅橋. 穂別長和 splits into two headers around the 稲里 block. The road runs 長和 → 稲里 → 長和, but the two 長和 stretches had been welded into one block sung first, so the 稲里 block then started 10.84 km behind where the previous line left off. Now: 長和 62.36 - 62.94 オマナイ橋, 桂木橋 稲里 64.44 - 71.86 大和橋 … 穂別ダム神社 長和 72.02 - 75.28 長和トンネル … 稲里トンネル This is the same repeated-header pattern the song already uses for 由仁町川端 / 栗山町滝下 at the opening, where the road crosses back over the 夕張川. Applied to both 274.md and 274.lrc; the two are now identical, 98 lines each. Lyric order is monotonic by kilometre end to end. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.