Description of the need
As https://www.drupal.org/node/3276042 says Drupal has deprecated the Color module in 9.4.0 and will remove it from the core in 10.0.0. Has Backdrop community considered to do the same, because some of the arguments described on https://www.drupal.org/project/ideas/issues/2808151 feels true for also Backdrop:
We should move Color module to a contributed project since as it stands, it doesn't provide enough flexibility to be useful for the majority of sites. To be able to create website matching to corporate identity, you would probably want to change at least background images and font families as well.
We never use the Color module on any Backdrop projects as well as number of other modules in core, but I guess it would be too radical to request to move them too from core. But just in case if this resonates to someone else in the community I wonder how many of Backdrop developers really use the following modules? Should they be in core or could be better off as contributed modules?
See the whole list of core modules on https://github.com/backdrop/backdrop/tree/1.x/core/modules:
book - nice module, but rarely used. is core right place for it? ckeditor - too heavy, too slow, an overkill for some of the simple websites.
Recent comments
I also have a problem with the Taxonomy Menu module. I was trying to associate a menu to a taxonomy using the taxonomy menu, and it doesn't work. I thought it was a problem with the website I'm...
Taxonomy menu module is broken
I was gonna say I'll go off and try them options but the simple link looks like the easiest as it took seconds to implement! Didn't really want to manage outside of BD as that requires...
Set title to Node reference
You could have a simple link using this: Or you could make the Content: Nid field link to the content. Give it a meaningful label and you don't need the title field in the View. ...
Set title to Node reference