HTML hymnbook chapters
If you speak another language and are familiar with HTML, you can help us prepare content so that hymnbooks and songbooks can be published in the Gospel Library app. Preparing hymnbooks and songbooks is part of the LDS Music Content project. Most content is entered by volunteers who don’t necessarily know HTML, but frontmatter and backmatter requires changing the text inside HTML elements, and sometimes adding or removing paragraphs.
All of the transcription and QA work is done on the Music Content Management System (MCMS). After joining the LDS Music Content project, go to the MCMS and log in with your LDS Account. Find the language and collection you would like to work on.
At the top of the collection page you will see a "Manifest" link. The manifest lists each chapter in the hymnbook. Chapters include frontmatter sections, songs, and backmatter sections. You can use the manifest to preview and check your work – when you save changes to a chapter, it will be updated in the manifest.
Back on the collection page, scroll to the very bottom, where you will see a list of the frontmatter and backmatter chapters. Next to each chapter is a colored label. If the label is green with a checkmark, it has already been completed. If it's blue, there's still work to do – either it needs to be transcribed, or QAed.
Click on the chapter you want to work on. You will see three fields: Title, Subtitle, and HTML. Every chapter has a title. Usually only the copyright page has a subtitle.
If you are the first person to transcribe a chapter, you will see an English template already in the HTML field. Click "Start Transcription." Replace the English text with the equivalent text from the hymnbook or songbook you're transcribing (Samuel can send you a PDF if needed), without deleting the HTML markup. Use the manifest preview as a resource to make sure everything is transcribed correctly.
After you transcribe a chapter, someone else will need to QA it.
- Stick to the templates as much as possible. If you see differences between the template and the book, feel free to ask questions.
- Do not add CSS. CSS styles are added by a developer in an external stylesheet. (Note that there's currently a bug with where divider lines are placed in some chapters – you can ignore divider lines for now.)
- Use the <em> and <strong> elements for italic and bold.
- When a title or subtitle appears in ALL CAPS, transcribe it in Title Caps instead (according to the capitalization rules of your language for titles). CSS styles will convert the titles to all caps automatically. Other places where the titles are used require title caps rather than all caps.
- Punctuation (periods, commas, etc.) should usually be inside formatting elements (like <em> and <strong>), so it matches the formatting of the preceding word, but outside of hyperlinks (<a>).
- If you need to add paragraphs or move paragraphs around, be careful to preserve the HTML structure.
- Whenever a scripture or song is referenced, turn it into a hyperlink that directs to the song or scripture's URI (for example, “/scriptures/bofm/1-ne/3.7” or “/manual/hymns/the-morning-breaks”.
- Don't translate anything inside the angle brackets of an element tag (for example, HTML class names or alts).
- In most cases, you won't need to change image srcs.
- You can use the HTML code or manifest from equivalent English songbooks as a reference.
- Feel free to ask questions!