We want to avoid that certain data lands in the CaaS for various reasons:
Data from a synthetik transport language, that is only used to offer content to other editors, who would copy / adapt the content to their own content. The complete language is an internal part, which does not need to be in the CaaS and it would also be an extra security step to not have it in the CaaS, because it is only internal data.
Data which is marked as "not translated": This may be data that is invalid or incomplete. We what to avoid it being processed further.
Data from a project import from another CMS, that is stored in specific input fields. This data is a lot. And again not needed in the CaaS, because it is only in the FirstSpirit as refernce for the editor to build the new content from. As this is really a lot of data, it would really blow up the CaaS unnecessarily, which may cause a preformance issue.
Who is it for?
As this would possibly increase the security, performance and flexibility, it could benefit a lot of different users.
How could it be done?
Here are some ideas how this could look:
Make use of the setting, if a language should be generated. No generation => no CaaS
Make use of the "translated" marker: Not translated => no CaaS
Add an option to the input fields like such: sendToCaas="no" (default: "yes")