Skip to content

Blog Architecture

This article introduces how my blog works.

Warning

This blog is being maintained by me alone, and everything is subject to change without any explicit notice.

The Goal

  • I want my blogs looks clean and nice.
  • I don't want to operate a blog with my own server, nor spending too much money on using 3rd party services.
  • I don't want to distract readers with unnecessary ugly ads in a page.
  • I don't want to use outdated or EoL-reached techs like Ruby Sass.

Therefore I migrated my old blog to the new one.

Core Frameworks

MkDocs is a core engine used to build this blog. Material for MkDocs is an another layer built on top of MkDocs, which helps a lot on building static web page without too much effort. It was a pretty nice choice, because

  • I don't wanted to invest my time on HTML, Typescript, and CSS stuffs too heavily to create nice looking stuffs.
  • Python is the most familar programming language for me.
  • The framework is actively being maintained.

Most of theme in this blog is provided by those frameworks. I customized several stuffs that mkdocs-material is not currently providing, but I think that's a relatively smaller work compared to this whole infrastructure.

Info

If mkdocs-material becomes inactive, I may migrate this blog to another framework at that time.

Hosting

I use Github Pages to publish my static web pages on Github. I am already spending money monthly on AWS, Youtube Premium, Linkedin Premium, etc. I don't wanted to add more 30~40 USD/month eater for non-profit blog.

I have my own domain(mcdic.net as you see) with AWS Route 53. I have some number of subdomains under mcdic.net and this blog uses one of them.

Comment Section

I use utteranc.es to build comment system with Github Issues. Since I use public Github repo to publish my blog, and it was easy to override comment parts of HTML in mkdocs-material, it was trivial to add this. There are several alternatives like Giscus so you can check and compare.

Custom MKDocs Plugin

I made my own custom mkdocs plugin to customize following behaviors. Note that I got rid of built-in blog plugin because there were several big issues on the whole structure, refer here if you are interested.

  • Categories
    • Prev and Next buttons will lead to prev/next articles in same category.
    • Forcing zero or one category for every page.
  • Metadata of blog posts
    • Git dates
    • Post Views
      • Calculate the metadata from either custom data folder or GA4 API and embedded it. (Previously I used Javascript async fetch, but I got rid of it.)

Views on Posts

Since my blog is a set of static web pages, it was a bit tricky to add views. I use Google Analytics to get views, unique users and more of my blog. So I decided to run cronjob via Github Actions to periodically fetch GA4 data with Python, then customized the blog post HTML section and my own plugin.

So I failed to make my billing completely zero, but I think this is still feasible, considering I am providing unique user views on my blog posts.

May not accurate

I changed some posts paths and titles several times, and I am aggregating them by summation, which might be inaccurate in some cases.

I plan to add more stuffs whenever I need. If there is anything you wonder, please ask in comments.