I though I would try to discuss the most concerning issues currently with Cwicly.
First and foremost, transparency as to the future of Cwicly. I understand the goal is to publish it to the Wordpress Repository and release it as open source. But there must be a revenue stream at some point and potential investors. A business plan of sorts. Letting us in on the financial path forward would be beneficial. This will help repair the damage done to the temporary ceasing of development a few months back.
I hope Louis would be interested in opening things up and possibly creating a tier of advanced users that would be trusted to help with documentation, Youtube tutorials and forum management. Such delegation would provide Louis with the ability to concentrate on Cwicly.
To increase users I have a few opinions that I hope others could chime in on. I believe what I state below must be a priority before anything else is considered. Refinement of current tools I believe should take precedence.
-
3 free themes (integrated with Tailwind or without). This is most important so new users understand how to build in Cwicly and with best practices.
-
YouTube and Documentation support for setting up your first project in Cwicly including Global Colours/Gradients, Global Elements, Breakpoints, Tailwind activation and/or External Classes from Core Framework for example.
-
Add additional library assets to get people started that are integrated with Tailwind or without. Anything is better than nothing. The current library many of the thumbnails are missing completely leaving people in the dark.
-
Fully integrate Tailwind in all elements of the builder (it is present in global elements now but there is a bug limiting use). For example, add warnings so people are aware that when trying to add a Component option setting that Tailwind must be switched off. Having Tailwind activated creates conflicts say for example if you are looking for the CSS Grid builder a simple message to let you aware of that conflict would be very beneficial.
-
Components are one of the selling features of Cwicly but they must be refined. Add support for Repeaters and Background images within a Component. Address bugs (for example in Safari and adding padding or margin options).
-
Add the option for Repeaters/Query loops on every Div block. This is were Bricks Builder shines. Their implementation is ideal. Adding this to Cwicly is most necessary.
-
Responsive Images/Videos by breakpoint.
-
Select multiple blocks to copy or delete. This is only possible by wrapping the blocks in a single div and copying/deleting the div. In the current version of Worpdress Core 6.6, Gutenberg you are able to delete multiple blocks at once with a keyboard shortcut. This is not possible in Cwicly.
-
Themer does need some work but it is usable right now. I believe what I have stated above as more important.
-
Conditions need to be simplified. Again Bricks has implemented this very well so that even novices with a wee bit of direction can achieve desired results. With the new version of Conditions, simplification is best. Maybe even an option to select the most common functions at one click populating all required fields would be an excellent addition. This would help those learning to understand how to get something working and make their own conditions based on those provided.
These are just my opinions but I hope to get a conversation going.