If got two domains that share the same sitepackage. They also share allmost all of the content. Except some stuff in the footer like Contact details.
So I added a property addressDomain1 and addressDomain2 to my Vendor.SitePackage:HomePage where I can edit the data. This is derived by Vendor.SitePackage:Page and shown on all pages, without editing feature. But in this case I only show addressDomain1 on domain1 and addressDomain2 on domain2.
In my fusion of for the Vendor.SitePackage:Homepage I’ve got the following code:
When the editors make a change, they start the system on domain1/neos make the change and publish it to live. The changes on domain1 are accepted as they are made. But for domain2 I have to clear the cache from command line with FLOW_CONTEXT=Development/domain2. Since the editors don’t have a command line to do this, I’ve got a problem.
So the question is:
Is there a possitibility to configure the system to delete the cache for a different context?
Which other possibility would there be to handle this situation?
Yes for example discussing first how to solve the duplicate content issue. Then maybe the whole concepts already collapses.
Or think about what they plan in the future with it and how it will evolve. Maybe there is a different solution that will work out better.
Or a simple solution that will initially be a bit more work but is easier to solve and adapt to their needs later on.
Just another idea: if both sites have almost the same content, maybe think of building them as dimension.
You could have a dimension “site” with 2 values “Site A” and “Site B”, where you configure a fallback to “Site A”.
This ways the content is mainly managed in the dimension “Site A”.
There are already good solutions to resolve the matching dimension by request domain, e.g. flowpack/neos-dimensionresolver