Documentation

[pwFoo]

trafficstars

Awesome demo! But some documentation would bei nice :) Dependencies? Cash? How compare it to other frameworks like bootstrap (size, performance)?

[fabiospampinato]

Thanks! :)

Unfortunately I don't currently have the time for writing the docs... you know it's quite a big project, and it's not clear to me if it would get people excited enough to use it for their projects. The docs will have to wait until I finish some other stuff currently on my plate.

Dependencies? Cash?

It depends on Cash (4kb gzipped) (which I'm also maintaining) or jQuery (30kb gzipped), lodash, Modernizr, and some polyfills if you need it to work on IE 10 and stuff.

I'm currently making partial builds of some of those, so for instance in a project of mine cash ends up weighing about 3.5kb, another 3.5kb for lodash, and about 10kb for the polyfills (unfortunately the way core-js makes these bundles is not optimal https://github.com/zloirock/core-js/issues/388).

How compare it to other frameworks like bootstrap (size, performance)?

Before writing Svelto I thought about using Bootstrap and its plugins, but the problem with that was that all those plugins do not really work well with each other, they end up rewriting the same stuff, they don't take into account what other plugins are currently on the page... and being not written by the same guy all of them are kind of inconsistent with each other (both in style and API design).

Svelto, on the other hand, is monolithic, it's jam packed with features, it has everything I need and everything is designed consistently.

Svelto supports partial builds, so you can use as much or as little of it as you want.

Svelto is bundled with pacco, which is a bundler that I made that was previously part of this repo. This enabled a whole new level of customizability that you just don't get with Bootstrap, you can write your website-specific web framework on top of Svelto, overriding variables, overriding specific files, adding components and all that.

Performance is good, I think I've optimized it pretty heavily in these years.

Ps. in the published demo everything that interacts with the server (like remote popovers etc.) is broken because I'm emulating a server with service workers, and they don't work on non-https domains, it works on localhost though.