From 22a05ba718fbc5a7361c096ea9d7b2b6b79defe5 Mon Sep 17 00:00:00 2001 From: dannyrb Date: Wed, 1 May 2019 11:55:58 -0400 Subject: [PATCH] Copy links from top of deploy-static --- docs/latest/deployment/recipes/build-for-production.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/latest/deployment/recipes/build-for-production.md b/docs/latest/deployment/recipes/build-for-production.md index 632e11a5c..92673e69a 100644 --- a/docs/latest/deployment/recipes/build-for-production.md +++ b/docs/latest/deployment/recipes/build-for-production.md @@ -126,14 +126,21 @@ output. ### Deploying Build Output -_Drag-n-Drop_ +_Drag-n-drop_ - [Netlify: Drop](/deployment/recipes/static-assets.md#netlify-drop) _Easy_ +- [Surge.sh](/deployment/recipes/static-assets.md#surgesh) +- [GitHub Pages](/deployment/recipes/static-assets.md#github-pages) + _Advanced_ +- [AWS S3 + Cloudfront](/deployment/recipes/static-assets.md#aws-s3--cloudfront) +- [GCP + Cloudflare](/deployment/recipes/static-assets.md#gcp--cloudflare) +- [Azure](/deployment/recipes/static-assets.md#azure) + ### Testing Build Output Locally A quick way to test your build output locally is to spin up a small webserver.