RIM's 1st album, released on 21 Jul 2021.
Note: these are guides, not strict rules. This is a wiki, just throw stuff up here and I'll format it later, maybe when I have time.
I'm still experiementing with different stuff, and don't have time to follow all these strictly either. These are just reminders.
The title should be the translated english song name.
The subtitle should have the original japanese song name, romanji translation of the song name, and vocalist. These are helpful when people are searching, which'll only show the title and subtitle of a page.
The location (aka link) to the page should be same as the title, but formatted into all lowercase, and use hyphens for spaces. For example, "/to-kiss-this-world" for "To Kiss This World".
Probably should tag a page with the vocalist, maybe genre? we'll have to decide what tags are needed later.
We're using css to remove horizontal line breaks between rows in the lyrics tables, and to reduce padding (spacing) between rows.
Custom CSS for a page can be edited at: edit a page -> blue "Page" action top right -> "Styles tab
Whe creating a page, copy from an already styled page and place in the new page. Here's one styled page.
A song page should have an introduction section, that has the following:
The introduction section to a song does not need a header.
I prefer to use the markdown editor, instead of the html editor. Markdown is cleaner and easier to write. Wikijs documentation does not recommend using HTML editor.
I'd convert all pages inside Song directory (/song-lyrics) to use the markdown editor for consistency, but there isn't an option in Page Actions. Either because wiki.js is outdated (requiers 2.5.201), or converting might require admin previleges.
The following pages inside Song directory (/song-lyrics) are using html editor, updated 2021-06-16:
We can typeset furigana, or hiragana annotations on top of kanjis, by using the ruby annotations. The standard
<ruby> HTML tag is implemented in all major browsers.
We have to write the raw ruby HTML tags inside markdown. There is no builtin support for generating ruby HTML tags from markdown. (Wiki.js takes markdown code, generates HTML code, then displays it.)
The biggest reason of using markdown editor instead of HTML is that it's cleaner. Markdown is less verbose, easier to write, look at, and edit. Not having a clean way to write ruby annotations in markdown undermines this.
If we're to implement ruby support in markdown, we first need to find a library, if we don't want to decide on the syntax and write code ourselves. There are a few libraries, one candidate might be markdown-it-ruby. And to actually use the library, we'll need to create a Pull Request on Wiki.js, or fork it and implement ourselves. See this PR for reference.
But that's a lot of work, so we can just simply write less ruby annotations and call it a day, but:
Ruby annotations are helpful for people learning japanese, especially on difficult kanjis (溢?), and on uncommon readings (愛 as いと instaed of あい?).
Having annotations on all kanjis can be helpful to beginners (me), but too many annotations might be distracting, and ruby annotations are annoying to write and edit.
I'm not sure whrere's the balance on when to use ruby annotations, or maybe just not use annotations at all because it's too much work.
I wasn't sure if we want to present the english lyrics only (copy-paste-done), or want to make a jp-en side-by-side thing. So I tried both and placed them in tags to compare. But the tabs thing looks good too so we're keeping the tabs now.