chadtmiller.com/knotless

Switch repository

Loading…

What changes

marketing/ holds what knotless is presented with outside its own pages: the ATStore listing's fields, hero, icon and screenshots, and the knotless.dev account's Bluesky banner. marketing/src/ holds the pages that draw the hero and the banner, and render.mjs draws them again. The README names the listing's record, and says to update that record rather than create another, which would make a second listing.

Why

These were made and published from a scratch directory, which does not last. The next change to the listing or the banner should start from what was published.

How it was checked

node src/render.mjs in a directory of its own drew all three images. The banner came out the same size to the byte and the hero within about 150 bytes, and I looked at each committed image. Nothing here is read by a check but the check and test every pull runs: no crate, page or doc changes.

Shortcomings

The screenshots are taken from the live pages by hand, so they have no script, and they show the star count, version and relative times of the day they were taken. They add about 2.5 MB of PNGs to the repository, and any redraw adds more.

🤖 Generated with Claude Code

This adds marketing/: the ATStore listing fields and images, the Bluesky banner, the HTML pages that draw the hero and banner, and a render.mjs that redraws them. It also adds .dockerignore and .gitignore entries. I read every changed file except the PNGs, which I did not open. The pages, render.mjs, listing.json and the README agree on sizes, paths and the 2x scale: the hero is 1600×900 drawn at 2x, which gives the 3200×1800 the README states. Nothing in the Rust code, the web pages or the docs changes, so the change-file and docs rules don't apply. I found nothing that has to change.

Two small notes, neither of which holds the pull:

• hero-alt.html loads a font from Google Fonts at render time, so a redraw needs network access and can drift if the font changes. The README already says this.
• listing.json has fixed createdAt and updatedAt values. Anyone who runs putRecord from it should keep the original createdAt and bump updatedAt.