Typography Test Page

This page exists for one reason: to make every content shape look intentional.

If this page looks clean, every normal post will look clean - because it includes the full set of things you actually write: headings, links, lists, quotes, code, dividers, tables, and a couple of “awkward” edge cases.

A normal paragraph should be Georgia. A heading should be Inter. Links should feel consistent and calm.

---

Baseline paragraphs and rhythm

They say investing is a loser’s game.

It’s not about the winners you hit.
It’s about the losers you avoid.

The concept originates from Charles Ellis, who described amateur investing as a game of minimizing unforced errors.

Here’s a paragraph with a link to test colour and hover: Charles Ellis. And here’s an inline link to test wrapping: expected value.

And here’s some bold text, some italics, and a bit of bold + italic to see if any font rules leak.

---

A section break with intent

A well-structured life protects against downside. You design your environment to reduce exposure to temptation. You manage your attention. You simplify. You stay in the game.

Ask yourself:

• How many distractions showed up today?
• How many impulses did you notice, but not act on?
• How many little losses did you avoid?

Each one is a quiet victory. Not dramatic. Not shareable. But real.

Nested list and spacing

• Risk management
  • Position sizing
  • Time horizon
  • Liquidity
• Process
  • Review
  • Rules
  • Checklists

And a numbered list, because it often behaves differently:

1. Avoid ruin
2. Stay solvent
3. Let time do the heavy lifting

---

Blockquotes, pullquotes, and commentary spacing

Here’s the classic probability example:

Flip a coin. Heads, you double your net worth. Tails, you lose everything.
EV is zero - but the downside is fatal. You’ve taken on ruin risk, a violation of the first principle of compounding: don’t get knocked out of the game.

A paragraph immediately after a blockquote often looks weird if the margins are off. This sentence is here to test that.

Here’s a shorter quote to test a single-line blockquote:

Time averages diverge from ensemble averages if ruin is possible.

And here’s a quote with emphasis:

“Don’t be the six-foot man who drowned in the river that was five feet deep on average.”

---

Inline code, code blocks, and readability

Inline code should look like a quiet annotation: expected_value = Σ p(x) * x.

A short code block:

def expected_value(outcomes):
    return sum(p * x for (p, x) in outcomes)

coin_flip = [(0.5, 2.0), (0.5, 0.0)]
print(expected_value(coin_flip))