Rob Moorman

Still getting this issue, tried all steps: - yarn workspaces (via lerna) - checked if there is one react dep, yes Some things that can have impact: - using webpack...

We used this already in Wagtail: http://docs.wagtail.io/en/v1.10/reference/contrib/frontendcache.html#amazon-cloudfront. Reference: https://github.com/wagtail/wagtail/blob/01e891d0c458b8eaf46fa7ddf19900bfd12c0a31/wagtail/contrib/wagtailfrontendcache/backends.py#L109 The trickiest part is so support multiple CloudFront distributions depending the url/site.

Nope it doesn't. But the idea how they handle multiple backends is a good example.

Maybe a more universal solution, like any custom url render to static files so it's not limited to sitemaps.

I think we don't want to prefix locale paths in the build paths as it's up to the developer how to construct their url's (e.g. separate domains / third-party cms's)....

Would be nice to keep https://developers.google.com/search/docs/advanced/crawling/localized-versions#sitemap in mind

Hi @nasuru1 in which way this is a security risk, can you please elaborate? Besides the CTRL+L this still applies; by opening a new tab the end user expects to...

See also #135

This requires to have tags to be attached to a Page, which currently isn't the case. Would it be feasible to have a e.g. ``SegmentedPersonalisablePage`` which has a panel for...

Jeah I agree. I've implemented such before when using Aws Machine Learning to predict Page objects based on 'segments'. In this case a Panel 'Segments' was shown on the edit...