Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Bytes.co

    (@burlingtonbytes)

    Until version 1.0, We’re focusing on the Bootstrap grid, to accelerate our path to launch as much as possible. However, over the next few updates, Bootstrap will be made into a more pluggable component, where it will only be loaded if bootstrap blocks are enabled.

    At that point, we’ll start approaching building blocks for other grid systems and frameworks.

    If you need to add support for unsemantic before that point, I’d recommend adding a blockade folder in your theme, and copying the “simple columns” block from the addons folder into it. You can then change the slugs being used throughout the plugin (to avoid conflicts), and modify plugin.js to use unsemantic classes, instead of Bootstrap. Lastly, you’d want to use the wp-blockade-available-addons filter to ensure that the original simple columns addon isn’t loaded.

    Plugin Author Bytes.co

    (@burlingtonbytes)

    Replacing Bootstrap with another framework is now supported via filters. the wp-blockade-framework-css filter can be used to remove bootstrap itself from Blockade and/or replace with another css framework, then wp-blockade-tinymce-plugins can be used to remove the blocks that rely on bootstrap, such as simple columns and buttons. Finally, new blocks can be added that are based on the new framework.

    • This reply was modified 7 years, 8 months ago by Bytes.co.
    Thread Starter ashf

    (@ashf)

    great

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Unsemantic support’ is closed to new replies.