Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
After #2873576: Add description field to ParagraphType is committed, paragraphs types can have descriptions. Let's add some to our pre-existing paragraphs types in the Paragraphs Demo module.
Proposed resolution
In each of these configuration files
paragraphs.paragraphs_type.image_text.yml
paragraphs.paragraphs_type.images.yml
paragraphs.paragraphs_type.nested_paragraph.yml
paragraphs.paragraphs_type.text.yml
paragraphs.paragraphs_type.text_image.yml
paragraphs.paragraphs_type.user.yml
add the line description: {description}
, where "{description}" is an appropriate description for that paragraphs type.
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#7 | demoparagraphsdescription-2876597-7.patch | 3.2 KB | aheredia |
#3 | demoparagraphsdescription-2876597-3.patch | 3.15 KB | aheredia |
Comments
Comment #2
VladimirMarko CreditAttribution: VladimirMarko commentedComment #3
aheredia CreditAttribution: aheredia commentedHere are the descriptions for the demo paragraphs
Comment #4
aheredia CreditAttribution: aheredia commentedComment #5
miro_dietikerInteresting, compared it with Drupal Core content type descriptions, that is for instance:
description: 'Use <em>articles</em> for time-sensitive content like news, press releases or blog posts.'
We said, we want to avoid using "paragraph type" in the UI. Following core, we could repeat the type name in emphasis.
Or we could simply say "Used for.."
In any case, as uniform as possible.
I don't like long duplicated information like paragraph type or meaningless things like "Use this paragraph to", but it still needs to be a full sentence. :-)
Comment #6
aheredia CreditAttribution: aheredia commentedThanks for the suggesions.
I'll try to improve descriptions being as uniform as possible.
Comment #7
aheredia CreditAttribution: aheredia commentedWhat do you think?
Comment #8
aheredia CreditAttribution: aheredia commentedComment #10
miro_dietikerThx, committed. :-)