Description of the need
Since we are not making any progress on coming to a consensus about fixing CSS in Basis (https://github.com/backdrop/backdrop-issues/issues/4167), I'm inclined to begin to advocate for a new theme in core that we can eventually use as a default theme.
In my view, many UI or potential design improvements are on hold because of lack of any consensus on how to implement CSS changes to basis.
Proposed solution
Add a new theme to core that assume one of the following:
1) Take our time and try to get it right, recognizing that we will have the same inability to fix problems with this new theme, once it has been committed. 2) Make it clear that this is a DEMO theme designed to showcase Backdrop and that we will be making breaking changes to it. Users should only use this theme if they are willing to accept the risk or willing to fork it and use it like a custom theme (no updates). 3) Build this theme with the idea of supplemental stylesheets (https://github.com/backdrop/backdrop-issues/issues/4512) or supplemental selectors (https://github.com/backdrop/backdrop-issues/issues/4782) in mind from the outset.
Recent comments
The block system and API in Backdrop is very different from Drupal's. In Backdrop, as in Drupal, modules can define blocks in code (in fact some of the API at this level is the same, with...
Drupal block module conversion
This was from examining line 2463- of the webform.module, where // Attach necessary JavaScript and CSS. $form['#attached'] = array( 'css' => array(backdrop_get_path('module', 'webform...
How do I diagnose Webform Conditionals failing?
d'oh. Because of course it is reassigning. Don't mind me... the correct syntax is $form['#attached']['js'][] = backdrop_get_path('module', 'mymodule') . '/mymodule.js';
How do I diagnose Webform Conditionals failing?