Turning this site into a developer publication

This site now has two main jobs: help people find the software I build and share useful writing about development. That affects more than the homepage. Navigation, product descriptions, article topics and the contact route all need to reflect what people can actually do here.

Separate products from professional history

A product listing should explain what the product does and give a real destination for using it. My past professional experience belongs in the biography, where it provides context without suggesting that previous employers own, use or endorse my independent products.

Treat metadata as part of the content

A rewritten page can still tell an old story in search results, social previews or structured data. The site now uses the same positioning across those surfaces. The sitemap also needs to describe the current pages, while old URLs need an intentional redirect or a missing-page response.

Keep publishing intentional

The blog is organised around software engineering, SaaS development, game development and project notes. Articles belong here because they explain something useful about building or operating software. Automatic imports are paused while the earlier content is reviewed for that purpose.

The contact route is for product support, feedback and general enquiries. The most useful feedback includes a product name, what you expected and what happened. Those details connect the website to the continuing work of maintaining the products.