mikkeli cbee2a5f95 274: vendor the transect page into the repo
Keeps the interactive map available offline and under version control
while the song is in progress.

- 274-transect.html — self-contained; carries its data in a script block,
  fonts from Google Fonts, no other external requests. Opens by double
  clicking. Same page as the published artifact.
- 274-route.json, 274-districts.json — the route line and the 23 大字
  bands from the 250 m reverse-geocode sweep.
- 274-transect-build.py — re-reads the roster out of 274-dev.md and
  rewrites the page's data block in place, leaving markup and script
  alone. Run it after editing the table.

Everything under wip/ so the auto-wiki pipeline leaves it alone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
2026-09-11 01:06:57 +09:00
2026-02-17 14:10:46 +09:00

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.

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, outside wip/). 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 ```columns fence — 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).
  • N columns ⇒ 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.

S
Description
Lyrics repo
Readme 1.2 MiB
Languages
Markdown 100%