Sergii Lavrin

We definitely should go with client-side search, but yet to decide with which one. Candidates: - http://lunrjs.com/ https://github.com/jediq/grunt-lunr-index-generator https://github.com/assemble/grunt-assemble-lunr Some random tutorial: http://jekyll.tips/jekyll-casts/jekyll-search-using-lunr-js/

Seems to be nicer way to handle that wast variety of favicons for different systems and browsers: - https://github.com/haydenbleasel/favicons - or alternative online-only version: https://github.com/RealFaviconGenerator/grunt-real-favicon - or less alive https://github.com/gleero/grunt-favicons...

There is no ready solution for Grunt yet. So, we should come up with our own. Properties for `xml` could be gathered from Gray Matter or with `cheerio`. Some useful...

It's unclear how to treat multiple CSS files with `grunt-uncss`, `grunt-uncss` accepts multiple html-files, but outputs only one CSS, while sometimes we may need separate CSS — for IE hacks,...

CSS tests

1

Add CSS tests Some useful information: http://www.creativebloq.com/css3/4-tools-automatic-css-testing-7133777

Given the type ```js // @flow export type Term = { prop: string } ``` compare LSP error with original Flow error:   Because LSP error doesn't show full...

## Problem If this code is invoked right on page load, it often does nothing: ```ts const login = useGoogleLogin(...) login() ``` The issue happens because callbacks are internally waiting...