Streaming live at 10am (PST)

Workaround for too little "Fields per Collection" / CMS dependecies

Hi,
I have just started to implement my first project. The Angular developers should be relieved and the project should have been finished yesterday :wink:
It’s a really big / complicated project (at least in my head):
I want to create a CMS in which several projects can be displayed. Each project has more than 60 fields (text fields, images, copyrights, toggle buttons for visibility).
Is there a way to circumvent the limitation?

Another approach I tested was to link several CMS together. Unfortunately, only the main CMS can be changed and the content of the assigned CMS always remains the same.
Does anyone have an idea how to change the content of the main CMS depending on the project?

I am happy about every tip!
Many greetings
Kati

Do you have a sharelink of you current project