Add configurable description to content type title field.

If adding this feature we'll needs tests.

Looks good, thanks!

The test looks good.

+++ b/core/modules/node/src/NodeTypeForm.php
@@ -241,6 +247,10 @@ public function save(array $form, FormStateInterface $form_state) {
+    $title_description = $form_state->getValue('title_description');
+    if ($title_field->getDescription() != $title_description) {
+      $title_field->getConfig($type->id())->setDescription($title_description)->save();
+    }

This could result in two updates to configuration if you change both the label and the description. We should do something like:

    $title_description = $form_state->getValue('title_description');
    if ($title_field->getLabel() != $title_label || $title_field->getDescription() != $title_description) {
      $title_field->getConfig($type->id())
        ->setLabel($title_label)
        ->setDescription($title_description)
        ->save();
    }

Patch #16 works fine for me with 9.0.2, I assume it's because it hasn't change much since 8.7.
I now get a description field just below where I can edit the name of the title field.
It also properly exports and imports to/from config.

Not sure about the tests as I haven't gotten my testing setup to work, so someone with more testing experience with Drupal should probably weigh in on that.

Applied patch #16 .Now the title description field is available at edit section of a content type.
Including screenshot :
Before patch :

After patch:

RTBC

The patch doesn't apply to 9.2.x

Rerolled patch #16 for 9.2.x, please review.

I think there are a couple of things to consider from a UX perspective.

• We can already set a title placeholder on the form display - while not the same as a description is this not enough?
• This adds to the things to do on the node type configuration form and while the setting for the title label is here - is this really the correct place?
• Relatedly since this is going to be a large box with an empty value many people will be tempted to fill in it and that might not be the best practice.

Tagging for a product manager review to get product/UX feedback.

Also the issue summary could do with an update to go into the usecase a little but more.

Also there is a module for this functionality already - https://www.drupal.org/project/node_title_help_text - with 2000 odd downloads so some people definitely need this functionality. And there is a help page on how to do this with form alters... https://www.drupal.org/node/1218528

There's also history of removing a description #2350041: Remove node title field description

We have people signing up to use our site and we found that unlike our inhouse trained content authors, the ones that signed up do not write SEO-friendly titles so we needed to leave some instruction under the field, then I found a need for this feature. I was a bit surprised this wasn't there all the while.

I applied #16 and it worked.

I have created a patch for version 9.5x, Now the title description field is available at edit section of a content type. Kindly review patch,,

I have successfully applied patch #35 for 9.5.x. Adding screenshots for the reference

Verified and tested patch #35 on Drupal 9.5.x-dev. Patch applied successfully and looks good to me.
Testing steps:
1. Goto admin/structure/types/manage/article
2. Observe that the title description field is absent.
3. Apply the patch.
4. Reload.
5. Observe that the title description field has been added.
Testing Result:
1. After applying the patch the title description field appears.
Can be move to RTBC

Two years ago in #28, an issue summary update was asked for by a committer. That has yet to be done. And in #29 he questions whether this should be done at all because this was removed in #2350041: Remove node title field description.

And I see this is tagged for a product manager review, which has not happened.

There has been one comment for support of this feature request, aside from the author of this issue. Is that sufficient to do this?

Setting to NW for the issue summary update.

Patch #35 Verified and tested locally on Drupal 10.1.x.
Patch applied successfully and looks good to me.


Testing steps:

1. Goto admin/structure/types/manage/basic page

2. Observe that the title description field is absent.

3. Apply the patch.

4. Reload.

5. Observe that the title description field has been added.


Testing Result:
 After applying the patch the title description field appears.


Checked the code, also title appears in the node as expected
RTBC + 1

Still needs issue summary update.

Updating the IS.

The API already allows to configure this, it is not exposed on the UI though. I can see the use case of needing to give some guidance to the user about the title field. I also don't think this goes against #2350041: Remove node title field description, that removed a badly technical hard coded description, while this one does not add a new hardcoded description but exposes a feature to the user instead.

The field however is not added consistently with the rest of the elements. How is the field description presented on other field config pages? That would be best to replicate here.

Addressed #47.

Changed the field label to "Title field description"
Updated the description of the field based on the generic field description.

Thanks @Gábor Hojtsy for taking a look!

Appears to have a build failure

Fixed Build failure.

Thanks @Rassoni !

Re-rolled patch from #50 to 10.2.x-dev.

The Title field is a base field on Node.

Base fields can have their labels and descriptions overridden using the base_field_override config.

There is a module to expose UI to do this https://www.drupal.org/project/base_field_override_ui

Alternatively you can use drush to generate one for you, see https://www.previousnext.com.au/blog/overriding-base-field-labels-and-de...

An example of a title base field override for the page content type:
File: core.base_field_override.node.page.title.yml

langcode: en
status: true
dependencies:
  config:
    - node.type.page
id: node.page.title
field_name: title
entity_type: node
bundle: page
label: Title
description: 'My custom description'
required: true
translatable: true
default_value: {  }
default_value_callback: ''
settings: {  }
field_type: string