I added a new blog section to https://naokitnk.me/blog/.

The homepage already had the Recent Thoughts section powered by Mastodon, which works well for lightweight notes and small updates. However, I also wanted a place for longer writing that does not fit naturally into short-form posts.

This new blog section fills that role.

Goals

The main goal was to keep the architecture simple and fully static.

The blog is generated using Hugo, but intentionally avoids depending heavily on themes or large frameworks. I wanted the visual style to remain consistent with the existing homepage and CV site rather than looking like a generic blog template.

The current structure is intentionally minimal:

  • naokitnk.me as the homepage and presentation layer
  • Recent Thoughts for lightweight short-form publishing
  • /blog/ for long-form writing
  • mstdn.naokitnk.me as the publishing backend for Recent Thoughts
  • naok.io for personal short URLs

Design Direction

I wanted the blog to feel like a natural extension of the existing site rather than a separate product.

The homepage already had a fairly mature visual language:

  • restrained spacing
  • rounded section headers
  • lightweight cards
  • minimal shadows
  • static deployment
  • infrastructure-oriented aesthetics

The blog now reuses the same shared CSS and JavaScript sources used by the homepage. Hugo is mainly used as a static rendering engine and content organization layer.

Static Publishing

The deployment model remains intentionally simple.

The site is edited locally, committed to Git, pushed to a private Forgejo instance, then deployed to the public Linode host using a pull-based deployment workflow.

The generated blog output is committed as static files alongside the rest of the website.

There is no database, dynamic backend, or runtime CMS involved.

Future Topics

Likely future topics include:

  • Linux engineering
  • security and SELinux
  • infrastructure and homelab systems
  • identity management
  • static publishing and personal web architecture

The current implementation is intentionally lightweight, but it already feels like a good long-term foundation.