I am currently working on a prototype and would like to collect some feedback. The current state can be checked out at https://github.com/CORE4/neos-development-collection/tree/contentcontext-detection
The implemented concept and prototype add three (non-breaking) changes:
Additional configuration options are available:
possible detection modes are
subdomain. Thus de.seller-a.ch/18-49/ can be resolved to language German, seller A, market Switzerland and targetGroup 18 to 49 years.
A new routing interface is introduced: the
ContentDimensionPresetDetectorInterface. It is used in the
FrontendRoutePartHandler and is passed the current request’s URI, the request path and some configuration and extracts the dimension values from that information.
I’m not 100% happy with this since it exceeds the capabilities of a regular route part handler since it requires more information than given, but it works nontheless since it is still capable of adjusting the route path as expected.
Again, the route part handler has to be adjusted to only respect dimensions that use detection mode
The most significant change is to the
LinkingService, though. It needs to be able to detect whether a new base URI is required and if so, what it must look like. Note that links might have to be created absolutely although the parameter is set to false.
@core team: Do you agree with the course of action in general? Note that this is a prototype and implementation details are still subject to change
Also, did I miss any points in the code base that have to be adjusted?