Show field type descriptions when creating a new field

If this is a standalone patch decoupled from the Media improvements, then maybe we should mark #2930446: [PP-1] Improve field description texts for fields provided by core as duplicate, and improve all descriptions at once here?

I will adapt @marcoscano's patch. I am working with @phenaproxima and others at the Boston Media sprint.

I removed the parts of the patch that change the description text, leaving in the parts that display the text in the UI.

I removed the part of the test that checks for the description on a Media field. I left in the parts that test for the description of File and Image fields. These were already independent of the actual text.

It turns out that thinking really hard about uploading the patch is not actually good enough. Who knew?

Similar to #4, I'm still not convinced to show the current, sometimes *very* technical and likely confusing descriptions to end users. It's a bit harder to test them in advance (can be done by applying both patches together for example) , but would IMHO make sense to get the improved descriptions in first or at the same time.

Yeah I had a similar thought to #9; we don't want to inadvertently create a UX regression for other fields in trying to improve the UX for these. In general, the less text on the screen, the better, so we should make sure this issue doesn't add new text for other fields where it's not needed.

What someone could do is look around core for existing field descriptions that will now be exposed. We can:

• Post screenshots of what this will look like for File, Image, and Media fields with the current (unpatched) descriptions.
• Look around core for other existing descriptions that would also now be exposed on this screen for other fields, and document a list of them on the issue. (Probably with a screenshot of the longest or ickiest one.)

Then we can decide what to do for this based on that information.

@phenaproxima said this info is in #2930446: [PP-1] Improve field description texts for fields provided by core.

I agree with #9, getting this patch in without improving the descriptions is most likely a UX loss instead of a win.

Also, for committers, all the people who worked on this patch in #2862458: [META] Once media is enabled, having the File, Image and Media reference fields all listed is confusing should be given credit here.

Discussed more with @phenaproxima. We're going to start with adding some brief documentation to media_help() about Media reference fields, how File and Image reference fields are used on them, and what you should use when. Then, we can link to that wherever we need in whatever descriptions we need, potentially display help text as a block rather than as a description, or whatever.

So we'll start with the documentation first, and then decide whether this or another implementation is the correct way to fix it.

Thanks!

The documentation issue is #2934885: Document the difference between File, Image, and Media fields.

Another option is that we could initially display the descriptions only for media, file, and image fields, and only display the other descriptions once they're improved.

This has been fixed in #3356894: Make field selection less overwhelming by introducing groups, right?

Yes, this ticket seems outdated and already fixed in a certain way by #3346539: [Plan] Improve field creation experience / #3356894: Make field selection less overwhelming by introducing groups

Duplicate is probably a better classification.

Saving credits for those who worked on this one.