Recent Writing - Mark Story

I recently saw the htmx 4 release announcement and wanted to give the upgrade a try.

Through most of 2025, I had been working on Sentry’s task platform.

I am a long term tmux + neovim enthusiast, and for the last 10 or so years, I’ve been using vim-plug to manage my vim dependencies.

In the last few months, I have been working on new project.

This site and a few other small sites are hosted on a small VPS.

I’ve recently been working quite a bit on a worker application in python.

Recently, I’ve been working on a system that needs to run tasks scheduled by either web requests, or other tasks.

As a long time open source maintainer, I occasionally have to modify pull requests made by contributors via forks.

My long running Dell XPS laptop recently died.

The front-end tools landscape is always evolving and changing.

This Easter I had some time to dedicate to working through the rustling exercises.

A few years back I made a post on how I work with PHP + SQLServer.

I’m working on an infrastructure application that provides a GRPC API to its clients.

I recently had to do some maintenance work on an old application hosted on the CakePHP server.

I wanted to share a new CakePHP plugin that provides feature flagging.

During the development of CakePHP, we also wanted to update migrations to be compatible.

As I use webcomponents more, I found myself wanting a way to define the HTML for webcomponents with a non-trivial amount of light DOM contents in a more reusable programatic way.

When re-building docket with htmx, I wanted to retain the confirm dialog experience I had with react.

I wanted to share a CSS and webcomponent layout that I’ve been pretty happy with in a few projects.

Webcomponents are starting to get more traction now that they are fully supported across browsers.

After updating docket to use htmx, I wanted to share my experience.