Welcome! This is the a fresh start and the second rendition of this site. The initial plan was that it would build as my coding skills improved. I had done some html/css years ago, and thought it would be a good plan. The hosting of the website is handled by GitHub, so that made the backend super simple. Fast forward a few years and things are in a very different space.

Several life changes and the rise of AI and we are here.

So, back end has not changed, GitHub is still where this is hosted. However, I’ve done some vibe coding has taken place.

Part of the problem is my ability to focus on one task, and this blog is part of trying to help keep some focus on one aspect.

There are tons of platforms to choose from and for no particular reason, I picked Cursor. A free amount of credits was just enough for me to get this going. My prompt was pretty simple, look at the code I have already, make it smart and up to date and suggest a plan to make it easy for me to continue.

The output was this:

How the site works (plain language) Infinite Interest is a static site built with Jekyll — a tool that turns Markdown files and HTML templates into plain HTML/CSS. There’s no server-side app: each page is a file that gets generated at build time.

Publishing uses GitHub Pages with the github-pages Ruby gem (see your Gemfile). You push to Git; GitHub runs Jekyll and serves the built site. Your CNAME file points the custom domain infiniteinterest.uk at that GitHub Pages site.

Blog posts live in _posts/ as Markdown files named YYYY-MM-DD-post-title.md. Jekyll picks them up, applies your layouts (_layouts/), and your _config.yml sets things like pretty URLs, jekyll-feed (RSS at /feed.xml), and site metadata.

Locally, you run bundle install and bundle exec jekyll serve to preview at http://localhost:4000 before you push.

It’s look like a smart site that I can use and it’s very easy.

This leads me to an important point. I understand what the code is doing, just not good enough to make it from scratch. It’s a very small codebase, some some giant app or complicated workflow. This is why I’m happy to use the tools to do it. Unlikely to change, the next post will be about more building with tools. It’s really exciting that I can get idea built, that realistically don’t matter, nothing critical resting on it. Very different from work, where I use tools for more research and hunting down where settings have moved to.

That’s going to wrap this one up. The next post is going to be about another website I’m building, something silly and fun but hosted in the home lab.

More notes from the lab next time - pirranasaurus