Explore >> Select a destination
|
You are here 
|
blog.darylsun.page | ||
| | | | |
tim-boettcher.online
|
|
| | | | | Over the years I attempted several times to get into a habit of blogging, using various content management systems (CMS). In this post I will explain why these projects failed and why I switched to a static site generator instead. | |
| | | | |
tom.preston-werner.com
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
www.outcoldman.com
|
|
| | | At the beginning of this year, I moved my blog to AWS Amplify and started to use Hugo as a static site generator. Often, I write several blog posts, but I usually don't want to post them all at the same time, so I write them for the future. Like any other lazy developer, I want to automate the process of automatically posting new blog posts. Hugo is smart, and by default it does not render posts that are in the future. You can change it with the buildFuture attribute. | ||
