Content for reads.aiste.io is machine-generated daily rather than hand-authored, so a custom build pipeline inside the Action would be extra surface to maintain for no real benefit. Decided: the daily Action commits Markdown files with frontmatter (date, source, category, summary) and lets Jekyll — GitHub Pages’ native, zero-config build — render them into the site, the same pattern already used in this delulu-lab repo. Considered a custom static-site build step (more control over layout) but rejected it since nothing about a category-grouped daily issue needs more than Jekyll collections/frontmatter provide.