The main difference with ex_admin is that ex_admin uses a DSL to control its behavior. Torch is a generator: you run a command and you get standard Phoenix controllers, views, and templates in your project.
In my opinion, this makes it easier to customize because you don’t have to learn the DSL and potentially run into roadblocks if you need something the system doesn’t support. With Torch, you just have regular Phoenix files, so you can tweak them any way you like.
I am interested to help with Torch. I was already planning to work with it and add some liveview features, I will reuse some of my code from my table filter with liveview
And I will add an option for the generation of the templates to be liveview templates or the current templates.
I am quite new to Elixir/Phoenix and github and it would be my first team project on github.
I’m writing my own admin generator (Mandarin), based on a custom query builder which might be a little more powerful than the one used by torch. I don’t know if there is any benefit in both projects reusing part of the other. Probably not, because both projects seem to be coupled to their respective query builders. Link to forum post here: Mandarin + Forage - An admin tool for phoenix