Concepts
Why LibreTimes Markdown works the way it does — its relation to CommonMark, statements and admonitions, rendering, books and refused HTML.
These pages explain the dialect rather than list it. Read one when a rule surprises you, or before a large piece of work, so that the rules read as consequences of a few decisions rather than as a list to remember.
| Page | The question it answers |
|---|---|
| LibreTimes Markdown and CommonMark | What is standard, what is added, what is changed, and what the dialect refuses |
| Statements and admonitions | Why a theorem and a warning are different things, and why only one of them is numbered |
| How a document is rendered | What happens between your source and the page, why maths is KaTeX, and why the preview is the page |
| How a book is structured | Chapters as pages, parts as navigation, and addresses that never move |
| HTML and security | Which raw HTML a document may hold, and why the rest is removed |
The decision behind most of them is one sentence: the markup says what a thing is, never how it looks. A theorem is marked as a theorem, and its bold label and italic body follow from that. A centred line is marked as centred, never as a margin of a certain width. Each page shows where the sentence leads.