4.4 KiB
| title | description | summary | date | draft | author | tags | canonicalURL | showToc | TocOpen | TocSide | hidemeta | comments | disableHLJS | disableShare | hideSummary | searchHidden | ShowReadingTime | ShowBreadCrumbs | ShowPostNavLinks | ShowWordCount | ShowRssButtonInSectionTermList | UseHugoToc | cover | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hello World! | Yet another blog. | Yet another blog. | 2023-09-03T21:48:44+07:00 | false | Hiiruki |
|
true | false | right | false | false | true | true | false | false | true | true | true | true | true | true |
|
Yeah, my another blog again (￢_￢)
Previously I had a blog that used Static Site Generator (SSG) which is Eleventy, but now I have moved to other SSGs and what I'm using now is Hugo.
Tech Stack
- Hugo for the Static Site Generator (SSG)
- Netlify to host this site and for the CI/CD pipeline
- GitHub to host the source code
Why SSG?
I'm using SSG because it's easier to use and it's faster than using CMS (Content Management System) like WordPress. I don't need to worry about the server, database, etc. I just need to write the content and the SSG will generate the static site for me.
Static site generators offer several advantages that make them a compelling choice:
- Efficiency: SSGs pre-generate web pages, eliminating the need for server-side processing. This results in faster load times and reduced server resource consumption.
- Security: Since there's no dynamic server-side code execution, the attack surface is smaller, making your website less vulnerable to security threats.
- Scalability: Static sites can handle high levels of traffic without performance issues, making them suitable for projects of all sizes.
- Version Control: Content and code can be easily managed with version control systems like Git, enabling collaborative development and content updates.
- Cost-Effectiveness: Hosting static sites is often less expensive than dynamic sites because you don't need robust server infrastructure or database management.
- Simplicity: SSGs encourage a straightforward development process. Content is created and organized in plain text files (e.g., Markdown), and the generator takes care of rendering them into HTML.
- Portability: You can host static sites on a variety of platforms, making it easy to switch hosting providers or migrate your site.
- Maintainability: Easy to maintain regarding software updates.
- Transparency: Transparent in what is going on under the hood. Especially the open-source SSGs.
Why Hugo?
I'm using Hugo because it's fast, simple, and easy to use. It's also written in Go, making it cross-platform. I'm avoiding the use of Node.js because it's bloated and slow. Additionally, some individuals have security concerns related to JavaScript, so I'm minimizing its usage as much as possible. This site also functions properly even when JavaScript is disabled.
Why Netlify?
I'm using Netlify because it's free, easy to use, and it has a CI/CD pipeline. I'm using the free plan because I don't need the paid plan yet. I'm also using Netlify because it's easy to set up and it's easy to connect to GitHub.
Why Blogging?
I started this blog to jot down things I've learned, mainly because I tend to forget stuff I picked up earlier. But hey, I've made it public, so you're welcome to give it a read and pick up things too. Sharing is caring, after all! ^^
Sorry if there are any mistakes in the blog/articles/writeups, you can contact me if you have any questions.
Anyway, welcome to my blog and happy reading! ^^
