Hi @David,
Thanks for asking.
Most of the base rework of Cwicly has been done. We’re coming to a stage where we’re happy with how our block architecture is designed and we can see it evolve/grow without much difficulty.
What remains to be re-worked:
-
Design library → completely cloud based (hosted with us, not through individual sites and API keys) where users can upload their elements, templates, complete themes with automatic setup
, global classes, settings etc. A community library will also be included, so you can choose to share your designs and elements with others. We’ve pushed the Mega Menu development aside for a bit and are working hard to get this out in the next couple of weeks. -
Interactions → reviewing the UI so that it flows a lot more. The base is pretty solid, but needs refining while needing an easier entry level. With this comes the inclusion of scroll animations/interactions, completely custom built by the user. The most important feature here is to have most/all interactions work on the backend, so you don’t have to go back and forward to the frontend to see how things look.
Is there some area that has you concerned in particular?