Could somebody please create some documention about fields? Especially how everything ties up with js?
I mean i managed to make some fields looking through sourcecode of other fields but it would make things lot easier if there was something about field lifecycle. Lets say if i want to make js only field, how to return data to be saved? What are all the basefield functions doing… core field classes dont even have comments.
My plan is to eventualy use vuejs to make ui because the jquery only approach gets nuts when doing more interactive fields and vue is just much easier/faster (please lets not talk about hype, i hated angular and agree with Bastian decision about Angular panel but i dont see reason why not use smart small lib like vue).
I am confused and while i might figure it out eventualy - i would be really nice if i didn’t have to figure out everything by myself.
I believe Kirby would also have more fields if they are documented correctly :)).
We feel your pain.
Actually we are already planning to improve the Panel to make it easier to extend, but as always we’d rather make it take longer to get it right instead of rushing it, so it may still take some time, no ETA yet.
You already have some great answers here. As a complement Kirby Secrets contains undocumented secrets of Kirby. It includes some articles about the panel fields as well. Maybe you can find something useful there.