eta (η) VS GrapesJS

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/

What I found was GrapesJS. I'd definitely recommend it: https://grapesjs.com/

Open-source web builder framework for creating templates without coding. Website - GitHub

I agree. It is a little confusing. As a dev I can see how it might be useful when I don't have time to build the interface. But not really sure.

Have you looked at something like https://grapesjs.com/ for templates?

E.g https://grapesjs.com/

This will be helpful https://grapesjs.com/

Take a look at grapesjs ( https://github.com/GrapesJS/grapesjs) . . . With a bit of work u can make a pretty good editor using it. For reference u can check out something like poweredit (https://github.com/anatoli-dp/poweredit) that uses it (I am aware it is a pretty poor example.domt hate me but it was my first take at using the framework and making an application) as well as quite a few others. But it does have a lot to use as a starting point for your own