New capture in the dark theme, showing a labelled screw tray instead of
the bracket. Same filename and alt text, so the post body is unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Drops every em dash, ellipsis and curly quote from the prose. The
surrounding corpus uses straight apostrophes throughout and almost no em
dashes: the two cleanest technical posts have none at all, so the density
the previous commit introduced read as machine-written.
Rewrites the affected passages with the constructions used elsewhere on
the blog (colons, "since", "so", split sentences, first person) and drops
phrasing that does not appear in the corpus, such as "load-bearing" and
"is not a drop-in copy".
The file tree keeps its box-drawing characters since it is tree(1) output
inside a code fence and predates these edits. The viewer snippet now spells
the ellipsis as a JavaScript unicode escape, matching the deployed
stlview.js exactly.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The guide told readers to copy Codeberg's stlview.js verbatim, but the
deployed viewer is a rewrite of it: it keys off the URL instead of the
"view raw" block, takes over .file-view, and loads three.js as ES modules
rather than through the UMD global. Following the guide as written left
you with a viewer that never loaded. Point at forgejo-stlview instead.
Also documents three things that were load-bearing but unstated: the
volume mounts (and that the container path is /data/gitea), the
classList.remove('stl-page') without which the step 2 CSS hides the
injected canvas, and the patch the three.js example modules need because
they import via the bare 'three' specifier.
Adds the file-view-only limitation, the [stlview] console-logging debug
hint, AGPL-3.0 attribution for the derived viewer, and the Forgejo
version this was verified against.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>