Move posts from Wordpress to physical markdown

This commit is contained in:
Lewis Dale committed 2023-12-26 14:35:09 +00:00
1 parent e828f9f590
commit c8c5981bd3
147 files changed
+6219 -98

No files matched your search

+33
View File
@@ -0,0 +1,33 @@
---
title: "A new blog"
date: 2021-12-17T00:00:00
slug: a-new-blog
---
It’s been a long time since I’ve had an actively-maintained personal website/blog, but I got a spurt of inspiration after seeing a few other recently-revamped blogs. What better way to celebrate the end of the year than with… a blog?
My intention is to try and write a post on here relatively frequently, but we’ll see how that goes as I’m quite out of practice.
## [Tech stack](https://lewisdale.dev/post/a-new-blog/#tech-stack)
I wanted this website to achieve three things: be of my own design, be easy to update, and be accessible. To that end, I chose a relatively simple tech stack:
- [Eleventy](https://11ty.dev/)
- HTML
- CSS
And that’s… just about it. Eleventy gives me more than enough functionality to write simple blog posts in Markdown, convert them to HTML, and display them on a page.
I did start out using [Tailwind](https://tailwindcss.com/), but after a little while and seeing some of the recent discourse around it, I decided I wanted to write all the styles myself from scratch. It was pretty easy to remove Tailwind from the stack, as I hadn’t done too much work on it to begin with. Plus, it meant that I could get rid of PostCSS, which was giving me a headache when trying to serve both PostCSS and Eleventy at the same time.
I deployed the site using [Netlify](https://netlify.app/). It was my first time using it, and to be honest I’m pretty impressed by how quickly I was able to get things up and running. It took maybe 3 minutes from signing up to getting a version of the site deployed (pointing the domain took longer thanks to pesky DNS propagation times).
## [Accessibility and Performance](https://lewisdale.dev/post/a-new-blog/#accessibility-and-performance)
I wanted some assurance that my website would be accessible, so I regularly tested my pages with [axe DevTools](https://www.deque.com/axe/devtools/) and Lighthouse in Chrome.
At the time of writing, there are no accessibility issues reported by Axe or Lighthouse, so that’s a win!
![Congratulations! Found 0 issues automatically on the page](./src/images/axe-clean-output.png)
If anybody reading this does in fact spot or experience an accessibility issue, [please send me a DM or tweet on Twitter](https://twitter.com/LewisDaleUK).
@@ -0,0 +1,29 @@
---
title: "Year retrospective"
date: 2021-12-28T00:00:00
slug: year-retrospective
---
The last year has been a wild one, with some real highs and lows, so I thought I’d do a short retro on the year and outline some (fairly vague) goals for the next year.
2021 has been both a very short and *extremely* long year. Short, because the first 10 or so weeks of the year I was on parental leave after the birth of my daughter at the end of December '20 and so those first few months are mostly just a blur that doesn’t count. Long, because it’s been exhausting. I’d argue that 2020 was less exhausting - the COVID and remote working situation was stressful, and the period of adjustment made working effectively quite difficult. However 2021 saw many of those same struggles continued, but that was coupled with a degree of malaise from almost everybody I encountered - people were *tired* and it really started to show.
In addition to that, some health scares and struggles within my family made it difficult for me to take a break throughout the year - the only significant holiday I took was cancelled as my daughter was hospitalised. On top of the general exhaustion that comes from raising a newborn (and one that is apparently capable of going without sleep). The result was that by around July, I burned out. Hard. It impacted my work, I pulled myself off the project I was working on, and eventually ended up leaving the company I was working at and took a short break. It mostly worked - I feel much better now than I did then, at least, but recurring burnout is something I have to watch for.
## [Some wins](https://lewisdale.dev/post/year-retrospective/#some-wins)
But it’s not all been doom-and-gloom! I’ve had some great wins this year that I should definitely celebrate.
To start with, I decided to leave a job that honestly wasn’t a good fit. I went into the company with a set of expectations, and in hindsight I think they were in conflict with the expectations that the company had for me. The result being that I was struggling to progress with my career and succeed; recognising that and deciding to leave was definitely the right decision.
Since then, I’ve decided to start freelancing; I like being able to work in lots of different problem spaces, and this definitely gives me the agency and the freedom to do what I enjoy most. It’s been pretty good to begin with - I’ve got some steady work in now, but I’d love to get some more variety in there.
Somebody that I had been helping to mentor was recently successful in applying for a junior engineering role, and I am absolutely overjoyed for them. I find mentoring really rewarding, and it’s always nice to see people achieve that first step into a software engineering career.
## [Goals for 2022](https://lewisdale.dev/post/year-retrospective/#goals-for-2022)
My (vague) goals for the next year are:
- Take some time off
- Try and build my freelance business further
- I’ve got some ideas for products I would like to also build on the side