Article
Why one stack
A stack is a set of decisions made once so they need not be made again. Using the same few tools in every project means each new one starts from a known shape: the same shell, the same components, the same checks.
The interface is Flowbite Pro on Tailwind CSS; behaviour is added with Alpine.js to pages that already work without it. Pictures have the library that suits them: Cytoscape.js for networks, Apache ECharts for dense charts, Chart.js for simple ones, D3.js for drawings where data becomes form, and p5.js for generative art. The sunburst at the top of this page is one of them at work: ECharts splits the most recently active repositories by category and then by language, measured, not claimed.
The site is assembled by Zola in two languages (internationalisation is checked like any other rule), deployed to GitHub Pages, and supervised by Majordomus, which refuses to call work done before its verification ran.