Ronan Berder
Ronan Berder
Working on a new version that has a new Jekyll configuration.
Sure. I'm thinking of moving to supporting the [OpenAPI standard](https://www.openapis.org/) (API spec can be stashed in `_data/`), updating the Jekyll set up (something closer to https://github.com/Wiredcraft/jekyll-basics) and switching to [Alpine.js](https://github.com/alpinejs/alpine)...
I'm actually working on getting a lighter/simpler version of this using a single HTML file with some Tailwind and Alpine.js. All the templating is done by Alpine.js, and I believe...
Good idea indeed, but we probably want to have thoroughly outlined our framework before we invest in building an executable.
Only reviewing this now. @xufeng123 : why do we have that many codes? 5 or 6? What are they? Can't we simply have 3? Something like: alpha, beta and stable.
I'm setting up GitHub Sponsorship, but I'll also be releasing a Pro version in the next few weeks. Hopefully there's value enough for some of you to buy it.
The Pro version will likely include additional features useful to teams (e.g. scheduled edits, invite users by email, …), but I still want people to get all of the must-have...
> Would the pro version be a paid self-hostable model ? Pro will still be hosted, but I am considering selling an enterprise license with the Pro features that can...
Let me try to replicate.
Could you try with the latest version?