Reorganise server actions: tips?

As the project grows, the server action list is becoming quite a mess.

I want to restructure my folder structure.
For example I want to create a new ‘content’ folder and move the folders ‘audio_content’ and ‘courses’ into it.

However I’m aware that this will cause issues, AFAIK it can break:

  1. Server action calls on the client side (in a form, or a ‘server connect’ element)
  2. Data bindings on the client side
  3. For library actions: break includes and ‘execs’ in other server actions

I am now moving things while doing a search to see if there’s any file referencing this server action. But I feel like I might miss something and wake up to a broken application after finishing reorganising.

This is what I’m doing now:
image

There must be people who’ve done the same. Any tips?

Community Page
Last updated: