David Glick

@jensens I tried it and see output like this: ``` DOMAIN 'zope' (topic Applications) Zope and Plone application related TARGETS zope-instance zope-start zope-debug zope-runscript zope-adduser zope-dirty zope-clean zope-purge ``` Is...

@ramiroluz Thanks for testing it. > I am testing it and the build process took me several minutes (in the first run). Looks too slow for using in a training...

@wesleybl @avoinea I think it is backwards compatible and could be backported. If someone prepares the PR I can review it.

@jnptk @tisto I like this feature, but I have some doubts about putting it in Site Setup, because: 1. It's a tool for reviewing / editing content, not for changing...

@plone/volto-team My thoughts on contextual vocabularies: There are some situations where it is important to fetch the vocabulary in the correct context. But, we only want to do that when...

> pnicolli: What if we just let the developer decide? We add a parameter to getVocabulary and we decide it based on where it is used, instead of adding more...

@tiberiuichim I am talking about `@querystring` (which gets info about the available indexes), not `@querystringsearch`

@ericof There is a PR which is almost ready: https://github.com/plone/volto/pull/6236 It just needs docs for the new setting.

> I have no clue where to document this feature... @sneridagh I guess either https://6.docs.plone.org/volto/backend/index.html or a new section in https://6.docs.plone.org/volto/blocks/index.html

@stevepiercy It's an extension mechanism for addons to make changes to content data as it arrives from the backend.