Best practices in organizing Server Connect actions

Wooow thanx so much! This is very useful and shows how a project can be structured, cause its the beginning of every project and very important, as long as we cannot really rename actions now.

That with Forms and Lists makes sense to me. I try to think about CRUD, so :

MainAction could contain :

  • List : R(read) and D(delete) makes sense on same page
  • Forms : C(create) and U(update) are very similar and needs forms

@brad and @t11 I respect your privacy of each of your project, but maybe some sample structure within these folders would be interesting.

Similar post with some infos about organization folders and server actions: