Explore >> Select a destination
|
You are here 
|
reticulated.net | ||
| | | | |
vickiboykis.com
|
|
| | | | | I swore I'd never switch static site generators again | |
| | | | |
sathyasays.com
|
|
| | | | | Opinions, thoughts and tutorials on Cloud, DevOps, Linux and Technology by Sathyajith Bhat. | |
| | | | |
terrygodier.com
|
|
| | | | | Over the past few weeks I've migrated every content site I have from WordPress to Hugo, a popular and easy to use static site generator. In this post, I'll detail why I think WordPress is a bad solution for most people, and how I went about migrating my site in just a couple of hours on a weekend afternoon. Oh, and before we get started, the site I'm talking about in this post is the one you're currently on. | |
| | | | |
sookocheff.com
|
|
| | | Here it is. My version of the S3 static site. This one is publishable through CloudFormation and uses CodeCommit and CodeBuild to regenerate and publish the site with every push to the host Git repository. Any change to the CodeCommit Git repository automatically triggers a build through CodeCommit. This build runs the Hugo static site generator on your repo and syncs the results to an S3 bucket configured for serving a static site. | ||
