Haramizu.com has been relaunched!

Implementing a CMS

On the occasion of this renewal, we look back at what we have been using.

• Early Haramizu.com found Next.js + Tailwind CSS + Markdown templates and used them as is, hosted on Netlify
• Headless CMS and Next.js built with Contentful + Next.js + Tailwindc CSS for study, hosted by Vercel
• Renewed as blog.haramizu.com, using Contentful's multilingual functionality to translate between Japanese and English and, for English, using DeepL
• Templates using Astro, building doc.haramizu.com using Starlight and making the content that had been developed on the blog site easier to read together, in fact using markdown again.

In the future, I will take the form of covering the various tools I use.For this reason, I wanted to start by renewing the content of doc.haramizu.com as a base.In line with this, I will be evaluating and reviewing various products.

Looking for a headless CMS

Content management in markdown is good in terms of portability, but we still want to use a CMS.At first we thought about migrating to Contentful, which we used to use, and operating there.However, when we needed a paid plan, starting at $300/month was honestly too expensive, so we considered other CMSs.

We considered various conditions for a CMS when it comes to creating a website.

• Front end is assumed to operate with Next.js + Vercel Pro
  • Netlify is fine as it is a static site anyway, but I am used to Vercel.
• I want to choose SaaS
• I still don't think it's with Wordpress when it comes to the front office.
• In search of a scalable CMS
• Still more global than domestic.

So we found a headless CMS.This is the new CMS we have decided to use, and I personally like it very much, as follows.

• The product is in the Headless CMS genre, but the CMS is very easy to customise.
• Low hurdles to starting to use the system (low-cost start possible)

I would like to write about this area as the first series of articles for this renewal, as it will be easier for me to explain it systematically later than to write about it in a blog post.

Main changes.

The content previously developed on the site has been moved to the following

• doc.haramizu.com
  • The documents posted here have been placed under haramizu.com/docs
  • Japanese documents are expanded under the ja path and English under the en path.
  • All content will soon be redirected to this site
• blog.haramizu.com:
  • Some of the items were published a long time ago and are now out of date and no one will ever see them again
  • For this reason, we will reprint anything that could be summarised under docs
  • We will operate in parallel for a while, but we will eventually turn it off.
• Overall.
  • The / is always added to the end of the URL

Most content now has a different URL according to the above rules, but previous links will be maintained for some time through redirects.

I will only keep it on blog.haramizu.com if it is old again and no one will want it anymore, and close the blog at the end of the day.

Topics to be covered in the blog

From now on, rather than writing Tips as a blog topic, we will focus on delivering new and updated information on the site.

However, we may add to this blog as a past post for any previous blog posts that we think may be useful.