diff ref struct Rietveld refinement for the Mac · powder diffraction with X-rays, synchrotron and neutrons · started October 2026

Method

How this site works

Where it lives, what is generated, how the log is kept, and what counts as evidence.

Location

The site is ecosystem/ inside the private repository jmigartua/diff-ref-struct, next to core/ (the refinement engine) and app/ (the Mac app). It has three parts: data/ (YAML: navigation, brief, programs, log, releases), tools/build.py (the generator) and site/ (the Quarto project).

Build

cd ecosystem
python3 tools/build.py        # nav, brief, programs, log page, release notes, home includes, LOG.md, core/CHANGELOG.md
cd site && quarto render      # pre-render runs build.py again, then renders to _site/

The generated files are everything under site/_gen/, site/log/index.qmd, site/releases/index.qmd, site/ideas/, LOG.md and core/CHANGELOG.md. They are not edited by hand.

The seed-place

data/ideas.yml holds the ideas said for the project (I01, I02…, ids that never change), each with the day it was said, an assessment, a proposal, what is left to decide, and its own dated log. An idea's status is one of seven words: seed, discussed, workshop, green, migrated, parked, discarded; its home names where it migrates (the app, the core, a module, an extension, the kit, the site). The Ideas section, in the incubator's own palette, is generated from it: a board and one workshop page per idea. An idea becomes a requirement of the brief and a step of a stream when it gets the green light; the log entry that does so is cited on its page (L288).

Publication

Every push to main that touches ecosystem/ runs the Action .github/workflows/publish-site.yml: it builds, checks, renders with Quarto 1.10.18 and replaces the whole content of the public repository diff-ref-struct-site, which GitHub Pages serves at jmigartua.github.io/diff-ref-struct-site. The public repository holds no source; the sources, the core and the app stay in the private one (L007).

The log

data/log.yml holds one entry per dated event: finding entries from the study, decision entries with their reasons, and work entries as phases advance. Ids are L001, L002… in order and never change. A decision is logged the day it is taken.

Evidence

  • Programs. What is said about a program comes from its manual, its reference papers or its files, cited on the page. What is believed but not yet checked is marked so.
  • Code. A feature of the core is claimed when its test passes; the test is named.
  • Physics. Equations are cited to the International Tables or the paper they come from, by equation number.

Inherited

The design kit and the build conventions come from the FTIR ecosystem site of the difes project (L004).