Ready for big project?


I just got cwicly this week after looking at alternative for elementor and I’m really loving it so far. I was wondering If you feel the product is ready for big project yet? It seems very nice for smaller website but I’m a bit scared to use it on bigger project. I have a city website and a big health organization website coming up and would like to use cwicly to build them but I have a few concern.

Is it stable enough to not have update breaking your website just yet? With how big those website will be it would be unfortunate to have to redo the website because an update broke stuff.

Ease of use for the client… I saw there’s some settings for this but haven’t played with it that much yet. My clients will mostly want to modify some text/images on their pages and create different kind of blog post. Is there a way to not have the cwicly UI or a very simplified one that has pretty much the same option as base gutenberg for creating those blog post? And can I make it so they can modify page text/image without messing with the layout?

Last question… Do you feel confident enough to support the product for years? I know it’s a bit of a weird and hard question to answer but since those are website that will probably not change for a couple of years I need something that will stay stable and supported for years to come.


It really depends on your definition of “big”. I currently am architecting a shift from Bricks Builder to Cwicly for one of my Catholic non-profits. (I will definitely miss using ACSS and Frames! I will probably have to manually construct all the necessary frames in Cwicly. At least with the private library I can use them for future projects.)

From what I have seen and experienced, Cwicly has been pretty rock solid. Yes, the updates are fast and furious, but they have not killed my site. I have read the horror stories about upgrading Elementor and other page builders, but again I have not experienced anything like that with Cwicly.

That being said, with ANY update, you should ALWAYS use staging sites to test before. I cannot stress this enough, and I’m sure there are countless users here that update on live sites without testing.

For your client, you really should read about the role editor, and then watch the video about it. Then create a test account and play with the different roles/rights until you find something suitable. Because Cwicly is so close to Gutenberg, most of the lockdown abilities work flawlessly and the sheer granular level is just chef’s kiss. Doing this in Oxygen or Bricks is an exercise in patience.

As for support, I’ll let them answer it. Personally speaking, I have full confidence in the team. I don’t see them going anywhere but upwards and onwards.

Alright thanks ! Yeah I always do daily backup, most of my client want to modify some stuff on their website and I don’t always trust them so I have a backup in case something goes wrong. I’m in the process of building a website and really loving it so far and I will fiddle around with the roles/rights after but looking at the option quickly it seems pretty solid.

May I ask what made you switch from bricks to cwicly? I was looking at taking it as well but what made me decide on cwicly was that it is based on guntenberg instead of being a completely separate thing.

Thanks !

Good to hear that you are backing up stuff all the time! I’m quite paranoid so I have triple backups :smiley:

As for Bricks to Cwicly, since my clients are not tech savvy (read: tech allergic), for them to update their own sites requires extreme locking down. Bricks doesn’t seem to have the level of lockdown that Cwicly has out of the box, especially to hide stuff.

Don’t get me wrong, I love Bricks and use it for other clients. But those clients I am 100% in control of what gets on the page. With this client, they want control over content. Plus learning Cwicly is a bonus since they are Gutenberg based and that’s where WP is heading.

1 Like