Ok, been mulling over this one for some time...
Basically i created a secondary context with symlinks pointing to original context. This all works fine.
My issue is maintenance. Anytime an editor adds a resource to the primary context, the cloned context should also have the same resource's alias.
Lets simplify:
context1.site.com/about-us.html
context2.site.com/about-us.html
second "about us" is just a symlink pointing to the original about us page. They both have the same alias "about-us", they use different templates, all well and good. It's reasonably easy for me to set this up for all the existing pages, however what about new pages editors create?
How can I ensure that if an editor creates a new resource called "about-us-more-info.html" in main context, without my involvement secondary context will produce the error message if someone tries going to this link, as there is no page with the symlink in secondary context - all these new pages will fail unless I create them in the secondary context too (manually)?
I've been looking at babel, and I could possibly use this to ensure pages in the secondary contexts get created, however babel will only copy the content itself and won't create a symlink.
Its almost like I need a plugin which, on every page's creation -
- copy page alias, create resource of same alias under all subsequent contexts (use template specific to that context whilst doing so)
Anytime you delete the page, the clone version will be deleted from all contexts.
After done some research on contexts, I can see their use specifically for multilanguage purposes, or for purposes where you need totally separate websites (in which case most people will probably go with separate modx installations, just in case something breaks it is localised to only one site)