<h3 id="summary-problem-motivation">Problem/Motivation</h3> Add a new FieldFormatter plugin to output text fields as a <code> <details> / <summary></code> group. <strong>Initial use case for Standard profile:</strong> in [#3002770] there is a plan to add a transcript field to some media bundles. A details element is a compact, unintrusive way to present the transcript close to the video. See a demonstration in comment #4. Aside from that, it's a general purpose formatter to help authors make good use of a standard HTML element. A few other potential uses: <ul> <li>Events - a "venue address" field.</li> <li>Commerce products - a "size info" field.</li> <li>User profiles - a "contact details" field.</li> <li>A long-text-with-summary could populate the <code><summary></code> using token replacement from the sub-field.</li> <li>Paragraphs - a question-and-answer paragragh type, with two fields for the question and answer. The answer field would use the details/summary formatter, configured to show the question as the <code><summary></code> via token replacement. (See comment #10 for a demo.)</li> <li>Long accessible descriptions for complex images. A flowchart accompanied by a rich text alternative in a collapsed details element. Comment #5 elaborates.</li> </ul> <h3 id="summary-proposed-resolution">Proposed resolution</h3> The FieldFormatter plugin will have some relevant settings: <ol> <li>A checkbox setting controls whether it is should be open or closed initially, i.e. the <code><details open></code> attribute.</li> <li>Text of the <code><summary></code> element. will follow this order: <ul> <li>Custom text specified by the site-builder.</li> <li>The field label if no custom text specified</li> <li><del>Others? Maybe leave that possibility open for contrib.</del> Maybe could be follow-up</li> </ul> </li> <li>As a highly desirable bonus, the summary text can support token replacements from the parent entity. Patch #3 included this, and there is a demo in comment #10. <strong>Deferred, needs follow-up issue.</strong></li> </ol> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Implement the formatter.</li> <li>Needs follow-up issue to add token support (and tests) for the summary text.</li> <li>Tests.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> TODO place screenshots <h3 id="summary-api-changes">API changes</h3> None. <h3 id="summary-data-model-changes">Data model changes</h3> Just the necessary addition to config schema for the new formatter settings.