The article component atlas
Every supported article element in one place: typography, lists, figures, tables, code, disclosures, footnotes, and related reading.
A complete set of building blocks
This is an article-format showcase. The people, observations, and values below are illustrative; this page does not report an Abel experiment or a model benchmark.1
Each section demonstrates a different part of the current article format. A writer can keep using Markdown, while a designer can review the same kind of element across every article.
For a continuous reading experience, open From observation to intervention. To inspect individual elements, use the contents list on this page.
Paragraphs, emphasis, and inline code
A paragraph can include a strong conclusion, an aside with a different voice, an earlier interpretation, and a precise identifier such as intervention_set. These can also be combined: an important qualification, or a link with emphasis.
A deliberate line break keeps two lines together:
The second line remains part of this paragraph.
Long identifiers should wrap in prose: a_descriptive_identifier_for_an_observation_window_that_needs_to_remain_readable_on_a_small_screen.
中文也可以出现在正文中:一个清晰的问题,一组可检查的证据,以及一段解释。English and 中文 can share a paragraph without requiring an image of the text.
A heading hierarchy
The article title is the only H1. Sections use H2, and subsections use H3. Both appear in the contents list.
A fourth-level heading
Use this level to introduce one part of a subsection. Its smaller size keeps the reading hierarchy clear.
A fifth-level heading
A deeper note can still have a semantic heading without competing with the main sections.
A sixth-level heading
This is the smallest supported heading level. It remains part of the document hierarchy and stays out of the main contents list.
Lists with different jobs
Unordered and nested lists
- Start with a question.
- Gather evidence.
- Record the observation window.
- Keep the source and its context together.
- Note which assumptions were checked.
- Explain what changed your interpretation.
Ordered and mixed lists
- Define the question.
- Describe the comparison.
- Say what stays fixed.
- Say what changes.
- Read the evidence before writing the conclusion.
An ordered list can also continue from a later number:
- Review the limitations.
- Share the article for feedback.
- Revisit it when there is new evidence.
A read-only review checklist
These checkboxes demonstrate a static checklist. A reader cannot edit the source by clicking them.
Quotations and supporting context
A figure is most useful when the reader knows what to look for before seeing it.
A second paragraph can extend the same thought without becoming a new block.
A nested quotation can distinguish a question from its response:
Review question: What would change this interpretation?
Example response: A different observation window, an unmeasured influence, or evidence that the proposed change cannot be applied consistently.
Links and references
A link can point to an external reference, the article list, a figure in this article, or a bundled text file.
Reference-style links work as well: read the renderer documentation, then return to the original format example. A link remains a link when its label is long enough to wrap onto another line on a narrow display.
Images and figures
A standard Markdown image
The following uses ordinary image syntax. Its alt text describes the picture but does not become a visible caption.
A figure with a caption and reference
This separate figure has a visible caption and its own anchor. Follow the figure reference to return to it later.
Tables, alignment, and overflow
A compact comparison
The source markers define left, center, and right alignment. Emphasis and inline code can appear inside a cell.
| Element | Representation | Example count |
|---|---|---|
| Observation | x | 120 |
| Intervention | do(x) | 3 |
| Review note | Context | 8 |
The numbers are layout examples only.2
A wider table
This table intentionally has enough columns to need horizontal scrolling on a phone. The scroll stays inside the table area.
| Review stage | Question | Input format | Supporting material | Reviewer | Status |
|---|---|---|---|---|---|
| Framing | What are we trying to understand? | Markdown | A short problem statement | Editorial example | Ready |
| Evidence | Can the reader inspect the reasoning? | Table + figure | Sources, assumptions, and illustrative observations | Research example | In review |
| Presentation | Does the article stay readable on a small screen? | HTML | Image descriptions, code blocks, and contents links | Design example | Open |
Code in several forms
All code and output here is static article content. The page does not run the snippets.
A named Python fence
questions = ["What changed?", "What stayed fixed?", "What is uncertain?"]
for index, question in enumerate(questions, start=1):
print(f"{index}. {question}")
TypeScript and JSON
type ReviewNote = {
question: string;
status: "draft" | "reviewed";
};
const note: ReviewNote = {
question: "What evidence would change our interpretation?",
status: "draft",
};
{
"kind": "format-example",
"observations": 3,
"measured_result": false
}
Shell text and a fence without a language
# Example commands for a local article preview.
npm run content:check
npm run dev -- --port 43187
No language was specified for this fence.
Indentation is preserved.
Long source lines stay intact and can scroll within the code block: question -> observation -> comparison -> qualification -> explanation -> next question.
A source-and-output pair
questions = ["What changed?", "What stayed fixed?", "What is uncertain?"]
print(f"Review questions: {len(questions)}")
Review questions: 3
A bundled source file
These blocks read the files that travel with this article. The output is recorded text supplied by the author.
questions = ["What changed?", "What stayed fixed?", "What is uncertain?"]
print(f"Review questions: {len(questions)}")
Review questions: 3
A language without highlighting
An unknown language falls back to readable text and displays a notice. The original content remains visible.
Syntax highlighting is unavailable for example-dsl; shown as plain text.
question "What changed?"
observe "before"
compare "after"
keep "uncertainty visible"
Expandable supporting material
Open a short supporting note
This is a paragraph inside a disclosure. It can contain emphasis, inline_code, and a reference to the figure.
- The summary remains visible when the note is closed.
- The contents become available when it is opened.
- The disclosure works with a keyboard.
Open a longer note with a table and code
Inside the supporting note
A supplementary section can keep a detailed comparison close to the main explanation.
| Check | Example |
|---|---|
| Input | Three example questions |
| Output | A count supplied as static text |
assert len(["question", "evidence", "explanation"]) == 3
A supporting note still uses the same paragraph, table, quotation, and code components.
Repeated headings and footnotes
A recurring question
The first occurrence gets its own section anchor. A footnote can add background without interrupting the main paragraph.3
A recurring question
The second occurrence receives a different anchor, so both sections remain reachable from the contents list. The same footnote can be referenced again.3
A divider separates the closing note. This article demonstrates all element types currently supported by the article system; mathematical notation, video embeds, and interactive chart/demo blocks are not part of this version.
Footnotes
-
This page is a writing and design sample. The names identify example editorial roles and do not assign research authorship. ↩
-
All counts on this page are invented layout values and must not be read as a benchmark. ↩
-
A footnote can contain more than one paragraph.
The second paragraph provides additional context while the backlink returns to the original reference. ↩ ↩2