I understand IG's wish to choose something wide spread and well supported, so that it stays with us and our slow web-technique adaption cycle. But we also need something that both programmers and web designers (or rather the guy that patches the html together) can understand fast. That is why I opt for a small (in terms of file size and used components) tool.

Yesterday, I might have found exactly that: http://www.w3schools.com/w3css/default.asp

Look at their page, it is almost exactly what we need. They have some templates there, too.

Clearly you get it.  :)

I'm willing to give it a look.  In fact, I was in the middle of experimenting with a switch from Materialize to Bootstrap for exactly the reasons you cited.  W3CSS looks interesting, and it's definitely worth a look.

So let me ask you (the_mgt) two important questions:

1. Do you agree that the future of WebCit should be that we deliver the basic building blocks as REST/DAV from the C server, and build the UI using a web framework?

2. I know that in the past your time was limited; do you now have the time to work on it with us?

If the answers are both yes, then let's give the W3CSS approach a try.

 

Reply via email to