Provide default instructions on node/add/* forms

Is there any "proposed" text to use as submission guidelines?

I 100% agree with adding it; I'm not sure about associating the help text to the first form field, though. In fact, the "help text" refers to the whole form, not to a single field; in addition to this, aria-describedby could be used to associate a field with its help text.

When editing a content type for an article (/admin/structure/types/manage/article), the "Explanation or submission guidelines" are defined by:

    $form['description'] = array(
      '#title' => t('Description'),
      '#type' => 'textarea',
      '#default_value' => $type->description,
      '#description' => t('Describe this content type. The text will be displayed on the <em>Add new content</em> page.'),
    );

Which doesn't look great at the moment in Core.

I'm not sure where to insert the default text though or what it should be. I'd have expected it in in a yml file somewhere, but not sure where that (or $type->description) is defined.

Ok, this doesn't work locally, but it looks like it should.

Well, the ARIA doesn't work. The description does when I apply it in SimplyTest.me.

More info about ARIA #2126761: The body field summary textarea indicates it has a description with aria-describedby attribute, but the DOM id value points to a non-existent node & #1645420: Use @aria-describedby for fieldset descriptions

Also https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Tec...

Re-rolled

I am not sure about this at all and considering to won't fix this.

The page says its about creating content, and previously you get the instructions what type of content you are creating. So unless the flow that people took was wrong, I don't see how this text is needed. Also on a real website, people will have a much better idea about this since - the content types will map to the type of content shown on the website.

I'd like to know if this is a nice-to-have or a need-to-have because, this adds significant clutter on a key page.

I liked the idea about the text, but needs a little more information to help out the new drupal developers and users. Suggestions are:

1. Use this form to enter your static information such as "About-us", "Directions".
2. Use this form to enter your changing or time-sensitive information such as "News", "Updates".

We could make the help text invisible so that it is there as a hint for screen reader users.

I don't know how often this would come up as a concern. Like much of user testing it seems there are challenges in knowing what you can extrapolate from.

Here's a screenshot of the patch.

It does seem to disrupt the flow as it is now.

This would need to get approval for the UX changes. I know it's not the direction that the team has been going.

Definitely a won't fix, this is not a crucial value proposition and can be discovered through other means.