Fellow Cwicly enthusiasts, it’s time we talk about the recent news of Cwicly’s shutdown. While it may seem like a setback, I believe it’s actually a golden opportunity for us to evolve beyond traditional builders. Here’s why and how.
Firstly, let’s acknowledge how great Cwicly has been for layout and design, especially with its recent Tailwind integration. It’s like having a design tool that rivals Figma, tailored for WordPress. Even as a non-coder, I’ve found confidence in building stunning layouts using Cwicly. So why let this skill go to waste?
Thanks to the insightful help from Daniel Snell, I have been able to come up with a solid plan and I wanted to share it all with you. Also Daniel is putting together some nifty tutorials etc.. that will greatly assist us with this transition. If you don’t know Daniel he is super talented and super kind for offering to help us all with this. More info to come…
Now, with Cwicly winding down, the logical next step isn’t to retreat back to the builders but to forge ahead with what we’ve learned. We’ve already done the hard work transitioning to Gutenberg, and it’s time to take the next step – embracing a PHP program like Twig.
Here’s my current plan, broken down into steps, which will help us transition smoothly:
1. **Layout/Design**: Continuing to use Cwicly for its efficient layout and design capabilities. Alternatives like Figma combined with Tailwind can also be used for those who prefer other tools.
2. **Convert**: Transforming the HTML and Tailwind designs into a WordPress-friendly format, possibly as ACF Blocks for greater customization.
3. **Add Functions**: Using Twig for adding complex functionalities, supported by AI assistance for the coding aspects.
This plan sets us on a path to create efficient, beautiful websites without being constrained by traditional builder limitations. We’re stepping into a realm where we’re not beholden to any builders. It’s about leveraging the tools we are comfortable with and integrating new technologies for a seamless web design process.
Let’s view this period as an exciting new chapter in web design. We’re not just adapting; we’re upgrading our skills and methodologies. Stay tuned for more updates as we pioneer this new way of web design! 🌐✨
For me, it’s not the right time, as I need a solution ASAP, but I’ll keep an eye on the project, for sure.
If I were to develop something similar, I’m not sure if I’d choose Twig, but it’s not a bad choice, nonetheless.
I am not a Cwicly user, but I hope Cwicly’s closure is not final. Perhaps some entity (e.g. WPEngine) will take it over. Or maybe Louis will change his mind. So much work has been put into it, that it would be a great loss for the WP ecosystem. I’m saying this as a Bricks and GP user.