← Exploration
Exploration

Hello world

#meta #test
Compass rose with scattered exploration points

So this is the first post. Nothing groundbreaking, just making sure everything renders the way it should. Consider it a typography stress test more than actual content.

Headings

The blog uses Montserrat for headings and Roboto for body text. This section exists purely to verify that the type hierarchy looks right across different heading levels.

A smaller heading

Third-level headings should be visually distinct from second-level ones without screaming for attention. If you can tell them apart at a glance, the scale is working.

Paragraphs and inline formatting

Regular paragraph text is set at 18px with generous line-height. Long enough lines to test the max-width: 65ch constraint that keeps things readable. If you are reading this on a wide monitor and the text is not stretching edge to edge, that constraint is doing its job.

You can use bold text for emphasis and italic text when you want something slightly softer. Inline code spans should stand out with a subtle background without breaking the reading flow.

Lists

Things that work well as unordered lists:

  • Grocery items
  • Reasons to rewrite something from scratch (usually bad reasons)
  • Bands you keep meaning to listen to

Things that benefit from order:

  1. Read the error message
  2. Read it again, slower this time
  3. Actually fix the problem instead of guessing

Blockquotes

The best code is no code at all. Every new line of code you willingly bring into the world is code that has to be debugged, code that has to be read and understood, code that has to be supported.

That one gets attributed to Jeff Atwood. Whether he actually said it or was paraphrasing someone else, the point holds up.

Code blocks

Here is a quick function that does very little:

function greet(name: string): string {
  return `hello, ${name}`;
}

const message = greet('world');
console.log(message);

The code block should have a visible border, a slightly different background from the page, and handle horizontal overflow if the lines get long enough.

Images

You can include images in posts by adding a heroImage field in the frontmatter, or inline with standard markdown. Here is the exploration hero image inline:

Compass rose with scattered exploration points

Place image files in the public/images/ directory and reference them with ![Alt text](/images/filename.png).

You can visit the Astro docs if you want to understand how this site is built. Links are underlined by default with a small offset so they do not collide with descenders.

That covers the main typography elements. If everything above looks intentional rather than broken, the blog is working.