Most AI integrations stop at chat. Chat with a bot. Chat with a PDF. Chat with a bot that chats with other bots. It’s everywhere—and mostly unhelpful.

CMSs are a sensible technology that allows development and production teams to contribute to a site to the best of their ability. Payload CMS is a newer option with version 1.0 having been released in 2022, and brings several desirable features for fluid development workflows. As a dev who has previously architected a Contentful-backed solution, I thought it would be interesting to compare that previous experience with how I might create a similar, reliable dev workflow in Payload.

When you’re seeking improved manageability for your web application, the idea of breaking down traditional monolithic frontend architectures into smaller, more manageable segments conjures visions of enhanced efficiency and seamless deployment.

Almost any web app with authenticated users will need to send some emails. You could work around it by using an authenticated service like Auth0 or AWS Incognito, but let’s assume you’ve set up Remix with a stack that ships with built-in authentication.

Creating reusable components is often hindered by excess code accounting for each use case the components need to support. For example, a dropdown that supports text, links, buttons, and even complex components, or a text component that supports multiple different types of HTML tags, in addition to reusable components as well. In both cases, a variety of props will exist for each type of component we pass in that may need to be shared between the parent and child.

The other day I was uploading a lot of content, including images, to a 3rd party service. I put together all my objects and mapped through them to fire off requests. Nearly immediately, I blew past the API rate limiter, and my requests started failing. Oops.