Design research
Research records capture measurements, inputs, and tool versions from specific studies. Current behavior is defined by the Design contracts and validated on Hugo Extended 0.168.0 per the toolchain contract.
Publish research in the Design tree only when another maintainer can inspect its method, understand its scope, and repeat the applicable check. Keep raw agent transcripts, temporary build logs, and local absolute paths out of research records.
Research map
| Record | Evidence |
|---|---|
| Goldmark block attributes | Render-hook visibility and CommonMark container limits on the historical Hugo versions recorded in the study |
| Consumer and migration evidence | A dated corpus survey plus deterministic Book migration results |
| Comprehensive review, 2026-08-26 | Implementation, configuration, output, security, test, performance, and doc audit |
| Community issue and PR review, 2026-09-19 | Reproductions, PR acceptance advice, and remedies for sidebar, focus, and search feedback |
| OINK 1.1 release review, 2026-09-20 | Five runtime repairs, documentation readiness, validation evidence and publication boundaries |
| CLI acceptance snapshot, 2026-09-29 | Executed Starter, real-site, offline, upgrade, and reproducible-archive checks for the local CLI candidate |
| Visual preset acceptance, 2026-10-05 | Paper/Slate local implementation, actual output and bounded browser evidence |
| Ink and Terminal experiment, 2026-10-05 | Explicit experimental presets, design tradeoffs and real-site verification |
| OINK 1.2 pre-release review, 2026-10-05 | Final local candidate checks, cleanup, local resources, compatibility and publication boundaries |
| CLI maintenance acceptance, 2026-10-03 | Historical R1–R8 and A18 source-bound runtime and archive evidence |
| Theme review, 2026-10-13 | Reproduced output and interaction defects, repairs, and local validation scope |
| Component refinement, 2026-10-25 | Final component acceptance, 409 Chromium tests, targeted three-engine visual review, CSS/JS size comparison, and separate gallery baseline failures |
| Document comparison, 2026-10-29 | Dated source review behind the translation comparison decision; historical, not the released contract |
| Review repairs, 2026-11-06 | Reproduced v1.5.0 defects, bounded development repairs, validation and remaining work |
| OINK 1.5.1 readiness, 2026-11-06 | Three repaired candidate regressions, owning checks, browser acceptance, publication evidence and release gates |
Publication rules
A research record states its date, inputs, applicable versions, method, result, and known limits, with changing counts labeled as snapshots. External framework comparisons should be refreshed from primary sources before publication and focus on conclusions that affect OINK.
When a result becomes an accepted product choice, link it from an accepted decision. If it proposes behavior that does not exist, move the design question to Proposals.