Hey @aesmail, congrats on the project! It’s definitely a big undertaking so we all appreciate your efforts.
My honest feedback from what I’ve read so far about the project is that you should prioritize more convention over configuration. If you try to make the panel too extensible to accomodate all needs you fall into the trap of forcing developers to having to learn way too much in order to properly use it, which creates greater cognitive overload and thus steers people away: “It’ll be easier to just write this from scratch by myself than figuring all of this out to fit my needs”, you know?
I’d suggest to make some design choices on how you think most people will use an admin panel and create a powerful and simple workflow based on that, and if people need customization, give them the liberty to just write common controllers/views/templates as they would a normal Phoenix app.
I liked how Torch (GitHub - mojotech/torch: A rapid admin generator for Elixir & Phoenix · GitHub) approached this: it simply generates a bunch of files for you and lets you adjust them however you like. But that’s obviously just one way of looking at things, you gotta nail the right balance between funcionality and freedom, I just think Kaffy as it stands is pulling a bit harder on the functionality side (whilst Torch is too much on the freedom side).
I’ll be keeping a watch on how things develop, good luck!
