Changelog

v2026.10.09

Fri, 09 Oct 2026 12:54:49 GMT

Website

I’ve been wanting a bookshelf page for a while now (inspired by the first one I’ve ever seen on a personal website https://photogabble.co.uk/books/) and I finally built a simple one.

My bookshelf retrieves records from my BookHive collection server-side on build time. I don’t expect this shelf to change often so I opted not to show the live/latest version of it.

Other changes include showing a relative time (e.g. Published 5 days ago) as the publication date for each blog post, then showing the actual date at the end of the post.

v2026.09.23

Wed, 23 Sep 2026 06:59:05 GMT

Website

I added a social share and copy link section under my blog posts for easier sharing. Currently only X (formerly Twitter), Bluesky, and Threads are in the Social Share and there’s a general purpose Copy Link button for all other platforms.

v2026.09.19

Sat, 19 Sep 2026 12:54:41 GMT

Website

I added link previews to bare links in my blog posts with remark-link-card-plus. Now links can be pretty.

I also added a Tip Jar / Support My Work banner at the bottom of the page. Completely optional of course but very much appreciated.

v2026.09.17

Thu, 17 Sep 2026 11:24:08 GMT

I should have done this earlier, but I have an RSS feed for each of my publications now!

v2026.09.07

Mon, 07 Sep 2026 07:17:40 GMT

Only one main thing really changed in this version: I added support for custom cover images for blog posts.

Previously, I generated Open Graph images for each blog post that also serves as the document’s coverImage. I still generate OG images for each blog post, but it can be overriden by a custom image defined at the Markdown frontmatter of the post.

I also have officially published my blog posts under Against the Dying Light publication to the Atmosphere!

v2026.09.06

Sun, 06 Sep 2026 15:16:42 GMT

Website

The whole thing has changed! I locked in and actually made something beyond “okay na ‘to”—it’s a Filipino expression that conveys the energy of “this is probably fine.”

On the homepage, I added a list of my five latest articles or writeups, followed by a feature section for Against the Dying Light which is a publication where I write under my pen name Rage—sometimes I also call the publication itself Rage because I agree it is quite a mouthful. And then there’s a short blurb about myself, and finally a list of my previous work experience.

The publication pages and entry pages have also changed a little bit, but I will probably polish this more over the next days. Oh, and I added a reading time metric for each article!

Internal tooling

Storybook

I added Storybook Astro to the project to be able to prototype designs much quicker and so I can have a playground for experimental designs or components in development that the site isn’t using just yet.

The setup was pretty straightforward, except for two things:

Styling with SCSS
Fonts

I did have to change the way I’m writing my styles if I want to write a story for an Astro component. Previously, in my .astro files I have a <style lang="scss"> for styles. This doesn’t work with Storybook Astro for some reason, although the documentation say it automatically injects styles (maybe only for vanilla CSS?). As a result, for any components I am developing via Storybook I need a separate Component.module.scss file for styling.

I also had to re-declare my @font-faces in a .storybook/preview.css file (it also imports my global.scss) because my font variables are not resolving into anything otherwise.

v2026.09.01

Tue, 01 Sep 2026 02:40:27 GMT

Website

I changed the header, navigation, and footer so that it follows the theme color instead of reverting it. I added links to my social.

The Table of Contents component now highlights which section is currently in view. It works for the most part, but in shorter write-ups like this one it has a tendency to only highlight the last intersection entry. I think it’s good enough for most scenarios in its use case.

I added the /tags/[tag] route to show all posts tagged with a certain tag. Each blog post will also contain a list of clickable tags (if it has any) above the headline.

I also finally added a sitemap and robots.txt to my website. Hooray?

Internal tooling

I fixed a small but terrible (and stupid) bug where my AT URIs start with at::// instead of at://. Don’t be like me.

I also added support for uploading a cover image blob before uploading a document referencing the blob. Currently, this automatically retrieves the PNG from the OG images folder in the dist output directory. This means at least npm run build has to be called before running any of my internal AT Proto scripts.

I also added a GitHub Action to run an AI PR Review every time a PR is opened. I’m using Robin with an OpenRouter free API key. The model only reviews the git diff, so it doesn’t always have the full context of the changes. It could be more useful with big PRs where changes are contextful, unlike one-off changes or bug fixes where the bug isn’t immediately apparent.

v2026.08.31

Mon, 31 Aug 2026 00:00:00 GMT

Website

I decided to use Sass instead of vanilla CSS because it afforded me some tooling that would be perfectly useful for this site’s theming and design system needs. I was particularly interested in not having to re-declare CSS variables for [data-theme="dark"] and @media (prefers-color-scheme: dark) every time a new theme token is added. Typography is much better with Sass too.

I also found out for the first time about CUBE CSS, which is already very similar to how I do my CSS initially but there are certain stylistic practices I wanted to adopt. I am slowly refactoring my styles to follow this methodology loosely.

I changed the base font from Space Grotesk to Inter, and from .ttf to .woff2. Subsequently, I changed my OpenGraph image renderer from Satori to Takumi because Satori does not support .woff2 fonts.

I added a Scroll to top button for convenience.

Oh, and I changed the header design again because I can’t decide on a proper header. Same goes with the footer. Both of these will very likely change in the future.

Internal tooling

I added support for parsing MDX to simple Markdown when publishing articles to the Atmosphere since I am using the at.markpub.markdown lexicon for my blog content and at the same time I needed custom components to present my content a certain way (like PulloutQuote similar to Substack’s Pullout Quote).

I removed rkey from the blog post frontmatter schema (I was previously manually adding an rkey every time the relevant blog post is published) and instead the update-document script retrieves this from the records file when needed. The records files gets automatically appended whenever a record is created.

v2026.08.26

Wed, 26 Aug 2026 14:55:47 GMT

Website

Added /changelog as a publication
Configured dynamic routing to cover any additional publication in the future
Added a Safari and Firefox workaround for scroll-state

Internal tooling

Added chalk, boxen, @inquirer/prompts, and yocto-spinner
Prettified scripts for publishing and updating AT Proto records
Added a script to create a boilerplate blog file in Markdown