Experiment: Content types tracking issue

[ntsekouras]

In #77497 we landed an experiment to manage custom taxonomies (Content types: manage custom taxonomies).

Let's see how far we can get with the current APIs and how possible it can be to support the majority of use cases for custom taxonomies (and later for post types), where it's assumed that the majority of the cases are the simple ones. Complex use cases will remain in the plugin territory.

This effort is also valuable to help other core features and APIs evolve, like DataViews and DataForm.

Custom taxonomies architecture

• Add more fields for taxonomy creation and edit. This will probably result to a new page for creating a taxonomy instead of the current Modal. PR: Experiment: Taxonomies new package and add/edit screens #77657
• Separate page for edit and add taxonomy. PR: Experiment: Taxonomies new package and add/edit screens #77657
• Consider renaming the current edit action to quick edit and create edit action that redirects to a separate page. PR: Experiment: Taxonomies new package and add/edit screens #77657
• Revisit how we store and consume the config of the entity. Should we use post_meta for some fields. Investigate implications, security, performance. PR: Experiment: Taxonomies REST controller #77697

Taxonomy fields

• Add more fields. Right now we've only added all labels. This task should be implemented incrementally for easier testing.
• Labels should probably be auto-generated on creating a new taxonomy from singular-plural labels. User should be able to manually update them after that.
• Users should be able to regenerate labels automatically when there are edits in singular-plural labels. Should this be an explicit button in the labels card UI (regenerate)? Should it be a checkbox (auto regenerate)? Take into account if manual edits exists before auto generating
• Investigate how/if labels are internationalized. Maybe adding some filters that 3rd party plugins is the way to go here.

Enhancements

• Relax taxonomy-key pattern validation. See ongoing discussion here: Experiment: Add custom taxonomies #77497 (comment)
• Now that the Drawer component has landed, explore using it for the edit action. This will inform us whether is good for our use case and whether the quick edit in site editor can use it too.
• Add more filters - especially the post type. This is related to how we end up storing the config. PR for post type filter: Experiment: Taxonomies REST controller #77697
• Investigate the rest of labels and whether they should be auto generated by the singular/plural labels - they should still be editable.

Bugs

• Fix height of taxonomies page. DataViews should fit 100% height like we do in site editor. PR: Experiment: Improve taxonomies DataViews height #77603

Upstream fixes

• FormTokenField: Add help prop to render additional help text below the field
• DataForm: Render field description as help text in the array control

Notes

This is a living issue and any suggestions are welcome.