January 22, 2025

This is the first post for my latest Web site. I've had a fair amount of thoughts simmering recently, which will be covered over time. One of the most immediate notes is that the format of the site has changed to reflect a daily(ish) journal which will be used to track work as it happens (as time allows).

My current plan is to work on this site a bit early in the morning, and occasionally in the evening - where some notes will be captured over the course of the day elsewhere and distilled here.

Each page (like this one) will record some work that has been done along with upcoming plans.

The content is authored in org-mode, and is currently exported using the org-export-dispatch command to product HTML. This is being done manually to start. At present this results in the html file being produced alongside the org - that should be split out to a distinct destination directory.

Similarly the home page will be manually updated and exported.

The site will be published to SourceHut pages. In the current iteration the generated HTML pages will be moved from their initial location alongisde source. To encode the instructions from srht.site and move the files, I'll create the site.mk file.

I had to spend a fairly typical amuont of time working through minor makefile issues, which made some of the exporting steps notably onerous - I'll look at getting those automated fairly soon.

This project will make use of literate programming within org; this will be expanded upon quite a bit later.

Per the instructions on the site, I clones the hut repository, built, and installed it.

The initial site (of pretty much just this page) is live at: https://mwhipple.srht.site/.

Per the sourcehut docs, the publishing can be automated using a conventionally named repository and a build manifest. This copies the example replacing the relevant variables and invoking make to handle the build.

image: alpine/edge
oauth: pages.sr.ht/PAGES:RW
packages:
- hut
environment:
  site: mwhipple.srht.site
tasks:
- publish: make --directory=$site publish

This requires the exported contents to be present in the repository for the time being.