How does the content hub exporter render entities?
When investigating the logic, I see ContentHubExportQueueBase::processItem() calls to ContentEntityCdfNormalizer::normalize() using the acquia_contenthub_cdf, but I haven't been parse out or inspect the actual $ch_entity before its decoded, prepared for export by $exported_entity['entities'][$key] = Json::decode($ch_entity->json());.
Does the exported entity get rendered by Drupal somewhere within ContentEntityCdfNormalizer::normalize()?
If a site uses contrib or custom module or theme preprocessors to manipulate a rendered entity; are these invoked as part of the Content Hub Export process? If so, where? If not, how can we manipulate (e.g. add classes or data attributes) exported entity that used by Acquia Personalization (Lift) when changing content within slots?
Closed: outdated
1.48
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Lift is now using a totally different approach which no longer relies on Content Hub: https://www.drupal.org/project/acquia_perz → and https://docs.acquia.com/personalization/personalization-module/
I believe this issue can be closed, unless I'm missing something.
Also CH1 is about to be deprecated.