alexwlchan / books.alexwlchan.net Goto Github PK

I want a fixed seed for determinism, and I want a consistent seed to get a consistent shape – but that also means I get a consistent pattern of light/dark/dark/light/etc.

I should really use:

• the same seed for the shape of every image (e.g. seed = 0)
• different but consistent seed for the colour of every image (e.g. seed = colour.as_int(16))

This will be more obvious once I actually implement it.

See https://app.netlify.com/sites/books-alexwlchan/deploys/62d0901fc6f54500084d55d7

Currently I'm setting the width/height of the cover images with max-width/max-height attributes in the CSS, but this means a browser which hasn't loaded all the images will have to keep redrawing the page layout as they load in.

It's a static site! I can know what the dimensions are! If I load them and set them as width/height attributes, a browser can render the whole page when it gets the HTML, then do lazy loading of the remaining images.

Occasionally the build will fail because the GitHub Releases API will refuse to return results for an unauthenticated GET. It should be possible to give Netlify a token with minimal permissions that avoids this issue.

I used to do this, but I think it got lost in the move from Python to Rust.

Hi Alex! 👋 Great job with building your book-tracking website. I like the design and idea. However, I do have a question: What is the architecture of this project? What role does the 🦀 play? I have a similar project here. Mandy is a new static-site generator built solely by me in the last two weeks. The architecture is quite simple: Mandy fetches all the info from the Mandy project directory, stores this info in a structure and generates the static site's files from this info. In the same way, what is the architecture you used for your project? I'm just curious! 🙈

e.g. https://brill.com/cover/covers/9789004369054.jpg

Mimicking the User-Agent of a different browser would get around this.

There's a bug in the Netlify deploy process where:

1. I push and tag a new version
2. GitHub Actions creates the new release
3. Netlify tries to pull vfd from that release, finds it's missing, and breaks

This is clearly suboptimal; I have to restart the build whenever this happens. For some reason Netlify interprets "build failed" as "upload an empty folder as the site", which is wrong.

e.g. https://www.google.co.uk/search?as_st=y&tbm=isch&hl=en&as_q=In%20God%20We%20Doubt%20john%20humphrys%20&as_epq=&as_oq=&as_eq=&cr=&as_sitesearch=&safe=images&orq=&tbs=isz:l&biw=1093&bih=774&sei=uBx7UM7YEueN0AXBzoHQAg

If you run an out-of-date version of vfd, you get a helpful message:

A newer version of vfd is available, please update:
https://github.com/alexwlchan/books.alexwlchan.net/releases/tag/v1.3.3

Unfortunately this message will also appear locally if you're running a newer version than what's on GitHub, and you haven't pushed your changes yet. This is mildly annoying, and should be fixable.

This build should either have failed or done the right thing, but not delete the entire site: https://app.netlify.com/sites/books-alexwlchan/deploys/62e58d3317db330008cacbdc

That's what I was doing before the big Rust rewrite.

Currently I can only deploy the site when running locally on a Mac that has the binaries installed. But Linux binaries are available through the GitHub releases – Netlify could download those and build the site.

This would allow me to make edits through the GitHub web interface/from an iOS device.

Either detect them as Markdown and drop a warning, or fail the build on unrecognised file extensions.

Precisely because it's not read by any of the rendering code, and is just for my personal records, it's in at least two places (book.format and review.format). It's a property of the book, so I should move it there.

See e.g. https://books.alexwlchan.net/reviews/the-secret-diary-of-lizzie-bennet/

The build is failing with the following error:

./vfd: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

I don't think I've suddenly started pulling in libssl.so.3; it's been there for a while. What changed on 11 December?

In particular the boost filter passed to the templates. If you over-boost, the colours get washed out to white – that's not what I want. I should look at maybe boosting the saturation or something, rather than the RGB values.

As part of the Jekyll rewrite, I changed the URL structure from /reviews/{slug} to /{year}/{slug}.

• This allows me to read the same book in different years
• The /reviews/ namespace is unnecessary; there's nothing on this site except reviews

But to make sure any existing links keep working, I should create some redirects from the old URLs to the new URLs.

I have a bunch of books that I know I read at sometime, but I don't have any more information than that. In those cases, there's no point capturing the review metadata – it will always be empty.

I should have a better way of handling this – possibly fetching those "reviews" separately, maybe even having them in a separate directory – which will make the internal code cleaner.

That is a better way to say “near instant”, but without implying these operations take no time at all.

Currently I'm shelling out to ImageMagick, which is both crude and arguably unnecessary – I already have the Rust image libraries available.

vfd 1.3.4, observe:

$ vfd deploy
Building HTML pages... done in 997ms
Syncing static files... done in 1ms
Creating thumbnail images... done in 9ms
Deploying to Netlify...
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/main.rs:218:86
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The actual problem is that I was running this on a laptop without the Netlify CLI, but that's not obvious from this error.

Currently I have to modify the scripts every time I add a new type of contributor; I should change it so it can accommodate new contributor types on a per-book basis.

I don't need a big list of tags, but being able to find books by fiction/non-fiction/genre might be useful.

I've got https://github.com/alexwlchan/inquire_tag_autocomplete as a component for getting this data when I save a review.

There are a handful of books that have null as their publication year; this is probably a data bug that was introduced by an old version of the scripts.

I should:

• Fix the dates in the broken files
• Update vfd to detect these so it will warn me pro-actively

Something I want to know is how many books I didn't finish, but this isn't counted in the HTML. A vfd subcommand to count that might be helpful.

Browsers will cache the CSS for a very long time (good!) but they don't know to invalidate it when the CSS changes (bad!).