Hi @kreativoli
I did something similar, described in this answer
When you talk about different content, you talk about different properties for the NodeType, correct? Top of mind, I can not tell how that would be. But first thing that comes to mind, is this part of the docs
https://docs.neos.io/cms/manual/content-repository/nodetype-properties#depending-properties
So you will create all properties in the base package, and activate them on a condition level (is my guess) - it could become spaghetti when it grows large, but it’s a way to get started. Since the properties is needed in the nodetype definition