Lars Trieloff

> The "audience row" would be extracted before block handling logic which means the block code would receive the same dom as before > […] and providing a way to...

Given that we have only one personalization use case so far, I'd be fine with having one single personalizable block over the more general solution.

Feedback appreciated: - would the ability to generate `sitemap.xml`s be useful or don't we know enough yet? - we could implement the whole thing (except for filters) using Compute@Edge -...

Feature requests that come with a PR are my favorite. From a quick look at your commit, it looks good – I would just flip the `yargs` argument configuration: make...

Do we have a way of getting the response time distribution (ms to first byte would be ideal) from Coralogix? Once we know the real response time distribution, we can...

Supported in all browsers relevant for Helix https://caniuse.com/mdn-api_window_customelements

As of https://github.com/trieloff/superdevoluy/commit/ce4c9f00b29ab446cd242b4260d14ed432a39797 all blocks have been ported to custom elements.

After the complete porting, I've tried some more variants: 1. Eager Loading of Custom Elements (each custom element has a `script` tag before use) like this: https://github.com/trieloff/superdevoluy/blob/8d85a67e15b90f210c9e7f412e0b587a9c7c006a/index.html#L15-L16 2. Lazy Loading...

Great points. > note that this puts extra strain on `helix-static`. We can also consider creating a new `helix-image` action for that. But in general, ahead-of-time metadata extraction beats just-in-time...

yes, I'd reopen adobe/helix-static#88 if we start with asynchronous asset processing, would it make sense to process with NUI?