Indicate which fields of the content type go into the active view mode that are currently displayed

Created on 15 March 2023, almost 2 years ago

Updated 26 March 2023, over 1 year ago

Problem/Motivation

At first a double thumbs up and a thank you for the creation of this module! While watching the video on Loom I wondered about one detail. From an educational perspective it might be very helpful to illustrate which fields out of the ones available in a content type go into the preview of the selected and active view mode. That way the user would also be able to switch in-between view modes and understand the inner workings of a content type and understand which fields of the content type go into which view mode.
But aside the educational and demonstrational aspect it would also provide a certain degree of visual feedback and control for more experienced users and content editors in particular to recall which fields out of the ones available in a content type actually build a the current page aka fuel the current view mode. With that reminder the fields in question could be easier and more conveniently compared with the output in the preview for quality assurance and seeing the content in question in the visual context.

Steps to reproduce

Proposed resolution

the indication of the fields that go into a view mode probably shouldn't be done via the regular focus outline style. there should be a clear visual difference. and i wonder if it would make sense to have that feature active all the time. maybe adding the ability to dynamically activate or deactivate it via a checkbox might be the best bet.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request

Status

Postponed

Version

1.0

Component

User interface

Created by

🇩🇪Germany rkoller Nürnberg, Germany

Live updates comments and jobs are added and updated live.

Usability
Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Comments & Activities

Issue created by @rkoller
Comment over 1 year ago →
🇺🇸United States brianperry
Interesting idea. This also might have the side effect of allowing us to save preview data to the temp store more efficiently. If the currently edited field isn't being displayed, we could defer updating the temp store until it would have a visual impact.
Comment over 1 year ago →
🇺🇸United States cosmicdreams Minneapolis/St. Paul
This issue feels like it would be tackled when we're focusing in on Phase 2: Update preview when someone finishes editing a field. Perhaps we should start creating an epic for issues that are targeted for that phase.
Status changed to Postponed over 1 year ago10:40pm 26 March 2023
Comment over 1 year ago →
🇺🇸United States cosmicdreams Minneapolis/St. Paul
Postponing to focus on other issues. We'll have to hash this out in phase 2.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024