Why I am switching from Craft CMS to Payload CMS

Summary

In this video, Chris from Westside Technology Solutions discusses his transition from Craft CMS to Payload CMS, highlighting the challenges he faced with rising costs and the need for more affordable solutions for clients. He compares various options, including Gatsby and Strappy, ultimately finding that Payload CMS meets his needs for both static and dynamic site generation. Chris appreciates Payload's code-first approach, local API capabilities, and the ease of managing collections and fields without the complexities of other CMSs. He expresses excitement about integrating Payload with Next.js and looks forward to meeting the Payload team.

Takeaways

• 😀 Chris from Westside Technology Solutions shares his journey in choosing a CMS for his projects and clients.
• 📈 Craft CMS has been a significant part of Chris's work, but rising costs have prompted him to seek alternatives.
• 🔍 After exploring various options, Chris found Next.js to be a better fit for building affordable websites.
• 🚀 Payload CMS caught Chris's attention due to its code-first approach and local API features.
• 💡 The JSON object configuration in Payload CMS simplifies the creation of collections and fields.
• 🔄 Payload allows reusability of fields across collections, unlike Craft CMS, enhancing flexibility.
• 📊 The ability to create both static and dynamic sites with Next.js offers clients more options based on their budget.
• 🛠️ Chris appreciates the customizable admin panel in Payload CMS, allowing tailored user experiences.
• 📅 Upcoming updates to Payload CMS promise improved integration with Next.js, heightening Chris's excitement.
• 🤝 Chris looks forward to meeting the Payload team, sharing a connection as they are based in the same city.

Q & A

What is the main topic of Chris's video?

The video discusses Chris's exploration of content management systems (CMS) and his decision to switch from Craft CMS to Payload CMS.

Why is Chris considering a change from Craft CMS?

Chris is looking to make sites more affordable for his customers, especially after Craft increased its Pro license pricing significantly.

What alternatives did Chris consider before deciding on Payload CMS?

Chris initially considered using Gatsby and then Next.js for static site generation before finally deciding on Payload CMS.

What advantages does Next.js offer that Chris appreciates?

Next.js allows for the creation of both static and dynamic websites, enabling Chris to cater to clients with varying budgets by starting with a static site that can be upgraded later.

What are some key features of Payload CMS that attracted Chris?

Payload CMS offers a code-first approach, an easy-to-use admin panel, the ability to manage collections and fields through code, and a local API that enhances developer experience.

How does Payload CMS manage collections and fields differently than Craft CMS?

In Payload, collections and fields are created through code in JSON format, allowing for easier version control and the ability to reuse fields, while Craft uses a YAML file and a database setup.

What problem did Chris encounter with Craft CMS regarding environments?

Chris experienced issues with Craft CMS where modifying collections or fields would create conflicts between the database and YAML files, requiring manual selection of which version to use.

What is a significant feature of Payload CMS that Chris highlighted?

The local API feature of Payload CMS allows it to hydrate data directly into Next.js server-side components without making separate HTTP requests, enhancing efficiency.

What upcoming feature for Payload CMS excited Chris?

Chris was excited about the upcoming major version of Payload CMS that would integrate better with Next.js, aligning perfectly with his CMS needs.

What personal connection does Chris have with Payload CMS?

Chris discovered that the Payload team is located in Grand Rapids, Michigan, where he is also based, and he looks forward to meeting them.