Problem/Motivation

New users don't know where to go to add new content types. Everyone starts by clicking on the "content" link in the Toolbar (sometimes, repeatedly) and struggles with this being almost the right place do to what they want. Here's a video of one participant from the Google Usability studies struggling with where to go to add a new type of content and again after hes already been there once, and again a third time.

Proposed resolution

Add a "+ Create content type" action link at the top of the content listing page (admin/content) for privileged users

Related Issues

Files: 
CommentFileSizeAuthor
#59 Screen Shot 2017-01-28 at 12.57.07 PM.png62.92 KBahughes3
#55 add_a_create_content-1440678-55.patch417 bytesmandclu
#39 Add_content___d8_local_test.png56.26 KBaburrows
#39 Content___d8_local_test.png59.92 KBaburrows
#39 add_a_create_content-1440678-39.patch445 bytesaburrows
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 114,130 pass(es). View
#32 add_a_create_content-1440678-31.patch583 bytesCinnead
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,666 pass(es). View
#27 addcontentafter1.png59.17 KBandymartha
#27 addcontentafter3.png40.41 KBandymartha
#17 1440678-before.png94.91 KBdastagg
#17 1440678-after.png95.97 KBdastagg
#17 1440678-node-add.png83.85 KBdastagg
#14 add_action_link_for_type-1440678-14.patch667 bytesjenlampton
PASSED: [[SimpleTest]]: [MySQL] 36,661 pass(es). View
#10 1440678-add-content-type-9.patch665 byteslarowlan
PASSED: [[SimpleTest]]: [MySQL] 34,324 pass(es). View
#10 Selection_017.jpeg30.95 KBlarowlan
#10 Selection_018.jpeg38.18 KBlarowlan
#8 1440678-add-content-type-8.patch684 byteslarowlan
PASSED: [[SimpleTest]]: [MySQL] 34,320 pass(es). View
#6 1440678-add-content-type.patch596 byteslarowlan
PASSED: [[SimpleTest]]: [MySQL] 34,336 pass(es). View

Comments

jenlampton’s picture

Issue summary: View changes

added a second instance

jenlampton’s picture

Issue summary: View changes

added 3rd example

jenlampton’s picture

Issue summary: View changes

make links easier to read.

webchick’s picture

Priority: Normal » Major

Yes please!

a_thakur’s picture

I think it is a nice usability feature. I would like to work on this feature-request.

Thanks
Ashish

a_thakur’s picture

Assigned: Unassigned » a_thakur

I would like to work on this issue. A good usability feature and good issue for a novice to work upon.

Thanks
Ashish

Bojhan’s picture

Priority: Major » Normal

This is important, but not major - a large number of people have difficulty finding it and navigate to this page , but it rarely stopped them from actually finding it. From my perspective major and critical is only to be used for issues, that prevent people from using the functionality - its the criteria we have used in past issues, unless we use new criteria I think this should be normal.

This was also found in http://groups.drupal.org/node/159444 testing.

This might introduce kind of a "hack" until we make this a global Drupal pattern. Because we don't list to "related topics" in actions, I strongly wonder if placing it at node/add is more useful.

jenlampton’s picture

I thought about that, but We don't really have any other interface that would follow this pattern. Theres no UI for user "types" in core, term "types" are vocabularies, and menu item "types" are menus. I think this is the only interface that needs an additional action link, and also the most important.

larowlan’s picture

Assigned: a_thakur » larowlan
Status: Active » Needs review
FileSize
596 bytes
PASSED: [[SimpleTest]]: [MySQL] 34,336 pass(es). View

sorry a_thakur, was working on this before I realised you'd bagged it.

larowlan’s picture

I'd advocate that this link also belongs on node/add (patch to follow).

larowlan’s picture

FileSize
684 bytes
PASSED: [[SimpleTest]]: [MySQL] 34,320 pass(es). View
Bojhan’s picture

Issue tags: +Needs screenshots

Screenshots please :)

larowlan’s picture

FileSize
38.18 KB
30.95 KB
665 bytes
PASSED: [[SimpleTest]]: [MySQL] 34,324 pass(es). View

This patch fixes comment.
Also attached - screenshots

David_Rothstein’s picture

Title: Add a "Create content type" link to content listing page (for privileged users) » Add a "Create content type" link to the content listing page and/or the add content page

I agree with Bojhan. The basic pattern we currently have is that pages which list things of type X get an action link for adding a new X at the top. Adding this link to node/add is consistent with that pattern. Adding it to admin/content would violate it.

