Frontpage

A list of nodes marked for display on the front page.

We should change ‘marked’ to ‘promoted’. It's more consistent with the checkbox label and less ambiguous.

Recent comments

A block and a page with recent comments.

We are reiterating information that is provided in another column. We don't do this anywhere else and this requires the user to update the description if they add another display.

Taxonomy term

Customize the default taxonomy/term display.

I assume this will change once it replaces the core output? Either way I think adding ‘vocabulary’ and replacing the ‘/’ with ‘or’ would be more descriptive. We could probably rewrite this description to be more descriptive of the view itself, for example: 'a list of content contained within a taxonomy term or vocabulary'? We would also need to update the title to be more generic or include vocabularies.

Archive

A list of months that link to content for that month.

I feel like this should be more consistent with Glossary.

Glossary

A list of all content, by letter.

I only included this for reference but it's worth pointing out that four of the descriptions start with ‘A list...’ and three do not. All of these views are lists, we should decide whether this information is redundant or not.

Backlinks

A list of other content items which have a link to the content item.

The description here is from the perspective of someone viewing a resulting page of the view (node/%/backlinks), hence ‘the content item’ seems to assume that the user has a particular node in mind. If you take the perspective of some viewing the view edit page, which is responsible for creating every resulting page, I think you would end up with something similar to my suggestion for Taxonomy above: 'a list of content which have a link to a content item'

Files: 
CommentFileSizeAuthor
#23 copy-improvements-to-default-views-1958754-23.patch2.75 KBemma.maria
PASSED: [[SimpleTest]]: [MySQL] 58,836 pass(es).
[ View ]
#17 copy-improvements-to-default-views-1958754-17.patch2.74 KBemma.maria
PASSED: [[SimpleTest]]: [MySQL] 58,572 pass(es).
[ View ]
#10 copy-improvements-to-default-views-1958754-10.patch2.89 KBgreyrhino
PASSED: [[SimpleTest]]: [MySQL] 58,425 pass(es).
[ View ]
#7 copy-improvements-to-default-views-1958754-7-with-comment-description.patch1.94 KBgreyrhino
PASSED: [[SimpleTest]]: [MySQL] 56,046 pass(es).
[ View ]
#7 copy-improvements-to-default-views-1958754-7-without-comment-description.patch2.39 KBgreyrhino
PASSED: [[SimpleTest]]: [MySQL] 55,394 pass(es).
[ View ]
#5 copy-improvements-to-default-views-1958754-5.patch2.39 KBgreyrhino
PASSED: [[SimpleTest]]: [MySQL] 55,762 pass(es).
[ View ]
#4 copy-improvements-to-default-views-7350890-4.patch2.39 KBgreyrhino
PASSED: [[SimpleTest]]: [MySQL] 55,615 pass(es).
[ View ]

Comments

LewisNyman’s picture

I've also suggested over in #1834576: Improve details on the Views listing page that we add tags to signify admin and front-end views. This feels more relevant in this issue and less likely to be dragged into a huge UI overhaul.

xjm’s picture

Component:views_ui.module» views.module
Issue tags:+Novice
greyrhino’s picture

Assigned:Unassigned» greyrhino

Currently looking into this.

greyrhino’s picture

Status:Active» Needs review
StatusFileSize
new2.39 KB
PASSED: [[SimpleTest]]: [MySQL] 55,615 pass(es).
[ View ]

Patch attached for review.

A couple of very minor deviations from the above suggestions to keep consistency that was more noticeable once the initial suggestions had been implemented.

greyrhino’s picture

StatusFileSize
new2.39 KB
PASSED: [[SimpleTest]]: [MySQL] 55,762 pass(es).
[ View ]

Wrong issue number on the patch file is comment #4. Correctly named/numbered file attached in this comment.

dawehner’s picture

Thanks for the patch!

+++ b/core/modules/node/config/views.view.frontpage.ymlundefined
@@ -1,7 +1,7 @@
+description: 'A list of nodes promoted for display on the front page.'

Do we really want to talk about "nodes"?

+++ b/core/modules/views/config/views.view.comments_recent.ymlundefined
@@ -1,7 +1,7 @@
+description: ''

That's odd, why do we want to have no description?

+++ b/core/modules/views/config/views.view.taxonomy_term.ymlundefined
@@ -1,7 +1,7 @@
+description: 'Customize the default taxonomy or vocabulary term display.'

or vocabulary? It always just displays terms and associated nodes.

greyrhino’s picture

StatusFileSize
new2.39 KB
PASSED: [[SimpleTest]]: [MySQL] 55,394 pass(es).
[ View ]
new1.94 KB
PASSED: [[SimpleTest]]: [MySQL] 56,046 pass(es).
[ View ]

Do we really want to talk about "nodes"?

I agree - all the other decsriptions use 'all content' so I have updated the Frontpage description to keep consistency.

That's odd, why do we want to have no description?

This was following the initial suggestion that we were repeating what was in the first column - though I think it looks tidier with something in the description column - so i have attached two patches. One has a description and the other does not - they are suitable named.

or vocabulary? It always just displays terms and associated nodes.

You're right - i had seen that there was an option for the view to accept two arguments so assumed that the above suggestion fitted. But as the optional second argument is depth then I have amended the description to remove 'or vocabulary'.

dawehner’s picture

+++ b/core/modules/views/config/views.view.taxonomy_term.ymlundefined
@@ -1,7 +1,7 @@
+description: 'Customize the default taxonomy term display.'

What about: A list of content belonging to a certain taxonomy term?

yoroy’s picture

Status:Needs review» Needs work

I like that suggestion and would suggest to make that 'A list of content that belongs to a certain taxonomy term'.

Re: "A list of all content which have a link to a content item." I don't see how that improves on "A list of other content items which have a link to the content item." ?

