The site now supports web mentions. I setup a go service to handle incoming and outgoing mentions as well as discovery. The local Laravel api will fetch the incoming and send outgoing after a deployment. Keeps everything nice and static. If you blog doesn't support web mentions, you should consider adding them.
The idea for a now page is fairly old, and although I can't recall exactly when or where I saw it, I was recently reintroduced to the concept of a 'Now' Page by Roy Lindauer after he added one to his personal site. A Now page is a page on a personal site that tells you what tells you what the site owner is focused on at this point in their life.
I liked the idea so much that I have added a Now page to my own site. In addition to the Now page, I have added a Past page as well to serve as an archive of past now pages. If your personal site doesn't have a Now page, you should consider adding one.
I've added support for RSS and Atom feeds. Its a shame that most people don't use RSS readers anymore, but its a great feature to keep around. I've also added a basic service worker. It enables offline browsing of the site and handles fine gain caching of pages, fonts, images, js and css. The site should feel a bit more zippy.
I've done a bit of work on the site over the long weekend. Got around to a basic theme instead of plain text styles. It support both light and dark styles. It's still simple, but improves the readability. The front-end now supports markdown. Markdown has been on my list of things to-do for awhile. It make formatting easy, and also takes care of links, code blocks and an common way to do image embeds.
Along with markdown I have built out an actual back-end with a post editor. The back-end is also nextjs but it runs locally and talks to the laravel api that also runs locally. The front-end is nextjs but statically exported and pulls posts and pages from the api when building. Another item is media uploads (and embeds thanks to markdown). It gets uploaded to the api from the back-end and then the front-end copies them at build time.
I wanted a way to do comments without switching from a static site. There are a few ways to do that using javascript and 3rd party services, but I had the idea to use Mastodon instead. The way it works is if comments are enabled for a post, at build time it will trigger my @blog bot to share a post. From there I can either boost or quote it to share it with the people that follow @bhhaskin. People can then comment/reply to the post and the next time I build the site it will be pulled down by the api. It does mean there is a lag between commenting on the Mastodon post and when they show up on the blog post, but it is a good trade off.