> Both of those lack support for custom "sources", instead of just markdown files. That's why I wrote sitio[1]. sitio has a pretty simple imperative API where

> Both of those lack support for custom "sources", instead of just markdown files. That's why I wrote sitio[1]. sitio has a pretty simple imperative API where you can say stuff like "generate page on /about/ using the React component on 'components/page.js' and the following data: {}", so your entire configuration is just a simple nodejs script and you can use data from anywhere. Then it generates static pages that, if JavaScript is avalaible, will become React components and the entire site will be a Spa with proper history. If there's no JS, it's an HTML static site. Also, it uses Browserify under the hood, because Webpack is horrible. [1]: https://github.com/fiatjaf/sitio https://github.com/fiatjaf/sitio