4 posts tagged with "CI/CD"

To streamline content management for this site, I integrated the headless CMS, Decap CMS (formerly Netlify CMS). This article documents the implementation process, the technical decisions made, and the solutions to problems I encountered.

Ultimately, I settled on a slightly unusual hybrid architecture: the CMS admin panel is managed by Netlify, while the public-facing site is operated on Google Cloud Run.

• CMS Admin Environment (Netlify)

  • URL: https://[your-site].netlify.app/admin/
  • Role: Provides the Decap CMS admin interface and handles authentication via Netlify Identity.

• Public Site Environment (Google Cloud Run)

  • URL: https://[your-custom-domain].com/
  • Role: Hosts the static site, maintaining the existing CI/CD pipeline.

I hope this article will be helpful for anyone considering a similar setup. For subsequent operational improvements, see Optimizing the Decap CMS UX by improving config.yml and index.html.

Note that this article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

This post is a memo organizing the process of internationalizing (i18n) the main UI components of a Docusaurus site: the navbar and footer.

For the basic i18n setup, see Procedure for Implementing Multi-language (i18n) Support on a Docusaurus Site.

Note that this article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

1. Purpose​

The Docusaurus i18n feature is a mechanism for making site text multi-lingual. This time, I'll explain the process of adding new items to the navbar and footer and translating them from Japanese (the default) to English.

This article is a record of the journey from identifying to resolving two tricky problems I encountered when adding internationalization (i18n) to a site built with Docusaurus v3: "client-side routing collapse" and "container startup failure on Cloud Run."

The basic i18n setup steps are covered in Procedure for Implementing Multi-language (i18n) Support on a Docusaurus Site.

Note that this article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

Prerequisites:

• Site Generator: Docusaurus v3
• Hosting: Google Cloud Run
• Development & Deployment: Docker, GitHub Actions
• Package Manager: pnpm

This article organizes the procedures and troubleshooting records from when I implemented a GitHub Action to detect new articles and post them to X as Twitter Cards.

This article is a record from when it was written. For the continuously maintained procedure, see the technical documentation version.

Feature: Detect new posts with GitHub Actions and post them to X as Twitter Cards.