/explore
|
You are here 
|
ajaykarwal.com | ||
| | | | |
danilafe.com
[AI summary] The author discusses transitioning from a custom-built blog to a static site generator for improved efficiency and features like version control and code integration. |
|
| | | | | ||
| | | | |
levimcg.com
I decided to migrate my site from Eleventy, a static site generator to Kirby a file-based CMS written in PHP. |
|
| | | | | ||
| | | | |
www.simpleprimate.com
Jekyll bills itself as "a simple, blog-aware, static site generator." It takes source files like templates, stylesheets, includes, and posts and uses them to generate a website that can then be hosted on your server of choice. This means that the entire website is generated at once, and visitors are simply served static files. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
