mikkeli
1ec8aff737
Replaces the three separate tables (structures / watercourses / PoI) with one table in road order, and adds a Name column: the proper noun with generic tails stripped (橋, 川, トンネル, 覆道, 郵便局, 発電所, 町, 丁目), Ainu size qualifiers stripped (パンケ, ペンケ, ポン), and variants aliased (十三哩→十三里, 滝ノ上→滝の上, 浪ノ沢→浪の沢, 能見→熊見, クルキ→久留喜, 三川 compounds folded together). Objects are kept in full alongside, with kilometre, offset, kind, WGS84 coordinates and the register attributes. 188 entries, 119 distinct names, 15 names carried by three or more objects. Adds machine-readable copies for later visualisation work: 274-lookup.csv and 274-lookup.geojson (route line plus one point per entry, all properties carried through). Name extraction is mechanical and meant to be corrected by hand. 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.