While reviewing the Plone v6 documentation (User Guide, Editor Guide, and Volto UI docs), I noticed that editor-focused documentation currently exists mainly as global, external documentation pages.
However, I could not find any integrated mechanism for providing field-level, contextual editor guidance directly inside the editing UI (for example, attaching organization-specific documentation or guidance to individual fields or block settings).
My understanding of the GSoC idea around providing more documentation to editors is that it aims to address this gap by embedding contextual documentation into the editor experience itself — so that editors can access rules, tone guidelines, examples, or policies at the point where content decisions are made.
For reference, similar field-level contextual help patterns are commonly used in tools like Google Forms, WordPress (ACF), Jira, or Salesforce, where help icons or inline guidance are attached directly to specific fields to reduce confusion and improve usability.
Is this understanding correct, and is the intended scope of this GSoC idea primarily focused on Volto (for example, block configuration panels and metadata fields), backend forms (z3c.form), or a combination of both?