The init_project script and dev-kit tools should be a pure-Matlab solution. This thing is intended to be easy to use for an Matlab user, and asking someone to install and set up WSL on Windows, or even use the Terminal on Mac, is a barrier to adoption. But any Matlab user can be expected to know Matlab. (Well, to some extent.)
That doesn't fix the doc-building problem: Jekyll and mkdocs still need Ruby. But the gh-pages version of the docs could be used in a "raw" mode on Windows, where you don't have a local preview and just rely on GitHub to do the Jekylling.
The init_project script and dev-kit tools should be a pure-Matlab solution. This thing is intended to be easy to use for an Matlab user, and asking someone to install and set up WSL on Windows, or even use the Terminal on Mac, is a barrier to adoption. But any Matlab user can be expected to know Matlab. (Well, to some extent.)
That doesn't fix the doc-building problem: Jekyll and mkdocs still need Ruby. But the gh-pages version of the docs could be used in a "raw" mode on Windows, where you don't have a local preview and just rely on GitHub to do the Jekylling.