The project which started me on my way, and one of the first projects I completed.

For me this was so much more than a blog. It was the first I'd done a project in Svelte/Sapper beyond the Repl tutorials, the first project I'd done in any JS framework/library. It was the first time I managed to implement a theme colour switcher, the first time I'd configured Tailwind to my specifications and the first time I was able to display code properly using Prism, although it appears it's not in this incarnation - it must be on another version I have scattered on my laptop.

Having made websites on and off for around twenty years, coming back to it after a break of around four or five years and finding these amazing frameworks and libraries was revelatory for me. The last time I'd built a website I had ftp'ed it using Panic's Transmit, to a website hosted by Mediatemple, and I had probably used Zurb's Foundation as my css framework.

Anyway, back to the this project. As I mentioned in the first paragraph, for me a 'blog' is core webiste functionality. It's a content management system, albeit a very basic one, with dynamic routing and, if done correctly, blistering speed. These features are key to any website. This project was also the first time I had worked with Markdown as a means of storing information for a site. As a means of storing blog posts it's absolutely ideal for most people. No extra applications or websites to open, just hammer out an article in the text editor you currently use, save it, update your Github, and hey presto! You're live.

But ehat about if you want to write articles on the go? Well, this is where Forestry comes in. Forestry calls itself "an editor friendly interface over Git" and "a static CMS that commits". To you an dI what it does is connect to the markdown folder in your repository, you tell it the structure of your markdown files, and it then gives you an interface (on your phone if you like) to create new markdown files on the go. These are saved directly to your Git provider, so I you have it set up as I do, once you save a new markdown file this triggers a deployment in Vercel and thus the live site is updated.