I have been playing a little with Cwicly today and set up a dummy style guide, basically a partial reproduction of something I usually have for other websites. Coming from Oxygen, recently bought Bricks and played with it a little I can compare them all a little bit.
In Cwicly first of all, I had to learn the interface, the usability is let’s say 80% similar to Oxygen, as it does the advanced stuff also, and basically just need to know where to find things. I honestly think that Cwicly is even more powerful than Oxygen but haven’t reached any dynamic or repeater stuff, which I will certainly do in the near future.
For this dummy style guide I used AutomaticCSS as it works fine with Oxygen and Bricks and wanted to try the basic stuff. It works with some limitations. On the front end all ACSS classes and variables are displayed corectly but none on the editor, so you have to know what you are doing and just do a lot of preview on the front end to check. I’m guessing the editor is loaded before ACSS. If you have an idea on how to make this work I would love to know.
I would love to hear ideas on how to mix Cwicly and ACSS better together.
The Cwicly editor started to lag once I added a second set of colors and variables. It lags on the load and it lags while selecting items but it’s nothing big as I’m coming from Oxygen and that is usual there
I must say that maybe the hosting has an impact on this, it’s a shared one where I have a bunch of other test environments.
I recently did the same thing in Bricks as I did today with Cwicly and Bricks has almost zero lag.
Overall I must say that I’m pleasantly impressed with the workflow and I will certanly continue exploring.
For reference the dummy pages built in Cwicly and Bricks are.