I've been wanting to have my own website for a long time. But I've been so busy that it forces me to prioritize those activities over building my own website and finally that day comes. I can publish the first post today. In this post, I will explain this blog and what kind of technology is behind it that I use to build this website.
Firstly, why did I build this blog? Yep, good question. Have you heard of this quote, "When we teach we learn" and "If you want to master something, teach it"? Very clear. Learning is great but greater if we teach those who want to learn it. Besides that, besides being able to dive deeper into computer programming, I can also learn how to write content and the content I write does not use my native language. It challenging me.
Next, like what I said at the beginning we will talk about what kind of technology is behind this blog. Let's go dive deeper and understanding the technology I used. This blog is built with JAM Stack . Jamstack is the new standard architecture for the web.
Now we are in the technology discussion session, here you go.
- Static Generation The HTML is generated at build time and will be reused on each request.
- Server-side Rendering The HTML is generated on each request. That's all about the website performances. if you want to know more about NextJs you can read the documentation about NextJs on their official website.
Vercel This blog is hosted on Vercel. Vercel is free hosting and opens serverless for static and hybrid applications. This hosting is so popular in the Developer Community, especially Frontend Developer. if you are familiar with Netlify or Surge, it same. only a few features make these hosting look different. You can see the documentation of each hosting if you want to learn more about it.
Github This is the last important thing, I used Github as CMS for stored my posts and delivering them with Github API. But Github API has a rate limit for API requests. I read from the documentation, Github allows you to make requests only 60 requests per hour if you're unauthenticated. How about authenticated users? Github will give you 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether Basic Authentication or an OAuth token was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user. It's different if you use an enterprise Github account, GitHub will give you a total of 15,000 requests per hour. You can open GitHub Official Documentation if you want to learn more about GitHub API.
maybe that's all I can tell for the first post on this blog. always keep updating with posts on this blog. I hope you like my writing, see you in the next post.