Source files for book chapters contain hyperlinks that should actually be footnotes. Before we release any future editions, we should convert all those hyperlinks to footnotes. Doing this would save an incredible amount of time in production.
Instructions
Markdown syntax for footnotes is (surprise!) very simple. A footnote has two parts: the in-text part and the at-the-end part.
At the end of a sentence with a footnote, you add the following text:
[^unique-identifier]
Where unique-identifier is a brief (one or two words) that identify that footnote and distinguish it from all others in the whole book (that part is important).
Then, at the end of the document, you add:
[^unique-identifier]: The text of the footnote.
And that's it! When the chapter renders, it'll contain sequential footnotes all linked to their appropriate references.
I am happy to participate in this effort but wanted to be sure to open up the work to others, too, as this sort of task is something a newcomer might also complete to become more familiar with our materials (and make a huge impact on a core project right away!).
Source files for book chapters contain hyperlinks that should actually be footnotes. Before we release any future editions, we should convert all those hyperlinks to footnotes. Doing this would save an incredible amount of time in production.
Instructions
Markdown syntax for footnotes is (surprise!) very simple. A footnote has two parts: the in-text part and the at-the-end part.
At the end of a sentence with a footnote, you add the following text:
[^unique-identifier]
Where
unique-identifier
is a brief (one or two words) that identify that footnote and distinguish it from all others in the whole book (that part is important).Then, at the end of the document, you add:
[^unique-identifier]: The text of the footnote.
And that's it! When the chapter renders, it'll contain sequential footnotes all linked to their appropriate references.
Notes