Closed sneridagh closed 1 month ago
Name | Link |
---|---|
Latest commit | 5804188435229d27c454c788a92723c22c4a734f |
Latest deploy log | https://app.netlify.com/sites/plone-components/deploys/6719548a4ff3b80008f91474 |
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
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
I would follow @davisagli's suggestion, as I have no clue what this thingie is!
@stevepiercy It's an extension mechanism for addons to make changes to content data as it arrives from the backend.
Gotcha. I think in Integration with the backend for sure.
However, I'm not sure how it relates to Blocks. Do we have a diagram and narrative similar to Pyramid's Request Processing, where one can see where this thingie fits into the entire process? I created that diagram, and its source is available as SVG, if we want to adapt it for Plone and Volto.
@davisagli @stevepiercy I added some docs.
@stevepiercy right now it's super simple, a function in the middle of the whole pipeline. I don't know if we need further bells and whistles for now...
I have no clue where to document this feature...
If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.
Closes #