PinkKidneyWeb

The deploy target for the Pink Kidney book — a mirror of another repository’s render output, with no source of its own, recorded here so nobody looks for the content in the wrong place.

Purpose

This is infrastructure, not a project, and its own README says so plainly: “Deploy artefact for the Pink Kidney project book… Contents of _site/ are auto-populated by quarto render running in D:\PembeBobrek\… Do not edit _site/ manually — changes will be overwritten on the next render.”

The mechanism is a post-render hook (scripts/post_render.ps1) in PembeBobrek that mirrors its _site/ output here with robocopy /MIR, from which it is published.

It earns a short page for one reason: the content lives in a different repository from the one that publishes it, and that is exactly the arrangement that wastes someone’s afternoon. A reader who finds a claim on the published site and goes looking for its source in this repository will find only rendered HTML. The source is in PembeBobrek; the analysis it documents is PinkKidney. Three repositories, one project.

Data used

None of its own. Everything in _site/ is generated elsewhere.

Worth noting what comes through in the mirror, because it says something about how PembeBobrek is being written: alongside the guides there are five audit reports — audit_A1_literature, A2_stats, A3_viz, A4_ml, A5_pathtools — i.e. the book has been reviewed along five separate axes and the reviews are published with it. That is an unusually disciplined habit and it belongs on the PembeBobrek page rather than this one, but this is where it was found.

robocopy /MIR is a mirror, so anything present here and absent upstream is deleted on the next render. That makes the “do not edit” warning a real constraint rather than a convention.

Methods

Not applicable — no code beyond the deploy plumbing, which lives upstream.

Current state / open questions

Eight commits, last 2026-05-03, private. Consistent with a deploy target: it changes only when the book is re-rendered.

• The mirror is one-directional and unverified. Nothing checks that what is published matches the current state of PembeBobrek; if a render fails halfway, or the hook does not run, the published site silently keeps serving the previous version. A rendered-at timestamp on the site would make staleness visible. [unverified] whether one already exists.
• Three repositories for one project is a choice worth revisiting, or at least writing down once. It presumably exists to keep a large _site/ out of the analysis repository, which is a reasonable motive — but the same split has already caused confusion about where the Pink Kidney work actually lives.

Related: PembeBobrek — the source repository whose render output this mirrors; read that page first, and note the five audit reports surfaced here. Related: PinkKidney — the underlying analysis the book documents.

Derived from: repository read 2026-07-29 — README.md read in full, git ls-files for what is tracked, git log and gh repo view for currency and visibility.