This looks like it will be a really helpful addition to Bricks, and it gives me a bit more confidence to dive in and try it. I'll be following to see what integrations come along.
Thanks for your comment gradxy. I see that Bricks 1.4 is out in beta. From my discussion with the author on his Facebook group, it sounds like 1.4 might address the barriers to integration I raised in the video. I'm looking forward to trying it out after Easter. Right now I'm focusing on adding support doe CSS masks and shapes. This should be available tomorrow with a bit of luck! Sebastian
OMG... I was just thinking about a way to use css hero to export the css to add to the yellow css tabs on bricks, and I saw this. I personally like it better than CSS hero, not even sure why. it just flows for me. specifically being able to choose what level of "nest" on the selectors. It makes me look like I know CSS when I really don't know much at all. thank you!
Hey, thanks for dropping by. I'm really glad to hear that you're enjoying Microthemer, and that it's helping with your CSS skills :) If you ever get stuck with a CSS issue, feel free to reach out here or in the forum: themeover.com/forum/ Cheers! Sebastian
Hey Max, thanks for your comment. Yes, I believe Bricks is ready for integration now. It's on my ToDo list, I'm just working on some internal optimisations first. I'll post here when I have news to share.
@@MarkWill890 this is still planned. Bricks integration is waiting on two features, the first is in beta now. 1. PHP-like conditional page logic for applying CSS on specific pages, and deferring non-critical CSS 2. Support for multiple CSS/Sass/JS snippets in the folders, rather than a separate "full code" view that only supports one editor for CSS/Sass and JS I think these are features the Bricks community would appreciate, so I'm holding off integration until they are both ready. Thanks for question, please let me know if you have any more. Cheers, Sebastian
This looks really interesting as I'm still learning CSS, how will Michrothemer handle the next 1.4 release,? what with replaced all jQuery code with vanilla (plain) JavaScript. The HTML output, element IDs & classes have been further optimized. There is a "Converter" in 1.4 that applies those changes. If you are using the "External Files" loading method, definitely make sure to regenerate your CSS after updating.
Hey Michael, thanks for your comment. At present, the workflow is the same as shown in this video, even for 1.4. However, the changes in 1.4 should pave the way for deeper levels of integration. I haven't started on this yet, but will play around with version 1.4 fairly soon. From what I've read, the issue I flagged at the end of the video about the HTML in the editor not matching the frontend have been addressed in version 1.4. If so, the CSS grid auto-fix MT was applying may be redundant, and so can be switched off via Microthemer's preferences (if enabled). Bricks moving from jQuery to vanilla JS should not affect anything. I hope that helps. Please let me know if you have any more questions. Thanks, Sebastian
This looks like it will be a really helpful addition to Bricks, and it gives me a bit more confidence to dive in and try it. I'll be following to see what integrations come along.
Thanks for your comment gradxy. I see that Bricks 1.4 is out in beta. From my discussion with the author on his Facebook group, it sounds like 1.4 might address the barriers to integration I raised in the video. I'm looking forward to trying it out after Easter. Right now I'm focusing on adding support doe CSS masks and shapes. This should be available tomorrow with a bit of luck!
Sebastian
Looking forward to the full intgration with Bricks
Good to know Dan, this is still very much on on the cards!
Full integration, yes please! My two most favorite WP plugins :)
Thanks for the comment and upvote!
OMG... I was just thinking about a way to use css hero to export the css to add to the yellow css tabs on bricks, and I saw this. I personally like it better than CSS hero, not even sure why. it just flows for me. specifically being able to choose what level of "nest" on the selectors. It makes me look like I know CSS when I really don't know much at all. thank you!
Hey, thanks for dropping by. I'm really glad to hear that you're enjoying Microthemer, and that it's helping with your CSS skills :) If you ever get stuck with a CSS issue, feel free to reach out here or in the forum: themeover.com/forum/
Cheers!
Sebastian
Isn't Bricks now more consistent? I think they have updated to that end. How about the integration with Bricks Builder?
Hey Max, thanks for your comment. Yes, I believe Bricks is ready for integration now. It's on my ToDo list, I'm just working on some internal optimisations first. I'll post here when I have news to share.
@@Microthemer Wondering if anything ever came of deeper integration with Bricks.
@@MarkWill890 this is still planned. Bricks integration is waiting on two features, the first is in beta now.
1. PHP-like conditional page logic for applying CSS on specific pages, and deferring non-critical CSS
2. Support for multiple CSS/Sass/JS snippets in the folders, rather than a separate "full code" view that only supports one editor for CSS/Sass and JS
I think these are features the Bricks community would appreciate, so I'm holding off integration until they are both ready.
Thanks for question, please let me know if you have any more.
Cheers,
Sebastian
This looks really interesting as I'm still learning CSS, how will Michrothemer handle the next 1.4 release,?
what with replaced all jQuery code with vanilla (plain) JavaScript.
The HTML output, element IDs & classes have been further optimized.
There is a "Converter" in 1.4 that applies those changes.
If you are using the "External Files" loading method, definitely make sure to regenerate your CSS after updating.
Hey Michael, thanks for your comment. At present, the workflow is the same as shown in this video, even for 1.4. However, the changes in 1.4 should pave the way for deeper levels of integration. I haven't started on this yet, but will play around with version 1.4 fairly soon. From what I've read, the issue I flagged at the end of the video about the HTML in the editor not matching the frontend have been addressed in version 1.4. If so, the CSS grid auto-fix MT was applying may be redundant, and so can be switched off via Microthemer's preferences (if enabled).
Bricks moving from jQuery to vanilla JS should not affect anything.
I hope that helps. Please let me know if you have any more questions.
Thanks,
Sebastian
@@Microthemer Thanks for the reply Sebastian, I see they have just released 1.4 hope to see you making a video with the 1.4 with over 300 updates.