New users have difficulty finding where to adjust the content model

Yes please!

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

Thanks
Ashish

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

Thanks
Ashish

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.

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

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

Screenshots please :)

This patch fixes comment.
Also attached - screenshots

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.

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

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.

#14: add_action_link_for_type-1440678-14.patch queued for re-testing.

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.

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.

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?

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.

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?

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

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

Fixing tags per http://drupal.org/node/1517250

related: #384150: Cross-link content type settings from node add/edit form

clean up grammar and linebraks.

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.

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.

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?

Same issue for block types #2078635: Add an 'Add custom block type' local action to the 'Custom block library'

added related issues section

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

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.

Activating Testbot.

@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.

@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

@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.

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

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

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.

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¢. ;-)

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.

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.

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.

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.

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

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

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

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

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.

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!

@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.

@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!

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

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.

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

Reviewing this at @DrupalConBaltimore2017.

I still agree with those who think the button shouldn't be so prominent as to confuse a new user into thinking that they might need to add a content type (rather than just a new piece of content), but do think that a button to add a content type (a less prominent button) would be a GoodThing™. From the screenshot shown in #59, it seems that the patch still produces a prominent "call to action" with a blue button to add a new content type, above links to create a new piece of content of existing types. (I'm still in agreement with others that have voiced the opinion that this approach may not provide ideal UX.)

The patch in #55 works with Drupal 8.7.x.

RTBC +1

Updated the description to reflect a restricted scope, with the more contentious question about the Content listing page moved to a child issue. Moving this to RTBC since the most recent patch has been tested and verified to produce behaviour now defined for this issue.

Is the screenshot in #59 still correct? Because if so, then like in #63 and even #28 I don't think that would be a good use of the blue "add" button pattern. This needs to clearly identifiable as a link to somewhere else, and not present itself as the main thing to do on this screen.

This issue triggered some more thoughts in general for what to consider when connecting dots across admin screens: https://www.yoroy.com/2019/drupal/no-one-offs

The part relevant to this particular issue:

Notice the distinction between “create content of type X” and “define a new type of content Y”. The first is a content creation task, the second is a content definition task (in Drupal jargon usually captured under “site building”). This distinction then should clarify why a link to define a new content type should not use the “blue + button” pattern on a screen that is in service of a content creation task.

#55
Hi,
I applied this patch in 8.8 version its not getting applied, it showing error for 8.8. Can you please update this patch.

Thank you

The patch in #55 is working and getting applied on the lastet code of branch 8.9.x. No need for rerolling the patch.
Below are screenshot for the reference.

Removing the "Needs reroll" tag.

#55 patch works for me as well. I have tested this patch in Drupal 8.9.x.

Per #72 / #73 the current solution does not pass the usability gate so we need to consider a different solution if we want to do this at all. One possibility would be to implement hook_help() for this page and add a sentence along the lines of

Choose which type of content to create. You can also add a new content type.

Update issue summary per #81

Add hook_help() as per comment #81

As perr suggestions in #81 The new patch #84 for hook looks good to me and applied cleany.
Attaching Screenshot for reference

+1 RTBC looks good to me as well and the patch in #84 works, just a quick suggestion i guess it would be good if upon clicking on the link "add a new content type" opens in a news tab instead on open in the same page.

Attaching test results

thank you

As per #86 i have created a patch for Add content type link to be opened in new window. Adding interdiff also. Please review

I don't think we need to open link in new tab here are some example from core help text open in current window.

#84 works fine.

If you have no content types and have this fix applied with the help module enabled then it looks like this:

The repetition of the link is not ideal. Maybe we should be adding this as a footer to the view. This would also help with the weighting on the page. You've clicked on add content and the first thing you read / have to ignore is a link to creating a content type.

Furthermore there's an issue with permissions. It's by no means certain that the user has permission to create a content type.

Its been a long time since activity so assigning it to myself to work on further from here.

Hi, I have created a patch that covers the three points mentioned in #90.

1. Shifted the line to footer.
2. When there is no content type available there will only one line will be seen, i.e. You have not created any content types yet. Go to the ....
3. Added a permission check as well.

Correcting the testcase.

Got one issue in #95. Here uploading the patch with correction.

@himanshu_sindhwani can u plz attach interdiff .. so as to track the changes easily

Sure @shimpy, Here is the interdiff. Apologies for not uploading before.

Tested the patch given in #99 on some of the core themes, it worked for me and changes are reflecting accordingly. Also, "add a new content type" opens in the same page as a generic behavior.

Please refer to screenshots attached.

Removing screenshots from display.

#99 I have checked for all core themes and it seems to work fine . Please take this for RTBC & the new link is getting open in the same page as expected .

Cleaning up some tags. I also retitled the issue to based on the problem, not the solution.

Another thought I have is that maybe "Structure" is too generic for people to understand that content model is adjusted under that? How about we add new menu for tasks specifically related to entities which we call "Content model"?

Applied patch #99 .It works fine with adding new content types link .Including screenshots
before patch:

after patch:

Thanks for making it easier for users!

The proposed resolution in the issue summary does not agree with the solution in the patch. I skimmed the issue to find where it changed but the lack of interdiffs made that difficult and requires more time than I have now. Since this requires screenshots, it helps if the latest are in the Issue Summary. Adding tag for an IS update.

I may have missed it but I don't see that a code review was done.

Applied patch #101 applied successfully and looks good for me
Thanks for the patch
For ref sharing screenshot....

Reroll against 11.x

This would be very useful! I would like to consider this as a small UI design pattern.
An updated screenshot would be nice.

1. Adding #3325034: Providing additional methods of navigating the admin interface for a similar situation.
2. Though the screenshots are old, current Claro designs also don't add a final horizontal line in these kinds of lists. This suggests that the link is part of the content of the last list item instead of a separate thing.

It's not a primary, not even secondary action, more like a helpful navigation hint: 'Oh, by the way, if you want to create your own version of these thingies, go here. Right aligned would work I think. It probably needs more top spacing or border to clearly separate it from the list items above.

For the IS update from 110.

May be worth pinging in #contribute or #needs-review-queue-initative for subsystem review.