Hi HMM - Iâm still deep in the exploration process: right now Iâve purchased Blocs/Solis and Pinegrow. I am also taking a serious look at RapidWeaver via tutorial videos on Youtube.
All 3 of these options in varying ways, have revealed to me a real need to know more about website coding, and frameworks, perhaps mostly at the conceptual level or in actuality in order to control the apps and therefore the outcome on the screen.
While in varying degrees the three apps Iâm currently exploring allow for non-coding experience, and market themselves as non-coding apps in varying ways and to varying degrees, in my learning curve with each I feel knowledge of coding is invaluable to understand each oneâs UI. Blocs, for example uses âclassesâ for CSS, which is a solution to add code without coding in the strict sense, and my sense is that this can become quite cumbersome to manage over time to achieve a personal look and function, and does require understanding what âclassesâ are; and I sense it will become a frequently needed UI tool to do things âoutside the boxâ; and while I can see a correlation to âlayer states/stylesâ in Photoshop or other similar appearance control UI functions in a range of âdesignâ apps, this is not necessary in Muse in order to control appearance and functionality and location of elements on the page (though âstylesâ can be saved and reused), and this is significantly augmented by 3rd party âwidgetsâ (such as the ones Iâve mentioned as âwish listâ items).
In a large way, 3rd party âwidgetâ makers for Muse, spans the gap for non-coders to give us more design power, by packing into widgets the functionality while using the primary UI approach for styling the widget. Blocs has opened itâs API and this is promising. I actually wrote to QooQee and mentioned this to them, encouraging them to explore Blocs & Pinegrow.
To address my learning curve, Iâve also gotten a hold of Brackets code editor and am wading into the book Bootstrap Quick Start guide by Jacob Lett, and several other HTML & CSS books, and will do the same with JavaScript at some point, to see how much coding I can learn and be able to make use of â the purpose of doing this is to give me deeper insight for making a final app decision to replace Muse, and be able to maintain the functionality that I currently have with my Muse site.
My end goal is to be able to replicate what my current website has, and be able to make changes down the road with the equivalent freedom, control and independence Muse currently provides me.
Since I have 2 years to cut the cord with Muse, I have plenty of time to see how all three apps, or any others that may arrive on the scene, evolve to meet my personal needs.
My guess is I am in a minority position, in that I am not a web designer/developer, but rather due to having an architectural design background and therefore comfortable with using CAD and other âdesignâ software, and un-interested in using a premium âtemplateâ website service (WIX, ect.) or something like Wordpress to make my one and only website, I like learning what I need to (and having fun doing it).