[Note: I'm aware of #553308 "Clean up UI for 'Text with summary' field settings." That patch is mostly about the UI for setting up a field that has a teaser component. It has implications for the node/add/ as well in that you can set the "summary" field to display by default. The issue I'm opening here is different because it's about strings and not functionality.]
Background
There are two use-cases which would require someone to use the "summary" functionality:
- User wants teaser text to be different from full text. A common example is when a listing page will list a title and description of an article, not the beginning of the article which is what would happen if the summary functionality were not used.
- User wants precise control over how much text gets in to teaser. On the content-type admin page (so much better than on the now defunct "Post settings" page), you can set the automatic trimming length. However, many users want more precise controls and the ability to override. Many content editors will also not have the permission to edit the content-type admin page.
Proposal to replace "summary" with "teaser"
"Teaser" is better than "Summary."The word "summary" relates to use-case #1 above but not at all to use-case #2. The word "teaser" applies to both use-cases and so this issue is proposing that "teaser" replace "summary" on the node/add form and on the content-type settings.
Some arguments
- Given the auto-trimming features of Drupal, one might argue that use-case #1 above is far more prevalent and so we should not change terminology because #2 is really an edge-case. In my experience, clients are much more likely to use "summary" type functionality for use-case #2. In those cases, the "summary" language becomes a barrier to learning.
- Even for use-case #1 above, I believe that a lot of content-editors and especially marketing types will hate the word, "summary." If you are writing short text that will appear in a list, and the purpose of that text is to entice someone to click through to the article, the last thing you want to do is write a "summary" of the article. It's likely to be too long and boring. The word "teaser" is absolutely perfect for this. The fact that teaser can connote both "beginning" as well as "enticement" makes it the perfect word for this purpose.
- Some might say that the "teaser" in Drupal (as per Views and elsewhere) is talking about more components than the "summary" field. It also refers to the title and possibly the links that go with it. If people are concerned about that, I would propose, "Teaser text" as an alternative to "Teaser."
For all these reasons, I think "summary" is a bad and confusing choice and should be replaced by "teaser."
Comments
Comment #1
Bojhan commentedI like the thought you have given the rationale. I am inclined to disagree though, from the user tests we now did with this interaction - no one seemed confused over the word Summary. To provide feedback on the arguments.
1. I do not see, how changing this label now gives use case #1 more prominence over #2.
2. Right, I think this arguments holds up. I think the biggest worry was that, teaser does indeed have a positive effect in the copy-editing world. I am wondering though, if we are truely thinking about the whole of our audience with that though. Is teaser to be conciderd lingo, to others? Especially non-native spakers.
3. I agree, and hence why changing it back to Teaser would be confusing - as the boundries between those tools and this is lowering. However this doesn't seem like an argument for anything? Teaser text is somewhat wierd?
Eitherway, I am somewhat puzzeld by this issue. Is it really that big of an issue, have we seen actual users confused over this? Since, I havn't and although its usually unpopular to step away from lingo, I believe in this case it will widen our audience to more people.
Comment #2
Tor Arne Thune commentedStill a valid issue. Moving to 8.x, as this changes UX.
Comment #3
colanBetter yet, toss it completely. See #1378350: Clean up the "Long text and summary" field for details.
Comment #4
Shai commentedI'm inclined to agree with @colan. If that happened, this issue might transform into one which desires to add to the standard installation profile an imitation of the long text with summary functionality using only two long-text fields. And it would apply only to the "article" content type.
Comment #16
smustgrave commentedClosing out as outdated based on comments #3 + #4. Seems all work will go under https://www.drupal.org/project/drupal/issues/1378350
If you feel this is still an issue please reopen.