From the round-1 review of #224 (issue #149).
Where: scripts/fleet/build_subsets.py:21-25 on fix/npm-record-links.
The SITE_BASE comment changed from "CultureMech and MediaIngredientMech do not deploy per-record pages" to "do not reliably deploy per-record pages". That groups MediaIngredientMech with CultureMech's flickering pages/media/ (#175). In fact MediaIngredientMech publishes no per-record pages at all.
- Its repository: eight
.html files, none of them per record, and its generate-pages workflow uploads only docs/.
- Its site: links only
browser.html, ingredient_graph.html and ingredient_umap.html, and /MediaIngredientMech/ingredients/ returns 404.
The old wording was right for it.
Fix: split the sentence. MediaIngredientMech publishes no per-record pages; CultureMech's come and go with its Actions deployment.
From the round-1 review of #224 (issue #149).
Where:
scripts/fleet/build_subsets.py:21-25onfix/npm-record-links.The
SITE_BASEcomment changed from "CultureMech and MediaIngredientMech do not deploy per-record pages" to "do not reliably deploy per-record pages". That groups MediaIngredientMech with CultureMech's flickeringpages/media/(#175). In fact MediaIngredientMech publishes no per-record pages at all..htmlfiles, none of them per record, and its generate-pages workflow uploads onlydocs/.browser.html,ingredient_graph.htmlandingredient_umap.html, and/MediaIngredientMech/ingredients/returns 404.The old wording was right for it.
Fix: split the sentence. MediaIngredientMech publishes no per-record pages; CultureMech's come and go with its Actions deployment.