-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move site to Netlify? #1289
Comments
The other advantage of Netlify is that it builds a preview version of the website for each pull request Example PR: https://github.com/Daniel15/babel-site/pull/2/files |
Ok that's really cool too!
all sounds good to me? cc @thejameskyle on the domain? |
This is ready to go, just need to get the DNS updated. Netlify is so fast... It's building pull requests in around 55 seconds. In the time it takes for Travis to simply spin up the environment (install Node.js, Rubygems, and npm packages), Netlify has already built and deployed the preview site. |
Done! Feel free to ping me directly if you notice any brokenness. |
This would allow us to add custom build steps, which is needed if we want to compile JavaScript on the site itself using Babel (for example, to convert the REPL into a React component #1287).
I created a Babel site on Netlify as a proof-of-concept: https://babel.netlify.com/. This is basically the same as the current site, running
jekyll build
to build it. We'd just need to point thebabeljs.io
domain to Netlify to move across. As a bonus, we could get proper end-to-end SSL rather than the CloudFlare one that's unencrypted from CloudFlare to the origin.The text was updated successfully, but these errors were encountered: