Using the Core Framework with Gutenberg and Cwicly

In this video I walk-through using the free version of the Core Framework with vanilla Gutenberg and with Cwicly. I show what works and the gotchas, as well as the steps for using it with Cwicly.
The Core Framework website: coreframework.com/
The Cwicly website: www.webtng.com/go/cwicly/
(affiliate link)
0:00 - Introduction
0:34 - Core Framework website and intro
2:53 - Testing the plugin version with Gutenberg
10:24 - Testing the plugin version with Cwicly
12:17 - Using the Core Framework UI to create our own CSS Framework
23:21 - Steps for using the Core Framework with Cwicly
27:06 - Conclusions

[@davidbabinec]

Thanks for this video, David! It gives me and the team ideas on what to improve next in Core Framework.
We will soon work on the deeper integration to Cwicly so it's going to be way more seamless.

[@DavidMcCan]

Great to hear!

[@brianlovelace]

Would love to see a way to preview classes kinda like what ACSS does, but with all builders, including Cwicly :)

[@LupusDesign]

Another excellent walkthrough, David. Thank you.

[@DavidMcCan]

Thank you for the positive feedback.

[@maxziebell4013]

It seems plausible to develop a Cwicly connector, although pricing it at 99 Euros like the Bricks version may appear excessive. However, since the classes are already present in the database via the plugin, it might pave the way for CF developers to collaborate with the Cwicly team for integration. On another note: Previously, Cwicly has signaled a deeper integration with Tailwind, which now aligns well with their component offerings. This integration could simulate a Vue/React-like component environment, minimizing Tailwind's limitations while maximizing its advantages. Ultimately, offering choice would be the favorable outcome for users.

[@DavidMcCan]

Totally agree. Thank you for sharing your insights.

[@EricDegaardt]

Great help 😊 thanks!

[@DavidMcCan]

Glad it is useful.

[@stefanradu4550]

Great video.

[@DavidMcCan]

Thanks Stefan

[@John.Rearden]

There are no videos on the internet comparing Core framework vs ACSS vs Oxyprops vs Tailwind for Bricks.
Food for thought.

[@OneBrokeBloke]

Does Bricks support Tailwind?

[@John.Rearden]

@@OneBrokeBloke Yes, through third party plugin, Winden.

[@devbash]

Hey David. Loved the first vid. A little off topic but I think I hear some phasing on your voice. Don't know if you have two sources recording.

[@DavidMcCan]

Thanks for letting me know. I'll check to be sure only 1 mic is enabled.

[@SamFrysteen]

With Cwicly, why wouldn’t you just use the CF Wordpress plugin to set the styles … then just add the external classes with copy and paste. That way, classes will be loaded and you can change the settings on the fly still in the CoreFramework area in the backend.

[@DavidMcCan]

There are two parts to the CF WordPress plugin that are different than the online tool. One is the loading of stylesheets in the Gutenberg editor and frontend and the other is the UI in the editor for picking classes. The stylesheet is not loaded by the CF WordPress plugin in the editor when using Cwicly and the UI for picking classes doesn't work. I show those things in the video. I guess you could disable the Gutenberg integration in the plugin and just use it to generate the variables and styles, but then it is an extra plugin that is only rarely used so you might as well use the online tool.

[@dcolum23]

There's no reason to think Core is going to work seemlessly with other frameworks, even if they utilize Gutenburg.

[@DavidMcCan]

I agree. I don't think I said it would. Cwicly in not a framework and I showed the manual DYI mode of using Core to generate styles.