I feel you guys but I think a lot of you want to use ABMaterial to design websites, not webapps. And it is not made for this. If you want to build websites there are literally thousands of programs/online builders that will allow you to make what you want. (e.g. like the site demonstated in the post above).
ABMaterial was build to make great interfaces for B4J apps. Using all the power of B4X and having a nice interface that works on all devices.
For example, in my day job, we've now build an app that reads an Opticon scanner attached to a Raspberry pi. The user surfs to the pi, attaches its scanner and clicks a read button. This is impossible to do in a browser, but works great thanks to B4J. We read the scanner, send it over to our central server, process the new data and build reports, send a notification to the users browser that he can download a new pdf report, show a chart etc...
Another app we made is the CRM app for our sales people. They can lookup their tasks, make notes, lookup clients, prospects, show them in google maps etc...
In both cases ABMaterial is just the UI, B4J is the real engine. And by using my framework, it was done in a fraction of the time, saving thousands of hours not having to write the HTML, CSS, Javascript, tuning it for every device etc... I wrote both apps in 3 days, would have been 3 weeks without the ABMaterial/B4J combo.
I know it may be hard for some people to grasp the concepts I use in ABMaterial and I try to explain it to the best of my capacities, but believe me, writing the HTML, CSS and Javascript behind it manually is much, much harder. I too have to take a piece of paper, draw out how I want the interface to look, decide how the grid should react depending on the device and only then I start writing the B4J code to make it.
So in short, I will create 'helper' tools like this code-builder on the way and they may become more and more advanced in time, but I have no intention to write yet another Website builder (sorry).