Víctor Fernández de Alba

@pnicolli @wesleybl luckily we have this written down: https://6.docs.plone.org/volto/release-management-notes/index.html#dom-structure-and-default-styling Yes, it is a breaking change and should be documented as one properly. Also, this makes it non-backportable to 18. As...

@pnicolli you are right, let's remove the addition to `@plone/components` for now. I didn't realise of this fact. Could someone take care of it?

@davisagli I think this can be closed, some of the whishlist are already fulfilled or outdated/no sense in the current implementation. If needed, we can open a new PLIP for...

> [!IMPORTANT] > If you are not a member of the Volto Team or Developers Team in the Plone GitHub organization, then do not work on or comment on this...

@wesleybl I agree, let's create one. Also, in VLT I'm adding a wrapper for blocks, that even pulls the `StyleWrapper` for the blocks. @Tishasoumya-02 maybe it would be useful to...

@JeffersonBledsoe so as a plain member user I am able to see other's info? I guess by default this is not possible, right? Even in classic. Sorry for not taking...

@silviubogan did you see my comment yesterday in the other issue, right? We are not encouraging that people use the core checkout in this way. I think I left it...

> Unfortunately we lack universal documentation, although we have this for Volto https://6.docs.plone.org/volto/upgrade-guide/index.html#upgrade-18-cookieplone-label. We also have to contend with the [Plone Upgrade Guide](https://6.docs.plone.org/backend/upgrading/index.html). Let's chat to figure out what is...

@fredvd Are you preparing documentation about this, right? Do you plan to add it to the Plone docs?

Leaving this open, since I really think we could get back to it at some point in the future, and the code is really amazing. However, there are also third...