Mitar

This looks cool. How could we detect which packages are not Blaze Components? So one idea is as I described in https://github.com/meteor/meteor/issues/4267, allowing people to add some custom metadata. How...

Or maybe just ask component developers to provide a screenshot. :-) And a possible link to a demo app.

I made this simple site: http://components-explorer.meteor.com/ :-)

We should probably do such search recursively (so packages which depend on packages which depend on `peerlibrary:blaze-components`), but it is OK for now. :-) Also, probably not all packages will...

> `offthegrass:testing123` Skeptic! :-)

Current code for explorer: https://github.com/peerlibrary/meteor-blaze-components-explorer

Some questions with server side rendering: - ~~what to do with `*.html` files which add things to `` and ``~~ - can we use this for spiders? - and that...

Not really sure. I have not looked yet much into server-side rendering.

Yes, this is something @mquandalle should add to his compiler. [Here is code](https://github.com/peerlibrary/meteor-blaze-components/blob/master/patch-compiling.js) for HTML files.

Because magic events seems to renders event handlers to DOM to define events. This is much uglier approach.