Is there any recommended convention about naming DataTypes (eg. ContentPickers)?

There is already a datatype naming convention in the backoffice, if you go the route of edit doctype, add property and create a new datatype..

The name of the Data Type is based on the name of the Document Type, the name of the property, and the property editor

https://docs.umbraco.com/umbraco-cms/fundamentals/data/defining-content#property-editors But with that it ignores any folder structure that we now have (and could hark back to the days before folders were available) Though I do think it probably does also need context of your data structures, eg you might have a dual root node site, and have specific doctypes/datatypes/templates for each setup and if these are mutually exclusive having the names include an indication of that mutual/mutually exclusive usage might matter. with v 17 search now having a filter to datatypes, we probably don't need a dtTextString for quckly finding all datatypes.. (which we used to do) From my side, I do think it's nice to have the datatype name include the type, and a name that indicates functionality, but not sure that the Doctype it's used on is all that useful, as it's rare that we have a datatype that is that limited.. the dt prefix I think also came from instantly knowing it was a datatype with strongtyping in code... (back when stongly typing had collisions between template or property groups with identical names, think modelsbuilder has come on since then) (ct (contentType), pt (property), dt(datatype), t(template) all suffixes we've used in the past ... ;-))

Is this for the creation of a new data type and who is using the nam is going to be key...