Another problem with adding it to admin/content is that we then get two action links on the same page (as seen in the screenshot), which is discouraged according to http://drupal.org/node/1089894. And we know the "Add content" link is very helpful there, so adding another link that people could confuse it with seems risky.

It's also not clear to me how adding this link to admin/content would even solve the problem shown in the videos - seems like a lot of what he was doing there was trying to find existing content types rather than add a new one? (And therefore, he got confused between the page that listed his content and the page that listed his content types.) Seems like a different problem.

a_thakur’s picture

#8: 1440678-add-content-type-8.patch queued for re-testing.

Barry Madore’s picture

I'm confused as to the direction of the last few patch submissions but have done some testing. I tested the patch in #10 1440678-add-content-type-9.patch can confirm that it adds a "+ Add a content type" action link to both node/add and admin/content. It does not, as the comment implies:

// Add 'Add Content Type' action link to admin/structure/types/add.

I don't have the capacity to commit a new patch with a more accurate comment but would recommend that this be done. I can confirm that the screenshots in #10 are accurate.

However, after reviewing the comments related to the usability issue this patch is designed to improve, I agree with David_Rothstein in #11. I feel this change would be confusing and lead to more problems. I've encountered a number of Drupal sites where the site builder created content types when they should have created pieces of content. I believe the change suggested in this issue and implemented in the patch would encourage this behavior.

After applying the patch I tried the links from both new places. Another potential confusion will likely arise when a site builder uses the "+ Add a content type" from the node/add page and is delivered to the http://d8core.localhost:8082/admin/structure/types page rather than back at the node/add page where they started.

I'm not sure this is the right solution to the stated issue.

jenlampton’s picture

FileSize
667 bytes
PASSED: [[SimpleTest]]: [MySQL] 36,661 pass(es). View

