[UX] Content type listing page: style it consistently with the Views listing page

[klonos]

Sibling issue to #2029 and #3886

Current:

Proposed:

• split description into its own column, and add priority-low class, so that it can be hidden on mobile.
• bold the content type name, for better scannability/readability.
• wrap machine name into a second line, and make the font smaller.
• font in rows of disabled content types should be grayed out (#999999).

---

PR by @klonos: backdrop/backdrop#2746

[klonos]

backdrop/backdrop#2746

Mobile:

The enable/disable feature is not included in this PR, as it would make it a feature request instead of a UX task: #3883

[bugfolder]

@klonos, would you rebase the PR backdrop/backdrop#2746, which has conflicts, and add the magic "Fixes" word to the first comment?

(BTW, I think these changes are indeed good UX improvements.)

[klonos]

Some time has passed between when this issue and PR have been filed, and most of the things outlined in the issue description have already been implemented in recent versions of Backdrop. Here's what that page looks like now:

So, to the points in the issue summary:

• split description into its own column, and add priority-low class, so that it can be hidden on mobile.

This has been done, with the exception of adding the priority-low class to the description column.

• bold the content type name, for better scannability/readability.
• wrap machine name into a second line, and make the font smaller.

This has been done 👍🏼 ...the newly-introduced theme_label_machine_name() function is being used to consistently output machine names across various listing pages now. Most of all this has been addressed in Backdrop 1.20.0 as part of #3402.

• font in rows of disabled content types should be grayed out (#999999).

I don't see any option to disable content types. Regression? Functionality intentionally removed? Was it even there to begin with? (perhaps it was something I was playing with on my local) ...in any case, outside the scope of this issue here.

I'm gonna go ahead and close this as outdated/WAD.