Alexandre Capt

I have tried v14.17.5 and v16.9.1. Same for both.

``` browserify: "17.0.0" resolve: "1.20.0" is-core-module: "2.6.0" ```

Sorry I summarised but with node 16, I only get: ``` Error: Can't walk dependency graph: ENOENT: no such file or directory, lstat '[...]/node:url' required by [...]/node_modules/hast-util-to-mdast/lib/util/resolve.js ``` with node...

> We're getting started today with https://github.com/adobe/spectrum-web-components/pull/2292. 😬 Nice, thanks a lot. > 2. "require other components" Half of the components have a dependency. Example: https://opensource.adobe.com/spectrum-web-components/components/quick-actions/ To get the example...

If you do a "Personalisation Block" (I made a prototype, that's the first I have done :) ), you will need to put the other blocks inside - or make...

> `window.addEventListener('helix-audiencechanged', (evt) => console.log(evt.detail);` I know by experience that this is the start point of an event mess: everybody listens and everybody fire events on each change. The time...

The reason we design it event base (I built the feature 2 times already that way...) is because we start by the simulation: you want to update the page on...

> 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. That's definitively a fair...

Minor concern: if the server gives me a `helix-card` in my DOM, I would assume this is a standard "helix" component shared across all projects with a predefined structure... But...

The current translation tool is running as a pilot on the Fedpub project. This is something we could work with @narcis-radu and @mokimo.