Problem/Motivation

Identified as a UX issue in #2497361: [meta] Fix issues found during UMN Usability Testing 2015

After adding a content type, user is brought to the Manage Fields page. Since this page does not have the content type name in the header (header just says "Manage fields"), the user believed that they failed to create the content type. "This page has nothing to do with what I just did. Whatever the helpdesk said didn't work."

Steps to reproduce

Proposed resolution

Not yet determined. Some potential options:

  • In the Field UI for a given content type, add a link to create a new node of that content type.
  • In the confirmation message after creating a content type (The content type
    has been added.) + [LINK TO NODE CREATION FORM]

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3353280

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

bnjmnm created an issue. See original summary.

zeeshan_khan’s picture

zeeshan_khan commented

I really like the approach as many user face the problem you have mentioned here.
Well, I believe it will be better if we can show a message with add content link e.g:- "Content type created you can add content here." Something like that.

sakthi_dev’s picture

sakthi_dev commented
Assigned: Unassigned » sakthi_dev

sakthi_dev opened merge request !3827

sakthi_dev opened merge request !3828

sakthi_dev’s picture

sakthi_dev commented
Assigned: sakthi_dev » Unassigned
Status: Active » Needs review

Please review.

smustgrave’s picture

smustgrave commented
Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs usability review

This ticket was more for discussion first to decide on an approach. As you can see in the Proposed solution.
No test coverage and one MR is actually empty.

Maybe the current MR can be used but solution should be decided on first.

Not ready for review.

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented
Issue tags: -Needs usability review

We made a similar insight as part of the research conducted earlier this year #3343940: Field UI 2023 User Research:

Users find navigating between "content" and "edit content types" burdensome

This is not exactly the same, which could be due to the fact that we used different scripts in the studies. In the more recent insight we discovered that there are challenges with navigating between the manage content type and content form even after the content type has been created, e.g. when adding fields to a content type.

One of the proposed solutions that could help with both of the problems has been documented in #3325034: Providing additional methods of navigating the admin interface.

I'm removing the needs usability review tag for now, until we have settled on a proposal.

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented
Related issues: +#3325034: Providing additional methods of navigating the admin interface

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.