Colophon

I decided to rebuild my personal site in 2026 after a long hiatus to take back ownership of my content from social media. We’ve all seen those platforms degrade and become toxic. On the flipside, there is a use case for limiting personal content to just family and friends. I’m trying to navigate this mess. It’s a work in progress.

I was never content with the blog as a format. I don’t like microblogging, either. Those types of publishing seem better suited for hyper-focused creators who benefit from high engagement. It’s pointless for me because my output is pretty random, and dealing with spam comments is a chore.

But I do want to share information and creative output. I’m experimenting with a digital garden approach where content is structured and maintained on an ongoing basis. It’s a reference for myself as well as anyone who might be interested. I’m by no means an expert in many of these topics, and don’t represent myself as such.

By sidestepping the drama of comments, I’ve sacrificed one route for learning new things from genuine readers. I do invite that sort of interaction, so feel free to reach out if you have anything constructive to share.

Technical

  • Engine: Astro.js static site generator.

  • Hosting & Infrastructure: Cloudflare Pages with continuous deployment via GitHub.

Design & Typography

  • Typefaces: Crimson Text, Inter, and PT Mono served by Google Fonts.

  • Color Palette: Copper ■ #bb7e3d | Slate ■ #5c6d7a | Spicy ■ #7d4545 | Thunder ■ #2e2622

  • CSS Frameworks: Just vanilla CSS.

  • Inspiration: The current site design is an amalgam of my previous site designs and elements of many external sites I found appealing. My Notebooks derive from structured documentation I created for professional use, and this format was originally inspired by ReadTheDocs. I’m generally satisfied with how it’s all come together, but still have some kinks to work out regarding responsive display.

Hardware & Workflows

  • Hardware: Linux Mint desktop, MacBook Pro.

  • Software Tools VS Code, GIMP, Claude Code (to scaffold features, refactor, and port content types originally developed in Umbraco CMS).

Standards & Policies

  • Privacy: Read the full Privacy Policy regarding how data and analytics are handled.

  • Accessibility: Review the Accessibility Statement for standards, continuous testing efforts, and contact details for access barrier reporting.

  • Disclaimer: The technical notes, mechanical guides, and opinions on this site reflect my personal experiences. They are provided for informational purposes only and do not constitute professional advice or formal instruction. If you choose to undertake bicycle maintenance, electronic repair, or any other physical project described here, you do so entirely at your own risk.