Building With Astro

Every framework has a personality.

Some encourage ambitious web applications filled with interactions, state management, and client-side rendering. Others focus on speed, flexibility, or developer experience.

Astro begins with a simpler question.

How little JavaScript does this page actually need?

For a website built around writing, that question changes almost everything.

Starting with content

Many modern websites begin with components.

Navigation.

Buttons.

Cards.

Layouts.

Only after those pieces are assembled does the content find somewhere to live.

Astro quietly reverses that relationship.

Content comes first.

A Markdown file is already a complete document. It has a title, a publication date, an introduction, and a body. The framework simply provides a comfortable way to present it.

That may sound like a subtle distinction, but it influences how a project grows over time.

Instead of asking, “What interface should we build next?”

You begin asking, “What would be worth publishing?”

HTML deserves more credit

The web worked remarkably well before JavaScript became its default language.

Articles loaded instantly.

Links behaved predictably.

Search engines understood pages without difficulty.

Browsers rendered documents using standards that have lasted for decades.

Astro embraces those strengths instead of replacing them.

Most pages can be delivered as plain HTML, with JavaScript added only where it’s genuinely useful.

That approach feels refreshingly honest.

A document should first be a document.

Performance as a byproduct

It’s common to talk about performance in terms of scores and benchmarks.

Faster loading.

Smaller bundles.

Higher Lighthouse ratings.

Those numbers certainly matter, but they’re only measurements.

The real benefit is how the website feels.

A page appears almost immediately.

The browser doesn’t hesitate before displaying text.

Scrolling remains smooth because there is very little happening behind the scenes.

Readers rarely congratulate a fast website.

They simply continue reading.

Content Collections

One of Astro’s most thoughtful features is Content Collections.

Rather than scattering Markdown files throughout a project, collections introduce a small amount of structure without becoming restrictive.

An essay belongs with other essays.

Projects belong together.

Notes remain separate from photography.

Each collection can define its own schema, ensuring that every document contains the information it needs.

Titles.

Dates.

Categories.

Descriptions.

Images.

A missing field becomes an error rather than a surprise discovered after deployment.

The result is confidence.

As a website grows from ten articles to several hundred, consistency becomes almost effortless.

Familiar tools

One of Astro’s quiet strengths is how little it asks you to learn.

If you’ve written Markdown before, you’re already productive.

If you know HTML and CSS, most templates feel immediately understandable.

You don’t need to adopt a completely different mental model before publishing your first article.

The framework respects existing knowledge.

That makes it approachable not only for experienced developers but also for writers and designers who enjoy understanding the tools they use.

Choosing simplicity

Technology has a habit of accumulating layers.

Each solves a legitimate problem.

Eventually those solutions introduce problems of their own.

Astro feels like a conscious attempt to pause that cycle.

Instead of assuming every page requires hydration, client-side routing, and reactive state, it asks whether those features are actually necessary.

Sometimes they are.

Often they aren’t.

Removing unnecessary complexity is just as valuable as adding useful functionality.

A foundation rather than a platform

Still is intentionally opinionated, but not rigid.

Its layouts, typography, and organization represent one possible way of publishing thoughtful writing.

Astro makes changing those decisions remarkably straightforward.

Replace the homepage.

Create entirely new collections.

Introduce custom components.

Remove features you don’t need.

Nothing feels locked away behind abstractions.

The project remains understandable because its foundation remains small.

Writing instead of configuring

Perhaps the greatest compliment a framework can receive is becoming forgettable.

After the initial setup, it fades into the background.

You stop thinking about configuration files and build pipelines.

You begin thinking about essays.

Photography.

Ideas.

Things worth sharing.

Astro reaches that point surprisingly quickly.

It becomes a tool rather than a destination.

Looking ahead

The web will continue changing.

New frameworks will appear.

Rendering strategies will evolve.

Development workflows will become more sophisticated.

That’s healthy.

Progress has always been part of the web’s story.

But regardless of how the tools change, one thing remains remarkably consistent.

People still arrive hoping to read something meaningful.

Astro provides an excellent foundation for building that kind of website—not because it tries to reinvent publishing, but because it quietly gets out of the way.

And for a theme like Still, that’s exactly the point.