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
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface