วีดีโอ

Thank you for the tutorial. The CSS version works smoothly however on mobile doesn't look good. I see the two divs (track) one on top of each other.

I did this, and repeated the tracks to make sure there was enough width... but on mobile, it doesnt seem to work. Can you show us how to make mobile view have the same effect? EDIT: found it lower in the comments. no-wrap.

FYI, I followed up with WPvivid on this issue and today received the following reply to my ticket: Hi Kevin, Just want let you know that after discussing your case in the team, we think it is reasonable to add an option of deleting all rollback backup files and have decided to do so. This option should be ready in the next 1-2 releases. Thanks for reporting it and let us know if you need any further information. All the best, WPvivid Support Team

weird that my bricks cant do unset. it wont pass 100%

Thank you. I just realized I had this same problem. Sigh.

Thank you for your extensive comment on the previous situation. I am happy to have heard Louis' decision to came back with Cwicly even as a free version and explaining some background plus current plans in his YT-video "Going live - We're free" here: th-cam.com/video/6LEdiiwXv8Y/w-d-xo.html Maybe this gives you enough confidence back in Cwicly which it deserves in my oppinion.

Why do we need to export the wire frames into Webflow? I had an understanding that Relume could build the complete website and luanch it.

Thanks for the coupon code m8! you saved me 20% !!! appreciate it!

Thank you for this. I had the exact same problem.

We both spent significant time in the Cwicly forum and were fully invested in Cwicly. If you recall the livestream with Kevin, Louis seemed not himself and was not speaking rationally. This worried me. As you noticed his work ethic was on another level. Several times we saw him pushing updates on a Sunday night. He burnt himself out as no one could sustain such a high level of production. When the announcement came, I was indeed shocked but deep down I knew why. Complete burnout and the critiques of Cwicly really stung him even though it was mostly just constructive criticism. The lukewarm Tailwind integration response was the last straw for Louis. Maybe there is more going on, we just don't know. The Cwicly catastrophe has made me really rethink the tools I use and realise that no matter what I use, there is a level of risk involved. Bricks is an excellent builder but just as expendable with a single developer. Though there is a strong community insulating it. That's why I am moving forward learning custom block development. In my opinion Bricks is not as intuitive as Cwicly. As for functionality you will need an additional 2 plugins to get it close to Cwicly's builtin options. Its a pity most didn't invest the time to learn this because I believe they were more familiar and comfortable with the Elementor builder approach.

This video is so bizarre. I use Elementor and chose it because it has wide popularity in the market, it is an established brand, a SAAS model, and the chance of it going out of business is very low. If you invest your time and money on every shiny new toy that comes in to play, and if things go south, you are to blame, not Cwicly or every other shiny new toy.

Thank you for your thoughts. I was often tempted by Cwicly but could never quite bring myself to commit. I can't put my finger on it but there was something not quite right about the setup. The team clearly do not need to sell their product and that might tell us something about what lies at the bottom of this mess.

Another great video! Very clear. Good pace. I like your style. Well done! Thanks.

This is great. I needed something simple without having to do a slider implementation because thats just too complicated for a logo ticker. I have a bricks + acss setup and i ran into an issue on mobile < 767 breakpoint. Both the tickers were running simultaniously. I managed to fix it somewhat with setting flex wrap to 'no wrap' at the section class i made and it fixed somewhat. I say somewhat because after a certain point in the first track there is a gap and then images get loaded after a delay; could this be an image size issue? Some of these images are png instead of svg... The 2nd/3rd loop runs fine, this is a problem in the first run only. As you may have guessed, i am rather new at css and dont understand all the nuances of code. Perhaps you can check your setup on the last 2 breakpoints and confirm if you're seeing this problem too?

FIIIIIIIIINNNNAAAAAALLLLLYYYYY ! The ones made by Cracka and Web Squadron were not my favorite. The css one is so easy ! I will try the motion.page version with Bricksforge. Thank You so much.

Nice, you could do this also with the GSAP animations of Bricksforge

amazing !

Nice tutorial, Welcome to Bricks. Please get rid of the background instrumentals, I always find it annoying and distracting.

Welcome to the Bricks community, Sunny. Been receiving your emails for some time and I appreciate their value. A couple of questions on this video. What are the pros and cons between the two implementations? Which one would you choose and why?

Instant like! thank you for the tutorial Sunny!

Nice video! Good to see you working on Bricks Builder!

Great addition to the Bricks community! Welcome!

Excellent and very well presented tutorial. Thank you for sharing. One request -- could you please provide the logo images (as a zip file)? I would like to try and reproduce this logo carousel.

