INTEREST JOURNAL DRUPAL & WEB

Why I started using Hugo for inter-est

About 700 words 4 min read

Japanese ↗
On this page

On October 24, 2026, I moved inter-est to Hugo. As the site grew, I wanted a way to follow each step from writing an article to seeing it live. For my first post about Hugo, I’d like to share why I chose it and what changed in my day-to-day work.

From Drupal and Tome to Hugo

I started building this site with Drupal. That’s where I learned to organize articles so readers could follow categories, tags, and links to related posts. I also used Tome with Drupal to generate static files and tried keeping the editing environment separate from the server that delivers pages to readers.

The next thing I revisited was how I write. Editing the body in Markdown and managing the title, date, and tags in files suits the way I work. I can also keep the Japanese and English drafts side by side when I review them. That was one of my reasons for choosing Hugo.

The three diagrams show where the work moved. With Tome, I moved editing off the public server. With Hugo, I switched to editing Markdown locally and building the site with Hugo.

  1. LightsailEdit and save articles in Drupal
  2. DrupalRender pages when requested
  3. ReadersVisit the public site
When the site launched in 2024, Drupal ran on the public server.
  1. MacBook ProEdit articles in a local Drupal site
  2. TomeExport static files from Drupal
  3. LightsailHost the generated files
  4. CloudFrontDeliver pages to readers
In July 2026, I moved editing to a local Drupal site and began serving static files.
  1. LOCALMacBook ProArticles, images, settings
  2. BUILDHugoGenerate static files
  3. ORIGINLightsailUpload via SFTP / Ubuntu & Apache
  4. DELIVERYCloudFrontDeliver to readers over HTTPS
Since October 2026, Hugo has built the files for publication from local Markdown.

What Hugo offers

Hugo is a static site generator written in Go. It takes Markdown files, templates, and site configuration and builds the HTML and other files for publication. It is designed for fast builds, and its built-in development server lets you preview changes in a browser as you save them.

Hugo also supports multilingual sites and taxonomies such as tags and categories. I use these features for inter-est’s Japanese and English pages and its tag-based article lists. Hugo documentation

What changed when I update an article

Here’s how my routine at inter-est changed from static publishing with Tome to working with Hugo.

Task Drupal + Tome Hugo
Write an article Write and save in Drupal’s editor on my MacBook Edit Markdown in a text editor and save the title, date, and tags in the same file
Check the page Open the article on the local Drupal site Preview it with Hugo’s development server and check changes as I save
Build files for publication Export Drupal pages as static files with Tome Use Hugo to build static files from the source files and templates
Publish Upload the exported files to Lightsail and serve them through CloudFront Compare with the previous build, upload changed files to Lightsail, and serve them through CloudFront

When I revise an article, I edit the local Markdown file and preview it in a browser. For a weekly roundup of Drupal security advisories, for example, I check the new posts in both languages and make sure readers can reach them from the yearly index and search. After building the files for publication, I compare them with the previous release and upload the ones that changed.

The public server delivers the generated HTML, images, and other files. Serving those articles no longer requires a running CMS or database on that server, so routine article updates can focus on the drafts and the files I publish. I still maintain the server and check the live site after publishing.

I’ve built the article lists and search around how people use this site. Recent changes include a search page for Drupal guides and updates and a blog page where readers can browse by genre. As the site grows, I find myself paying as much attention to how readers find an article as to how I write it.

What I’d like to cover next

Next, I’d like to walk through a small site for anyone trying Hugo for the first time. We’ll write a single article, preview the draft in a browser, and generate the HTML for publication. Later posts can cover organizing articles with tags and maintaining Japanese and English pages.

I’ve written more about starting the site and experimenting with Drupal on the About page. About inter-est

Explore Drupal & Web articles ↗