vite_logo zod-logo

Astro has a huge amount of hype in the developer community at the moment.

I have been thinking of redesigning my blog for a while & maybe even moving away from Gatsby.

Is it possible to completely replace Gatsby with Astro & keep the same features?

To try to answer this why not move this blog to Astro ?
(lets also use tailwind instead of bulma)

Init Astro Blog #

I looked at some templates but wanted to understand more how Astro worked so used the basic default blog template.

pnpm create astro@latest -- --template blog

I first tried in Astro 1.9.0 & didn't really like the structure of posts etc.

The project sort of got left for a while until Astro 2.0 came out with collections & type safety.
Suddenly Astro looked like it would be a lot easier to structure & use for blogs.

Linting Code #

The default code seems to be all over the place in terms of formatting.
There is a mix of tabs & spaces.

Install ESLint, Prettier & Astro plugins.

pnpm install -D eslint eslint-plugin-astro @typescript-eslint/parser astro-eslint-parser
pnpm install -D prettier eslint-config-prettier eslint-plugin-prettier prettier-plugin-tailwindcss prettier-plugin-astro

Setup .eslintrc.cjs with override for .astro files to use astro-eslint-parser.

  overrides: [
      files: ['*.astro'],
      parser: 'astro-eslint-parser',
      parserOptions: {
        parser: '@typescript-eslint/parser',
        extraFileExtensions: ['.astro'],
      rules: {},

Prettier has a bug with pnpm where it does not find plugins so it requires adding the plugins to the .prettierrc.cjs directly.

  plugins: [
  pluginSearchDirs: false,
  overrides: [
      files: '**/*astro',
      options: {
        parser: 'astro',

Modifying Slug #

The first thing I looked at was how slug was generated.
By default slug is generated using filename (makes sense for small sites).

First modification was to generate slug using title from frontmatter.
This involved creating a slugify function to call when generating slug for links.

-    params: { slug: post.slug },
+    params: { slug: createSlug( },

📝 Generating Slug From Title In Astro

I then compared this to my Gatsby setup and thought why not also generate slug using the published date of the post.
This involved using moment for a date formatting function.

-    params: { slug: createSlug( },
+    params: {
+      slug:
+        slugDate( +
+        createSlug(,
+    },

📝 Generating Slug Using Published Date In Astro

This also meant I could move src/pages/blog/[...slug].astro to src/pages/[...slug].astro as all blog posts will have unique slugs.

Newpost Creation #

I moved my newpost script from Gatsby to Astro as an easy way to create posts.

📝 Gatsby New Post CLI Script - Jul 6, 2019

The script uses readline and fs which are both core nodejs functions.

const fs = require('fs')
const readline = require('readline')
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,

Pagination #

The default blog posts feed was at /blog but I wanted to move this to /.
I decided to seperate the feed to /posts & have the most recent posts on the front page.

Pagination in Astro is really easy as there is a function which pretty much does all the work.

Routing 🚀 Astro Documentation

The only problem I had was related to types which was fixed by setting posts to CollectionEntry<'blog'> & typeof posts when mapping over the array.

interface Props {
  posts: CollectionEntry<'blog'>
} typeof posts) => (

Syndication Feed Generation #

I wanted to generate an atom feed using an excerpt of the blog post content.

There are two problems with this:

RSS 🚀 Astro Documentation

RSS v Atom #

Looking into syndication feed generation it's like everyone is using rss 2.0 instead of atom.
Atom seems to fit better with syndication & seems to have more features.

Comparison of RSS and Atom Web Feed Formats

Screenshots #

This is what I have so far, the site looks similar to the Gatsby blog.





A lot of time was spent on CSS & there were a few problems with tailwindcss.

Thoughts So Far #

Using Astro 2.0 changed my view, previously I only really used Astro for simplistic sites where content doesn't really change but with the addition of content collections & type schemas it really is nice to work with.

Astro Blog - Introducing Astro 2.0

I started porting the site over to Astro as a weekend project but ended up working on it in my spare time in the week as it was so interesting to work with.

Things I like:

I have not used any advanced features like islands architecture yet.
This will be a useful feature for adding things like dynamic comment components.

Astro Islands 🚀 Astro Documentation

It still feels like I've only scratched the surface so far.

Notes #

Trying to recreate my blog using a basic template was much more interesting than just downloading a premade template as I feel like I had to learn different things about Astro I would have otherwise never touched.

I first used UnoCSS which was so much faster than tailwind + postcss but I just could not get darkmode themed properly (the default darkmode did work using default colors).

Source #

The source for my astro blog is available on github.