DGdguo·Aug 16, 2017
The first time I heard of Netlify was when I was making a change to the documentation for Yarn and noticed deploy previews for pull requests[1]. Here's an example[2], if you expand the status check.
That alone piqued my interest. For static sites, I've been using a combination of GitHub Pages and CloudFlare, mainly for SSL support on custom domains, since you can't do that with just GitHub. I used Netlify for the first time on a small side project a few days ago, and the experience was awesome. I plan to move all my static sites to them in the future.
For dynamic sites, the idea of a frontend being served up from a CDN and having just an API backend is so appealing. My big concerns are SEO impact and users who have JS disabled. There is prerendering[3], but I need to learn more about how well it really works and what potential edge cases
Read the rest
exist. I went to the trouble to implement server side rendering for my day job website (React frontend), but it adds a fair amount of complexity. It almost certainly wasn't worth it for a MVP product.
[1] https://www.netlify.com/blog/2016/07/20/introducing-deploy-p...
[2] https://github.com/yarnpkg/website/pull/389
[3] https://www.netlify.com/docs/prerendering/