@David_Rothstein check out the 2nd and 3rd video links (maybe the first wasn't so clear), in both cases the user was trying to find the content types page, and clicked on "content" in the menu instinctively.

I worry that adding a create content types link might encourage people to create types when they meant to create content, but I think the problem we have now - users not knowing that creating new types is even possible - is much worse.

Patch re-rolled with updated comment, as per #13 :)

Status: Needs review » Needs work
Issue tags: -Usability, -Novice, -Needs screenshots, -GoogleUX2012

The last submitted patch, add_action_link_for_type-1440678-14.patch, failed testing.

Barry Madore’s picture

Status: Needs work » Needs review
Issue tags: +Usability, +Novice, +Needs screenshots, +GoogleUX2012
dastagg’s picture

Issue tags: +tcdrupal2012
FileSize
83.85 KB
95.97 KB
94.91 KB

Applied patch and created screen prints

Not sure if it is ok as at the time I looked at this #16 re-queued the #14 patch for testing but the #14 patch was green so not sure.

But, here are the screen prints to see if it is the intended result.

It does add the + Add content type to the admin/content page plus it also adds + Add content type to the node/add page.

dastagg’s picture

Assigned: larowlan » Unassigned
Status: Needs review » Reviewed & tested by the community

After speaking with larolan, the #14 patch is okay.

There still seems to be some indecision as to whether this is the right way to go but the patch does what #14 states it is supposed to do.

Dries’s picture

Playing devil's advocate here for a second: is 'Create content type' the right action?

What if in the usability testing, the user was instructed to change an existing content type? I think he/she would still be lost. Should it be 'Administer content types' instead?

Bojhan’s picture

These are action links, not links to administrative lists - I don't think we really want to break that pattern.

I suggest we reconsider this feature, as #11 and #4 are not adressed. And testing did point out where people look for "content type" configuration, but not explicitly adding.

larowlan’s picture

I see the distinction between the two (one is adding, the other is configuring).
Perhaps we need a different class of localized links for configuration, with a different icon - eg a spanner or a gear.
Yes I know contextual links are for this purpose but they might be missed in this case.
Thoughts?

David_Rothstein’s picture

Status: Reviewed & tested by the community » Needs review

Sounds like things are still being discussed here. Moving the status back.

bendev’s picture

tested patch #14 works fine.
status can be passed to rtbc

cweagans’s picture

YesCT’s picture

YesCT’s picture

Issue summary: View changes

clean up grammar and linebraks.

dcam’s picture

I'm amazed. The patch still applies. I don't know if this can make it into D8 or not, given that it's a feature request. It seems more like a task to me though, especially given the apparent severity of the problem. Perhaps I'm mistaken.

andymartha’s picture

Issue tags: -Needs screenshots
FileSize
40.41 KB
59.17 KB

addcontentafter1.png
addcontentafter3.png

Here are some screenshots for a fresh install of Drupal 8 and applying patch add_action_link_for_type-1440678-14.patch in #14 by jenlampton . The patch adds the links/buttons for cross-linking the "add content type" on the pages shown.

yoroy’s picture

Status: Needs review » Needs work

The same issues still stand though

- This shouldn't have to be an action link. The content types listing page seems like a better destination and you get the 'add content type' link there for free as well
- Making it a non-action link means we can't add it where it is now.
- We don't have a pattern for 'also see this page here' type of links
- Or do we? Tour module to the rescue?

larowlan’s picture

larowlan’s picture

Issue summary: View changes

added related issues section

xjm’s picture

Component: node.module » node system
Issue summary: View changes

(Merging "node system" and "node.module" components for 8.x; disregard.)

Cinnead’s picture

Assigned: Unassigned » Cinnead
Cinnead’s picture

FileSize
583 bytes
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,666 pass(es). View

Resurrecting this thread because the main issue is still in place.
Users will still be easily confused as to where they need to go to add new content types.

Also added a new patch since the previous ones are out-of-date.

This will add the "Add content type" button to the "admin/content" page and only shows it to users with the correct permissions.

dcam’s picture

Status: Needs work » Needs review

Activating Testbot.

Cinnead’s picture

Assigned: Cinnead » Unassigned
Issue tags: +drupaldevdays
darol100’s picture

Status: Needs review » Needs work

@Cinnead,

I do not see the content type button. It seem unclear what you added into this patch. I was expecting a "Add content type" button at admin/content.

jeffrey.vargas’s picture

@darol100, I'm seeing the buttons on a fresh D8 install (beta 10) in both /admin/content and /admin/structure/types. From the earlier discussion it seems that the "add" button pertains to the specific area you're in, so you won't see the "Add content type" button on the /admin/content page. You'll see it in the content type admin page, /admin/structure/types

Checking this issue out at DrupalCon LA First Time Sprinters session

darol100’s picture

@jeffrey.vargas,

I'm also at DrupalConLA room 403. Feel free to join me.

Once again I have test it out the patch on #32 and did not work for me on a fresh installation d8 beta 10.

From the earlier discussion it seems that the "add" button pertains to the specific area you're in, so you won't see the "Add content type" button on the /admin/content page. You'll see it in the content type admin page, /admin/structure/types

Should we close this issue then ? Or should we add updated the issue ? I have added the tag to updated issue summary.

aburrows’s picture

Assigned: Unassigned » aburrows

Will add a create content type button to the admin/content page

aburrows’s picture

Status: Needs work » Needs review
Issue tags: -GoogleUX2012, -tcdrupal2012, -drupaldevdays, -Needs issue summary update +DrupalCon Barcelona 2015
FileSize
445 bytes
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 114,130 pass(es). View
59.92 KB
56.26 KB

This patch will add an Add content type button to admin/content and node/add

aburrows’s picture

Assigned: aburrows » Unassigned
espurnes’s picture

Patch #39 from aburrows works as expected. But not sure if it's a good idea to add the + content type button in this section.

LoMo’s picture

Re #41, I understand that sentiment, but I think that may be coming from the myopia of being too close to Drupal. If it helps new site admins/site-builders find what they need or shortens the number of clicks needed, it could be useful. Personally, I think we could have decided NOT to implement this at some point in the past years that this issue has been active. Now, if added and it bugs some Drupal expert, they could simply enough remove the button in their own sites.

So, personally, I'm in favor of this being marked RTBC. If it turns out that the new button is more confusing (in subsequent UX testing), we could re-think this or provide the option for site admins to hide the button, but I'd rather see us experiment and try making this change than simply discard the well-intentioned (and likely useful) effort that has gone into this.

That said, I'll leave this on "Needs review", if the community feels it warrants further discussion before it should be RTBC. But at least I have put in my 2¢. ;-)

lauriii’s picture

Is adding a new content type that common use case that it needs to have a link there? I'm not very convinced that this is the right solution for the problem. I would say administering content types is way more common use case than adding a new one. Seems like the UX maintainer has similar thoughts about this on #28.

It would be nice to see feedback from both, subsystem maintainer of Node module and UX.

David_Rothstein’s picture

There are several reasons pointed out in the above comments (including comments by both UX maintainers) explaining why this should not be an action link on admin/content. No one has addressed those, so I'm not sure this is really at a "needs review" state...

To summarize, it sounds like what we want on that page is some other kind of link (not an action link) that goes to admin/structure/types. From there they can configure existing content types or add a new one.

On node/add, an action link fits the pattern better, but still means there is no easy way from that page to configure the existing content types. So based on the above comments, the same kind of link to admin/structure/types would probably be better than an action link there too.

LoMo’s picture

Re #43, I agree that administering content types is far more commonly needed than creating a new one. An admin just doesn't need to add a new content type very often...

That said, it is the first thing a new Drupal site builder needs to figure out before they can do very much with Drupal, so I do think that extra links to make this harder to overlook are probably a step in the right direction.

Anyway, I agree that there is some room for improvement with regard to the UI/UX here. Clearly someone should not immediately see the "Add content type" button staring them in the face when that's not what they really need to do. Could we (easily) move the "Add content type" link down below in these areas so that it's not looking like the most obvious action to take? If this is not easily implemented, I would motion that we return this to RTBC and make "improving" the UX further the new issue. Too many people have done good work here to just have it sit for another 4 years... with new Drupal site admins just as confused when they want to add a new type of content as they ever were.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

yoroy’s picture

Version: 8.1.x-dev » 8.2.x-dev
Issue tags: +ux-workflow
mikeohara’s picture

I like having the new button present, but Perhaps it needs to be tweaked.

I might suggest that we prioritize the calls to action. What is the most important thing we want users to do on the Add Content/Content pages? For me the primary action is to create new content, but I might also want to generate a new content type every so often. So I would move the Add Content as the primary important content type, and the Add Content Type as a secondary call to action using the grey button instead of the blue primary action. This would bring it inline with the current interface practices on buttons:https://www.drupal.org/node/1850248.

ws6shawn’s picture

Status: Needs review » Reviewed & tested by the community

I have successfully added "add_a_create_content-1440678-39.patch" to 8.2.x. I can see the "Add content type" button on both /node/add and /admin/content

alexpott’s picture

Status: Reviewed & tested by the community » Needs review

An unpublished comment rtbc'd the patch. However that comment does not answer any of the concerns in the many comments on the issue.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

kusalavan’s picture

I was able to this successfully. I can see "Add content type" under content. https://screencast.com/t/TALpKN2O

mandclu’s picture

Having read through all the comments in this thread, I would suggest that we could get some forward momentum by splitting off the various solutions that have been discussed (and implemented into patches) here.

For example, there have been concerns raised that adding a link to create or administer content types from admin/content could create confusion.

A second suggestion was to add a link to create content types from the node/add page. The only concern raised is that it may not be obvious to a novice site builder how they would get to where they can reconfigure one of the existing types.

I would suggest that it is most consistent with the UI patterns elsewhere within Drupal to have a link at the top of node/add to create a new content type. Additionally, it could help users if each of the types listed on that page had a contextual link (perhaps behind a gear icon) that would allow them to edit that type. However, because this issue has been in discussion for so long, I would propose the following:

  1. In this thread, implement a link on node/add to create a new content type, and nothing else (as this seems the least contentious UI improvement)
  2. Create a new issue to add some kind of link to admin/content, where different approaches that would not add confusion to novice users can be discussed
  3. Create a new issue to add contextual links (or some other subtle method) on node/add to allow users a convenient and intuitive way to edit existing types
mandclu’s picture

Consistent with my suggestion above, here is a patch that adds the link to create a new content type, only on the node/add page.

djouuuuh’s picture

Hi everyone.

I'm currently experiencing my first #DrupalSprint2017 and I'm trying to contribute :-)

I would love to test something here but my first question is: When you have a list a several patches that were suggested (like in this topic), how do you know which one you are supposed to test? Is it the one that is "highlighted" in the list up there? Or the last one that has been posted (which is not always the right one I suppose)?

Thank you for your help :-)

Looking forward to help you back!

mandclu’s picture

@djouuuuh thanks for your help!

To test the most recent patch (#55), on a fresh install of Drupal 8.4.x apply the patch and clear all caches. Then as an administrator go to the node/add page and you should see a link to add a content type, styled as a primary button.

djouuuuh’s picture

Status: Needs review » Reviewed & tested by the community

@mandclu Thank YOU for assisting me ;-)

I just tested your patch from comment #55 following your very clear instructions. It works as expected.

I'm so happy because this is my very first contribution haha!

ahughes3’s picture

@mandclu I reviewed as well and it worked as expected!

Create Content Type screen shot

tstoeckler’s picture

Status: Reviewed & tested by the community » Needs review

The usability team has not yet signed off on this. Also, if we go with the new approach this needs to be re-titled and the issue summary needs to be updated.

aburrows’s picture

We should get this sorted asap its over 5 years old now..