Formatting Guide: Writing Articles for Scripture in Depth
Last updated
This is a sample article included with the site. It doubles as a style reference — open src/content/blog/formatting-guide.mdx in VS Code to see the source for everything below. Delete it (or set draft: true) before launch.
Headings
The article title is the page’s only H1. Inside an article, start at ## (H2) and work down:
Heading level 2
Heading level 3
Heading level 4
H2 and H3 headings appear in the table of contents. It is shown automatically when a post has four or more of them; add toc: true or toc: false to the frontmatter to override.
Inline text
Paragraphs use a serif face for comfortable long-form reading. You can write in bold, in italics, or in both. Use highlighted text sparingly for a point you want to stand out. Titles of works, such as Augustine’s Confessions, go in italics. Inline code is available but rarely needed.
For the divine name rendered in small capitals, write <span class="sc">Lord</span>: “The Lord is my shepherd.”
Greek and Hebrew can be typed directly: λόγος, ὁμοούσιος, בְּרֵאשִׁית.
Links look like this link to the Christian Classics Ethereal Library.
Quotations
Plain Markdown blockquotes
Any line starting with > becomes a blockquote. This works in both .md and .mdx files:
Thou movest us to delight in praising Thee; for Thou hast formed us for Thyself, and our hearts are restless till they find rest in Thee.
— Augustine, Confessions 1.1 (trans. J. G. Pilkington, NPNF¹ 1)
Scripture component
In .mdx files you can use the Scripture component, which adds a consistent reference line. Leave blank lines around the quoted text:
The Lord is my shepherd; I shall not want.
Patristic component
The Patristic component works the same way for the Fathers and other historical sources. Only author is required; work, locator, translation and href are optional.
Thou movest us to delight in praising Thee; for Thou hast formed us for Thyself, and our hearts are restless till they find rest in Thee.
Lists
Bulleted list:
- Biblical exegesis
- Patristics
- Apostolic Fathers
- Apologists
- Historical theology
Numbered list:
- Read the passage in its literary context.
- Consult the earliest interpreters.
- Trace the reception of the text through the councils.
Footnotes
Add a footnote marker with [^1] (or any label, like [^irenaeus]) and define the note anywhere in the file.1 Notes are numbered automatically in the order they appear and collected under a Notes heading at the end of the article, each with a link back to the text.2
Tables
| Council | Year | Principal question |
|---|---|---|
| Nicaea I | 325 | The divinity of the Son (against Arius) |
| Constantinople I | 381 | The divinity of the Holy Spirit; revision of the Nicene creed |
| Ephesus | 431 | The unity of Christ; Mary as Theotokos (against Nestorius) |
| Chalcedon | 451 | One person in two natures |
On narrow screens, wide tables scroll sideways rather than breaking the layout.
Horizontal dividers
Three hyphens on their own line create a section break:
That is all. Everything else is ordinary Markdown.
Notes
-
This is a footnote. Footnotes can contain formatting and links. ↩
-
Footnotes may also run to several sentences, which is useful for bibliographic detail. For example: Philip Schaff and Henry Wace, eds., Nicene and Post-Nicene Fathers, Second Series, vol. 4, Athanasius: Select Works and Letters (New York: Christian Literature Company, 1892). ↩