Description of the need
I wonder if we should consider adding breakpoint functionality to core as D8 has done. This would allow core to manage breakpoints that could be used by modules, themes, layouts, ...
I started work on porting that module from D7: - https://github.com/backdrop-ops/contrib/issues/409 - https://github.com/backdrop-contrib/breakpoints
Here's the D8 info: - https://www.drupal.org/docs/theming-drupal/working-with-breakpoints-in-d...
This was @klonos in a separate thread:
Well, we are aiming for as much feature parity with D8 as possible (where it makes sense, and for features that would make people hesitate choosing Backdrop over D8), so I'd be all in for a breakpoints API in core, that both core and contrib could then use.
Breakpoints in core would help with make developing complex frontend themes easier, but could also be used in responsive things in the admin UI, like the admin bar, the primary tabs, the "low priority" columns in tables etc. Breakpoints could even be used as a visibility condition for blocks.
Recent comments
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared