Style Guide & Feature Test

This post exercises every feature and formatting element the blog supports. Use it to verify rendering after changes, and as the reference for the canonical post style. The headings below also demonstrate the fixed heading scale.

Heading Level 2 (section)

Top-level post sections use ##. Body text is justified, monospace, and wraps normally. This sentence exists to show how a longer paragraph flows across the column so that justification, line-height, and wrapping can be eyeballed at a glance without hunting through a real post.

Heading Level 3 (subsection)

Subsections use ###.

Heading Level 4 (minor)

Minor points use ####. Avoid going deeper than h4.

Inline Elements

Regular, bold, italic, strikethrough, inline code, a link, and a keyboard key like Ctrl + C. A footnote reference sits here.¹

GitHub-style Alerts

Useful information the reader should notice even when skimming.

A helpful suggestion for doing things better.

Key information the reader needs to know to achieve their goal.

Urgent info that needs immediate reader attention to avoid problems.

Advises about risks or negative outcomes of certain actions.

A plain blockquote, for contrast:

“Given enough eyeballs, all bugs are shallow.” — Linus’s Law

Code Blocks

Fenced blocks get a language label and a copy button automatically. First-line magic comments (any comment style, stripped from the copied text) enable extras: filename: x shows a name in the bar, linenos adds a numbered gutter, and highlight: 3,7-9 numbers the lines and highlights the listed ones. ASCII diagrams (text/ascii) show no label.

# enumerate listening sockets
ss -tlnp | grep -i sshd

// filename: loader.c
void load_file(char *name) {
    char path[100];
    snprintf(path, sizeof(path), "/var/data/%s", name);  // bounded
}

// highlight: 4
void load_file(char *name) {
    char path[100];
    snprintf(path, sizeof(path), "/var/data/%s", name);  // bounded copy
    system(path);                                        // the bug we point at
}

def reward(mitigated, fp, dt):
    return 1.0 * mitigated - 0.5 * fp - 0.1 * dt

Inline code stays unstyled by the bar.

Tables

Tool	Type	Size	F1
Ours	Reasoning	7B	0.66
o3	Commercial	N/A	0.60
CodeQL	Static analysis	N/A	0.30

Lists

Unordered:

• first item
• second item
  • nested item

Ordered:

1. step one
2. step two
3. step three

Task list:

• implement feature
• write the test
• ship it

Math

Inline math such as $E = mc^2$ and $\pi^* = \arg\max_\pi V(\pi)$ renders inline. Display math:

\[R_t = \alpha \cdot \mathbb{1}_{\text{hit}} - \beta \cdot \mathbb{1}_{\text{fp}} - \delta \cdot \Delta t\]

Diagrams (Mermaid)

Diagram 1 — A minimal build-time-rendered flowchart (feature demo).

Images

Images are centered with a dashed border; wrap with a caption when helpful.

Figure 1: a sample image (click to zoom).

Horizontal Rule

A horizontal rule (use sparingly):

---

Definition List

Term

A definition for the term above.

KASAN

Kernel Address Sanitizer — fast memory-corruption detector.

References

1. Author, A. (2026). Some Relevant Paper Title. Venue.
2. Author, B. (2025). Another Reference. arXiv:2500.00000.

1. Footnotes render at the bottom of the post. ↩