greyrhino’s picture

StatusFileSize
new2.89 KB
PASSED: [[SimpleTest]]: [MySQL] 58,425 pass(es).
[ View ]

What about: A list of content belonging to a certain taxonomy term?

Yes, that does make sense. I have amended the patch accordingly - though have used the syntax from comment#9 as 'that belongs' seemed to look better than 'belonging'.

There is also only one patch now - with comment description - as the description column scans more easily if it's not blank. The comment description has been amended to more closely match the others.

After this the only one that wasn't in keeping was the 'Tracker' row so I have amended that to 'A list of all new activity on the system'. I kept activity rather than use content as, after chatting to a colleague, it did seem the correct to use term.

Re: "A list of all content which have a link to a content item." I don't see how that improves on "A list of other content items which have a link to the content item." ?

As taxonomy now uses '... to a certain taxonomy term' should whichever is chosen from the above use '... a certain content item' - as these both take wildcards so should share the same convention where 'certain' implies the provided value?

My preference would be: 'A list of all content which have a link to a certain content item.' - this is what is in the patch file.

BTW: should I provide a patch each time or is it normally better to let the discussion take it's course and just provide a patch when there is a consensus? This is my first patch so didn't want to fill the thread with unnecessary files.

dawehner’s picture

+++ b/core/modules/node/config/views.view.frontpage.ymlundefined
@@ -1,7 +1,7 @@
+description: 'A list of all content promoted for display on the front page.'

Just wondering whether "A list of all content promoted to the front page." would be even shorter and easier to read.

+++ b/core/modules/views/config/views.view.backlinks.ymlundefined
@@ -1,7 +1,7 @@
+description: 'A list of all content which have a link to a certain content item.'

What about this: "A list of all content referenced on another content."?

+++ b/core/modules/views/config/views.view.comments_recent.ymlundefined
@@ -1,7 +1,7 @@
+description: 'A list of all recent comments.'

Not sure whether 'all' is required. It confuses me a bit, just because all recent comments would be also all comments.

+++ b/core/modules/views/config/views.view.taxonomy_term.ymlundefined
@@ -1,7 +1,7 @@
+description: 'A list of all content that belongs to a certain taxonomy term.'

Yeah the same point can be made here as well.

greyrhino’s picture

Status:Needs work» Needs review

Just wondering whether "A list of all content promoted to the front page." would be even shorter and easier to read.

I've just tested it in Chrome and unfortunately it still wraps over two lines - would be even better on just one - but it is easier to read and none of the other descriptions mention display even though they all do so will remove as per your suggestion.

What about this: "A list of all content referenced on another content."?

This doesn't work for me using 'referenced on' - mainly the on word. Trying it again it sounds better to me to say something like "A list of all content with links to a certain content item". Not sure for the average user if links or references is better?

Not sure whether 'all' is required. It confuses me a bit, just because all recent comments would be also all comments.

Is there any reason to use the word 'all' on any of them? They all make sense without it:

A list of all content promoted to the front page.
A list of all content, by month.
A list of all content which have a link to a content item.
A list of all content, by letter.
A list of all recent comments.
A list of all content belonging to a certain taxonomy term.
A list of all new activity on the system.

vs

A list of content promoted to the front page.
A list of content, by month.
A list of content which have a link to a content item.
A list of content, by letter.
A list of recent comments.
A list of content belonging to a certain taxonomy term.
A list of new activity on the system.

vs (and mentioned in the original authors comment)

Content promoted to the front page.
Content, by month.
Content which have a link to a content item.
Content, by letter.
Recent comments.
Content belonging to a certain taxonomy term.
New activity on the system.

I prefer the last version because it does away with duplication and scans very quickly - but equally the middle version is still quicker to scan.

jibran’s picture

jibran’s picture

Status:Needs review» Needs work

NW for 12.1 and for some more discussion.

LewisNyman’s picture

Assigned:greyrhino» Unassigned

I think “list” is redundant. “All” seems useful because it differentiates from the views that are filtered by time, the “recent” views .

I'd be happy to RTBC a patch with the following:

All content promoted to the front page.
All content, by month.
All content which has a link to a content item.
All content, by letter.
Recent comments.
Content belonging to a certain taxonomy term.
New activity on the system.

emma.maria’s picture

Assigned:Unassigned» emma.maria
emma.maria’s picture

Status:Needs work» Needs review
StatusFileSize
new2.74 KB
PASSED: [[SimpleTest]]: [MySQL] 58,572 pass(es).
[ View ]

I have replaced the descriptions using the list in #15.

Bojhan’s picture

Status:Needs review» Reviewed & tested by the community

I think this is a good solution, we should fix this. I am sure we can do much more tweaking but I'd like to move this issue to core.

damiankloip’s picture

+1, why not.

yoroy’s picture

These are good and useful tweaks, go for it.

webchick’s picture

Status:Reviewed & tested by the community» Needs work

Unfortunately no longer applies.

jibran’s picture

Issue tags:+Quick fix, +Needs reroll

Tagging for reroll.

emma.maria’s picture

Status:Needs work» Needs review
StatusFileSize
new2.75 KB
PASSED: [[SimpleTest]]: [MySQL] 58,836 pass(es).
[ View ]

Rerolled :)

Emma

dawehner’s picture

Status:Needs review» Reviewed & tested by the community

Great, let's get it in now!

webchick’s picture

Status:Reviewed & tested by the community» Fixed

Great work! :)

Committed and pushed to 8.x. Thanks!

Bojhan’s picture

Assigned:emma.maria» Unassigned

Nice job @emma!

Xano’s picture

Issue tags:-Needs reroll

Automatically closed -- issue fixed for 2 weeks with no activity.