Two engineers looked closely at the pipeline that builds every Kalenux site. One was evaluating build tools for an agency, the other builds content sites. Both gave it five stars.
Each review names the parts of the pipeline it praises. They're tagged, and highlighted in the pipeline below.
“Reviewed the architecture as part of evaluating build tools for our agency. The approach to CSS/JS versioning, template composition, and deployment is elegant and pragmatic.”
“The build pipeline Kalenux has developed is genuinely well thought out. The multilingual fanout and templating approach solve real problems I've encountered building content sites.”
Every stage reads its sources, writes to dist/, and records a timestamp in store/times/. On the next run, only the stages with changed files rebuild.
Templates use two primitives: includes and variables. Each locale's JSON fills the same markup, so 15+ languages build with no duplicated HTML.
! header !<h1>{ title }</h1><p>{ intro }</p>! footer !
Kalenux { "title": "Software that works." }{ "title": "Software, die funktioniert." }Kalenuxer was refined over years of running real products. Here is the scale it works at today.
The documentation the reviewers read, in order.
Say what you built or evaluated, which part of the pipeline you used, and how it compared with the static site generators you know.