0. [Resolved] Outcome and Final Conclusion (Updated December 2025)​

Regarding this issue, I have finally successfully logged in and resolved the problem. I would like to share the conclusion with those who visited this article facing similar circumstances.

Results of Support Consultation and Investigation​

Initially, I requested an investigation through Billing Support to a specialized team. However, it took considerable time to coordinate the scope of responsibility between departments (Billing Team ⇄ Technical Team). Ultimately, I was informed that the "Technical Team could not investigate as it was outside their scope," and the case was closed with a suggestion to use the official community forums.

The 7-Day Waiting Period​

However, immediately after the support interaction ended—approximately 7 days after the error first occurred—the situation improved after I refrained from any operations. The 2-Step Verification (2SV) process, which had previously blocked me with the "We couldn't verify it's you" error, successfully went through. I was then able to configure my security settings and log in to Google Cloud.

Based on the login history, the presumed factor for resolution is: "By refraining from login attempts for a certain period, the system's security lock was automatically lifted."

1. Overview​

This article provides a step-by-step solution for an issue on MacBooks where custom image files set as wallpaper (Desktop Picture) through System Settings are not applied correctly or are reset after a restart. After struggling with this minor but persistent issue for years, I finally found a solution and wanted to share it.

The Twelve-Factor App Principles​

Noting down the 12 Principles of The Twelve-Factor App as a quick reference.

This guide provides practical steps for transitioning Python code created in Google Colab to a full-scale development workflow using MacBook VSCode and GitHub. For those who have been developing exclusively on Colab, this tutorial introduces specific steps to build version control with GitHub and a comfortable editing environment with local VSCode, establishing a more efficient development system.

• Repository Setup: Building the receiving environment on GitHub
• Initial Integration: Safe code migration from Colab to GitHub
• Local Environment: VSCode editing environment setup
• Operational Workflow: Establishing daily development cycles

In a previous article, I explained how to integrate Decap CMS into a Docusaurus site. While the integration established a foundation for content updates, I felt there was room for improvement in daily use, especially regarding mobile usability and the efficiency of routine data entry.

This article introduces the practical customizations I applied to static/admin/config.yml and static/admin/index.html to address these challenges.

• Optimizing config.yml: Settings to reduce manual input and prevent errors.
• Modifying index.html: Adding CSS and JavaScript to improve mobile usability.

These tunings have created an environment where I can comfortably update articles not only from a PC but also from a smartphone. I hope this serves as a useful example of leveraging the high customizability of a Git-based CMS.

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.

Implementing the Share Buttons​

I've added share buttons to each article on this site for social media sharing. This post documents the implementation process and the technical decisions behind it.

A key feature of the final component is its ability to automatically fetch the page title and URL. This means that once it's set up, there's no need for special configurations on a per-article basis, which minimizes maintenance.

This article outlines the key considerations and technical details involved in implementing a "News Page" on a Docusaurus site, designed to list domestic and international news sources.

1. Page Purpose and Key Features​

The primary goal was to build a personal information hub for quick access to reliable news sources. The page is built as a static site, emphasizing fast performance, usability, and maintainability.

Tackling Rising Storage Costs in Artifact Registry​

When using a CI/CD pipeline with tools like GitHub Actions to deploy to Google Cloud Run, a new Docker image is pushed to Artifact Registry with every run. While this is a very convenient system, old images will pile up if left unchecked. Have you ever been surprised by a higher-than-expected storage bill?

This article introduces how to solve this problem using Artifact Registry's "Cleanup Policies" feature. I'll provide a step-by-step guide on how to automatically delete unnecessary old Docker images to continuously optimize your storage costs.

This guide is based on the Google Cloud Console UI as of July 2025.

Browser Memo Feature: A Log of URL Sharing and UI/UX Improvements​

Introduction​

Regarding the previously implemented Browser Memo feature.

Based on user experience and analysis of competing services, I have implemented significant feature enhancements.

This article outlines the key technical points of implementing a URL-based memo sharing feature and the UI/UX improvements made in the process.

Related:

• Previous Post:A Record of Implementing an In-Site Browser Memo Feature in Docusaurus