From 08b3004fcb8d6642c8397563f90ff34b4927c598 Mon Sep 17 00:00:00 2001 From: Timothy Hopper Date: Wed, 28 Oct 2015 10:52:28 -0400 Subject: [PATCH] Update link to S3 deploy instructions Previous link goes to page with warning "This article is outdated" --- docs/content/tutorials/automated-deployments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/tutorials/automated-deployments.md b/docs/content/tutorials/automated-deployments.md index 3981e2bb7..e3636ab28 100644 --- a/docs/content/tutorials/automated-deployments.md +++ b/docs/content/tutorials/automated-deployments.md @@ -267,4 +267,4 @@ Simply fill in the name, and make sure you enable **auto deploy** from the **mas From now on, any time you want to put a new post on your blog all you need to do is push your new page to GitHub and the rest will happen automatically. The source code for the example site used here is available on [GitHub](https://github.com/ArjenSchwarz/hugo-wercker-example), as is the [Hugo Build step](https://github.com/ArjenSchwarz/wercker-step-hugo-build) itself. -If you want to see an example of how you can deploy to S3 instead of GitHub pages, take a look at [Wercker's blogpost](http://blog.wercker.com/2013/06/10/Streamlining-Middleman-Deploys-to-s3.html) about how to set that up for Middleman. +If you want to see an example of how you can deploy to S3 instead of GitHub pages, take a look at [Wercker's documentation](http://devcenter.wercker.com/docs/deploy/s3.html) about how to set that up.