eta (η) VS Tabulator

ERDIA uses the ETA template engine to generate documentation. The reason for using a template engine is that it allows you to customize the documentation the way you want it. If you want to customize documentation that ERDIA generates run the following command.

Just stumbled on this: https://github.com/eta-dev/eta

Eta : a lightweight and blazing fast embedded JS templating engine that works inside Node, Deno, and the browser.

I've been using Eta: https://eta.js.org/

It doesn't do gzip or image optimization, but such features might be better suited as server middlewares separate from the template engine.

Haven’t used it yet, but Eta supports Deno: https://eta.js.org/

Eta is a very similar template engine to EJS. It's supposed to be faster, lighter, with async templates.

https://eta.js.org/

https://github.com/eta-dev/eta/

Coded mainly in Perl and Gnuplot, recently extended by Python Pandas and JavaScript Tabulator and ECharts

We use Tabulator for a similar use case at my job, it has a virtual DOM to support thousands of rows pretty well. It's not React based, it's a vanilla JS library. There is a React wrapper here but I don't have experience with that.

If you familiar with programming, then defiantly it way to go, tabulator as a CRUD for frontend and simplest sqlite backend. The reason such type of apps not broadly exists is that because any business has it's own workflow, so all-in-one common apps became overloaded with useless features but doesn't have feature a client needs

as well to have a choice for theme with detailed info page (size/modefied-time) with sorting capability (by utilizing something like tabulator)

I am a mostly backend dev using python and only know enough JS to be dangerous. I am doing some simple front-end work for my job, and I am using tabulator.js which creates a column with an x in it. When that x is clicked, this function runs.

Yeah. NaiveUI is good. Also check tabulator. http://tabulator.info/