Broader Frontends
Author : Kazuhiro Hara
Article permalink

I Have Started Trying Payload CMS 2.0

I am doing a technical evaluation because I want to try using Payload CMS. I installed it locally as a trial, so here are my impressions.

For installation, I followed:

However, because I want to use PostgreSQL rather than MongoDB for the database, I also referred to:

For the local environment, I prepared a dedicated database using a Docker container. I used the postgres Docker image.

By the way, the Payload CMS version is 2. The new features and other updates are announced in this blog post.

After trying it, my first thought was that being based on Next.js seems nice when you need to extend it. At the same time, I still have the impression that Next.js changes rapidly, so one possible countermeasure may be to put a layer like Payload CMS in between and avoid using Next.js directly as much as possible.

The PostgreSQL functionality I used for the database seems to still be in beta. However, Payload CMS uses Drizzle ORM:

The 2.0 announcement article says that SQLite and MySQL may become available in the future. I am more used to MySQL myself, so I would appreciate that.

Taking this opportunity, I bought PostgreSQL Tettei Nyumon because I thought I should properly study PostgreSQL even at this point. I plan to read it during the long weekend.

What caught my attention was the new rich editor called Lexical. Payload started adopting it in 2.0, and apparently it aims for something like Medium's minimalism combined with Notion-like functionality.

A CMS that feels good when entering content is welcome, so I want to try this part and write my impressions again. Incidentally, this feature is still in beta at the moment, so if you want to introduce it, you need to install it separately.

Personally, I feel like Markdown may be enough, but there is text suggesting that Lexical Rich Text can interoperate with Markdown, so I want to try that someday too.

CMSPayload CMS

Share