Guides
The reference pages say what each field does. These three say what to put in it, which is a different question and the one that takes longer to answer.
Every setting in this tool has a correct value and the tool does not know it. A width list is correct against a layout that only your CSS has seen; a rule order is correct against a shop that only your catalogue knows the shape of; a queue length is correct against a machine that is not this one. So these pieces are about the deciding rather than the clicking, and each ends up somewhere the interface cannot follow — in a stylesheet, in a spreadsheet of product codes, or in a terminal, where a shell script is frankly the better answer.
They are written to be read once and returned to for the tables. Nothing in them is a tutorial for the buttons; the buttons are on the front page and they explain themselves.
Reading the width list off your own layout, and deciding when a 2x file is worth its bytes.
Read it if you are about to type a width list into a build script and are not sure where the numbers came from.
One rule stack that turns an uneven folder of camera files into listing, grid and zoom images.
Read it if the same folder of photographs arrives every week and you are doing the same six things to it by hand.
What a run costs in memory, where each kind of machine gives up, and when to write a script instead.
Read it before you queue a thousand files, or after a run died at file 140 and you want to know why.
What is not in here
The field-by-field material lives on the naming reference, and the responsive control has a page of its own with the tool already switched on. There is no news here, no release notes and no posts: this site ships a page when there is something to look up, and a fourth guide will appear when there is a fourth thing worth writing down rather than on a schedule.