About this Blog
I’ve just about finished setting up this website using Astro, so I can use it for my blog.
What’s the goal?
In short, to write more and put it out there.
I want to get better at writing, at sharing my work, so I’m doing what I can to reduce the friction in that process.
Why Astro?
It started out as curiousity. Every so often, I tend to get inspired to revamp my personal website. I change up the styling, sometimes the technology, but never really get around to writing more. I’ve done this a few times, written a few posts, but this time, I want to just focus on writing. I spend most of my time in Neovim, and so I wanted to be able to write within it as well.
I wanted a setup where I could:
- Write in markdown
- Have the markdown converted to webpages automatically, as part of build
- Have an entirely static site that runs without javascript
Astro seemed like a good bet for this, and closer to the tools I’ve used before, such as React. To be fair, the initial idea I was looking at, was a script that would convert markdown files to HTML to display in my earlier site setup, which was entirely static.
Styling with Tailwind
Tailwind has been a styling constant for me, for a while now, and I’ve thought about why I like it. In my first try at doing this, I realised what I really liked about it. It’s the same thing that eventually frustrates me about it too.
My styles live in the html code, and not in a separate CSS file.
This makes it so that you can get an overview of styling with often a single glance.
But, I’ll admit, for a static website generated from markdown files, most of my styling work has been to undo the normalisation of styles that Tailwind does.
Tailwind Typography
This nifty little package seems to have solved the majority of the styling issues, once I’d addressed a minor hiccup with max width.
It’s worth a look, if you’re having similar problems with tailwind’s normalisation.