The bricks community will love your vids ;)

It's a terrible situation, given how many useful WP tools are built by Independents, and what this means for trust. I really like the team at Blocksy theme, if you want to continue with Gutenberg.

How are you a "long time cwicly user".. when it hasn't even been around a full 2 years? How do you have a fiancé and wife (wedding site) at the same time? With all of your statements, you're missing a very important and key thing.. ALL of these 'builders' are just that, builders. You aren't a 'developer'. You're just using a very well coded frontend tool to mimic a 'developer'. Do the actual developers of these builders use tools that mimick developer writing code? The answer is no. The point is, you want to build 'websites' as a business, you want to assume the title of 'web developer', then study and then apply actual coding languages! Start with basic HTML / PHP and JS. Then choose something more advanced like NextJS, Vue, etc. Then you are beholden to a 'builder' on top of a CMS trying mashup predesigned elements and passing it off as a 'website'. Cwicly wasn't and isn't the problem, it's your reliance on something that was merely created to mimic something else.. like all of the other builders that you load up with 'plugins' and then spend all of your time debugging just about everything in the generated code, fighting with responsiveness, trying to figure out how to increase your pagespeed and combatting hack attempts while using the world's number one hacker's red apple!

You say there's nothing comparable to Cwicly, and you'd rather stay in the Gutenberg ecosystem instead of moving to Bricks. You mention Greenshift already, but did you really deep dive that yet? It's extremely powerful and has most of the features Cwicly had, except for components (but that's on the roadmap too). But the UI is way closer to Gutenberg core (although they're using icon tabs like in Cwicly for more developer focused things like the classes system as well), so it doesn't take over the entire UI like Cwicly did. And, as with Cwicly, the development is crazy fast and they really listen to what the users want (and regularly ask what users want in their Facebook group). On the other hand, Greenshift is also a new plugin with a small team behind it. But Igor, the lead developer, stated he would never do what Cwicly did. He said that if he ever wanted to quit, he would find another team to take over, or make it open source. Just what Cwicly should have done...

I tried to post this video in the forum and the guy just delete it, I cannot just praise the guy for what he have done, he knows he screwed up a lot of people and i think all he cares its about his ego and issues, someone touched a thin fiber, such changes and decisions can't be taken under the blame on emotions alone.

Thanms for this great video. You nailed all my thoughts on this issue and i hope theres some hope left for cwicly in the future.

hi Sunny, my thoughts are exactly like yours. when something abrupt like this happens it feels like talking about it helps us elaborate the situation, and in community we can better manage to support each other emotionally so we can overcome the potential trauma that could lead us to our own bad decision making. so i'm glad you posted this video, because knowing that my decisions moving forward are similar to yours (a person so engaged in the community and dedicated like you are), i feel more secure and strengthened. thank you!

A very tough place to be for anyone that used Cwicly. It makes us all think ahout the tools we use. Toolset strayed into this territory about two years agon but have commited to maintaining their suite of plugins which, for all intents and purposes, works quite well as is. It should be a wake up call to the developers of core in WordPress. Wordpress really needs some sort of common framework upon which all the builders have to operate, not only for interoperabiluty and standards, but also work in a way that if one tool is discontinued, another can stand in in its place. This goes for plugins that generate post typse and custom fields as well as content and layout tools. In other words the content and design must persist if something is turned off. That migh be a tall order, but it would be something to aspire to, for the sake of all the WordPress users out there. I see that the Live Canvas plugin has managed to do something like this.

Totally agree with everything you've said, I built one site with Cwicly and had planned to use it for all future sites. Difficult to get motivated to use another builder at this point.

Very well said 👍

I think that everything said is right on the spot Sunny. A couple of years ago I was considering Oxygen for an enterprise website, but the Angular situation coupled with Breakdance made me take the niche tool card off the table for enterprise builds. I was watching Bricks & Cwicly evolve over time. Trust in niche tools was damaged for me, and frankly this Cwicly situation is the nail in the coffin for me.

That was an excellent analysis.

This is an excellent video - from someone who obviously is passionate for Cwicly, and for all the right reasons. I also bought lifetime deals for Cwicly - first for 3 sites and subsequently for 100 sites. But the learning curve was just too steep for me and my needs. So I switched to Bricks - but I still admired Louis and his work and I think he was a leader in e.g. moving first on Components. As I deeply want to support competition around the WordPress builder (and I believe Cwicly was/is simply the most advanced and well coded tool in this area), I would be happy to start paying a subscription again. Just to make sure that Cwicly stays around and continue to positively influence the platform (WordPress) that is behind 43% of all webpages. I sincerely hope that someone is able to reach Louis and manage to work out a solution to keep Cwicly as one of the core plugins for WordPress. I believe all that is needed is a more simply UI/UX for beginners and more tutorials/how to videos - we need more guidance on how to use the builder. Louis - if you are reading this - Cwicly is your baby and almost all admire you for what you have created. Please, please, don't let your (technical) "baby" go down just because of the unavoidable criticism from a small minority. You build Cwicly for the rest of us - please stay with us. We need you - your technical skills, your values and your personality.

I think all Cwicly users deserve the real reason why it shut down out of nowhere. Louis threw all Loyal supporters away.

The reason I bought Cwicly was because of Kevin, so would be weird if he was one of the influencers referred to, Kevin has been saying nothing but positive things about Cwicly

Well said Sunny. I can’t imagine going through this kind of torture for a second time. Only recently did I myself make the jump to Bricks from Oxygen. I think everything you said was thoughtful.

Very well said. I never got into Cwicly as I abhor all things related to Gutenberg. But I always respected the innovation it demonstrated.You'll enjoy Bricks. I was one of the early adopters (way back at version 1.2) after running toally frustrated from Oxygen (after 2 years) and I believe it's as close to the perfect Wordpress development environment that there is right now (especially with Cwicly out of the picture).

Thank you Sunny for taking the time to so thoughtfully, respectfully and empathetically express what I'm certain many Cwicly users would have wanted to express, myself included. I sincerely hope that Louis and the Cwicly team find a way to see for themselves how much love there is out "here" for him/them, his/their vision and his/their Herculean efforts to bring that vision to life. Nothing comes even close to the inspired fusion of art and technical mastery that Cwicly brings to the WordPress Community in the most unique and innovative fashion. Let's all take a pause and embrace the prospect that time, rest and reflection will give way to brighter days ahead.

"How am I supposed to get excited about building something that might just screw me again." - Bingo...

You are such a great person Sunny. I've never been interested in Cwicly, no longer in Oxygen over a year... However, I saw this video by clicking on the link from your newsletter, which I always wait for - because I like your work very much and I feel that You are such a great person Sunny. Keep your work! Kudos.

Well said. Everything you said. And thank you. You earned a subscriber.

Really well thought out and articulated. I myself was not a Cwicly user, but I saw a lot of potential there. It's a tough spot and my heart goes out to all the folks who staked their livelihood on Cwicly. Louis seemed like a great guy, and I agree with your comments that it seemed very out of character, so I think something else may have happened in his life that we are all not privy to that led to this decision. It's a sad day to see them go, and also to see the unfortunate collateral damage that will be felt across the WP community at large. I'm a dedicated Bricks user, and unfortunately now it makes me a bit nervous thinking, what's to stop Thomas from deciding to call it quits. I'm not implying he will, but it does make you look over your shoulder with a bit more anxiety. I really hope all that were affected by this can recover from it and move on - I am not directly impacted but I can definitely empathize with those who are. I also hope Louis, his family and his team make it through all this ok, and that maybe there is a way all of this can somehow work out for a positive outcome. Shocked, totally.

I continue to hold onto hope for their return.

16:40 that right there... especially for a mostly 1 man show .. people die and get severely sicke,.. so the worst case scenario especially for small teams is crucial

Hello. Excellent video. You have expressed very well the suffering that so many are experiencing at this time (the glazed eyes speak for themselves... ), summing up the situation perfectly. I was just thinking about it as soon as I read the news of how I might have reacted if I had fully invested in Cwicly and what a tragedy it might be in those who had solely bet on Cwicly. Which I had not done while being fascinated by Louis' brilliance and his way of dealing with users. Working almost solely on ecommerce-related projects, I never had the necessary peace of mind to seriously start a project with this builder. And... if I had, I would have been devastated and shocked today, I would have experienced all the emotions you expertly described. And knowing me too, I would have thought of abandoning everything in despondency. So ... I'm very very pleased that you haven't changed your mind. I think there is a great need for people like you. Don't ever give up! :) p.s. I have also signed up. If all the videos have the same quality (as I think), I will very gladly come back to listen/watch you.

Very thoughtful response video Sunny. You earned a subscriber. Thank you.

You say what I think, very balanced! Can't believe that the project will be completely abandoned in the long run. It really makes you wonder why Louis Cwicly doesn't at least sell to an interested party. Such a shame for everyone involved!