Simple footnote reference:
This text has a footnote[1].
Multiple references in the same document:
Here is the first note[2] and here is the second note[3].
You can also reference notes again[2] later in the document.
Rich content in footnotes:
Complex concepts require detailed explanations[4].
They support most inline formatting!
According to recent studies[5], the usage of markup languages has increased significantly[6].
Other research[7] suggests similar trends in technical documentation.
The algorithm was first proposed by Smith et al.[8] and later improved by Johnson[9].
The Zolt language supports many features[10] including variables, loops, and calculations[11].
For more details, see the official documentation[12].
This software is provided "as is"[13] without warranty of any kind[14].
Usage is subject to terms of service[15] and privacy policy[16].
Styled footnote references:
Important information[17] and warnings[18].
Place all footnote definitions at the end:
This document covers various topics[19].
Details about topic 1[20].
Details about topic 2[21].
Reuse footnote references:
The concept of "zolt"[22] appears multiple times in this text.
Understanding the[22] philosophy is essential for effective usage.
The API endpoint uses JSON format[23] for data exchange[24].
Press Ctrl+S[25] to save your work.
For macOS users, use Cmd+S[26] instead.
The first markup language[27] was created in 1991[28].
Markdown[29] was later developed in 2004[30].
Footnotes are automatically numbered in order of appearance:
First reference[31], second reference[32], and third reference[33].
Note: The actual numbers in the output depend on the processing order.
Place footnote definitions at the end of sections or documents for better organization:
Content with footnotes[34].
More content with footnotes[35].
The syntax allows inline code[36] and even code blocks:
Multiple items can be listed[37]:
You can even include quotes[38]:
The study examines the effects of markup languages on documentation quality[5].
We analyzed 500 documents[39] across various domains[40].
Findings show significant improvement[41] in clarity and maintainability.
Recommendations for adoption[42] are provided.
Keep footnotes brief and focused[43].
Use descriptive footnote labels[44] rather than numbers[45].
Always test footnote rendering[46] to ensure proper linking.
This is the content of the footnote. ↩
This is the second explanatory note. ↩
Footnotes can contain formatted text, italics, and even: ↩
"Impact of Markup Languages" - International Journal of Documentation, 2026 ↩ ↩
Survey of 10,000 developers, showing 73% prefer Markdown-like syntaxes ↩
"Documentation Trends in Software Development" - Tech Communications Quarterly, 2026 ↩
Smith, J., et al. (2020). "Optimal Algorithms for Documentation Systems." *ACM Computing Surveys*. ↩
Johnson, M. (2022). "Enhanced Parsing Techniques." *IEEE Transactions on Software Engineering*. ↩
Core features include lists, tables, code blocks, and more. ↩
Advanced features enable dynamic content generation and complex document structures. ↩
Available at https://zolt.marmotz.dev/docs ↩
See MIT License for full details ↩
Excludes liability for damages, including but not limited to special, incidental, or consequential damages ↩
Full terms available at https://zolt.marmotz.dev/terms ↩
Privacy policy at https://zolt.marmotz.dev/privacy ↩
This note contains critical information. ↩
This is a warning message. ↩
This footnote introduces the document and its purpose. ↩
Additional information about topic 1, including references and further reading. ↩
Supplementary details for topic 2, with examples and use cases. ↩
Zolt represents a modern approach to documentation markup, combining simplicity with power. ↩ ↩
JavaScript Object Notation, a lightweight data-interchange format ↩
Other supported formats include XML and YAML ↩
Windows and Linux keyboard shortcut ↩
macOS keyboard shortcut ↩
HTML (HyperText Markup Language) ↩
Specifically, March 1991 ↩
By John Gruber ↩
Originally released as Perl script ↩
Content for the first footnote. ↩
Content for the second footnote. ↩
Content for the third footnote. ↩
Footnote for Chapter 1 ↩
Footnote for Chapter 2 ↩
Use backticks for inline code like `print()` and triple backticks for code blocks. ↩
↩"Footnotes are the perfect place for additional context without cluttering the main text." — Documentation Expert
250 Zolt documents and 250 traditional Markdown documents ↩
Including software, academia, and technical writing ↩
65% improvement in clarity, 45% reduction in maintenance time ↩
Specific adoption strategies and implementation guidelines ↩
Long footnotes defeat the purpose. Keep them short! ↩
Numbers can be confusing when there are many footnotes ↩
Click on footnote references to verify they link correctly to definitions ↩