Introduction

In this series, we'll follow the content of the courses listed on Sanity's official website to manage WordPress content using Sanity.

• Migrating content from WordPress to Sanity

If you're more comfortable with English, please refer to the official steps. This is simply the English version of the article introduced in Japanese.

Sanity Introduction

Sanity is a highly flexible, headless CMS that excels at managing structured content. Custom schemas can be defined in TypeScript, allowing for real-time collaborative editing and rich API integration. In this course, we will introduce what kind of product it is, referring to the Sanity tutorial.

Prerequisites

This time, as a sample blog, I shall utilise a WordPress blog I previously created for personal use.

• 原水商店

This blog utilises only WordPress's standard features, resulting in the simplest form of data. When actually migrating, any sections utilising WordPress extensions will need to be disabled.

Once you have completed these steps and successfully migrated the data into Sanity's content management system, this course will be concluded. In practice, this merely involves migrating the data to the CMS; separately, you will need to build a website that integrates with the CMS. Regarding this, I intend to create and publish a sample after the migration is complete.

WordPress Site Check

When actually proceeding with the work, we will verify the data obtainable from the WordPress site. If you have launched your site using WordPress, data retrieval is possible via the following URL:

I use the WordPress.com hosting service, specifically the free plan, which imposes restrictions on API access. However, you can still access your blog data by following the steps below.

Access was possible as follows.

Regarding whether data can be retrieved via the API, please verify based on your environment. While the free version has limitations as described above, we will proceed with the migration within those constraints this time.

Summary

This time, we confirmed the status prior to the migration. This procedure was carried out based on the content published on the following page.

• First steps

Once you're ready, let's move on to the next step.

Preparing a Studio and schema types

If you've completed the WordPress environment checks in the previous prerequisites section, let's get started right away. This time, we'll create the Studio environment for the CMS and prepare the content schema.