The Big Headless CMS Lie (James Mikrut) 

About to recommend a headless solution to my company, payload is my top choice. Incredible work!

You can tell this bru has alot of experience. So many similar pain points.

Oh yeah, James, if you bring Payload into Next.js natively, I will rewrite all my Remix and Astro applications back into Next.js 14 again.

Great presentation. I totally feel your pain points as I currently feel them too. Building websites driven by CMSs used to be fun, now with the headless approach, I feel way more stressed when it comes to deployments, I gotta spit types all over the place and can't easily share them, I have this ugly separation of concerns between the front and backends, which was meant to be a developer's dream, but instead that dream has become a nightmare, for content editors and marketing users too. Broken or sub-par previews and ultimately, going headless was pointless as no one else actually needs access to the content from outside of our website. Going all in on Nextjs makes perfect sense. As you say, you get everything in a single repo, shared types, local API which can be utilised with server actions etc. and with REST & GraphQL access to the data should anyone else need it, it sounds ideal to me.

Really like the thoughts being put into Payload!

it sounds like a traditional CMS for next js folks

We've been doing wp + next at a place where I work, and I can see these pain points, the majority of the problems we see are not in building the project, but rather from handling the decoupled setup that we created. My current idea to try to combat this is to go back to just doing custom wp themes, but with twig, htmx and alpine, I get a decent SSR/CSR FE DX with a declarative syntax in a traditionally server first environment, I use twig for separating the components, handling their props and doing templating logic on the server side, on the client side I have alpine for any client side logic and htmx if I want to talk to the server without refreshing the page. Oh, and I just turn on a good caching plugin and I effectively have incremental static regeneration, static assets hosted on cdn with very little setup and maintenance.

4.0 will probably be like what happened for tanstack, payload becoming a framework agnostic core

I started to learn code 1 year ago. I’m stop trying to get past the cli errors. Maybe one day I’ll start to write code instead of being shunned by it.

I want this!!!! DO IT

The CMS is never for the developer, but it can get in the way of the developer...

Do it!

a few hundreds Ks of JS is actually a big thing, most web pages don't serve a 10 MB video, the tech should scale from simple static content to complex UI or big content, a simple page should not load and parse big scripts if it's not necessary, it should be mostly static and use very few CPU resources.

Thumbs up for a Counter-Strike mention

Thank you. I thought im only one who struggled with deploy

It’s hard to take someone seriously when he claims “I’ll say everything to get money”

6:51 “if you don’t even build with an API” - exactly - What year is it? … Asking a hypothetical question on stage of a service paddling server-client rendering and coupling like its the 1990s PHP again.

People peddling headless cms tryna tell people the whole thing going to have to go through a build step to see your content updates 😂 and then the build fails 😂

Counterstrike actually works on Mac. I speak from experience.

I think Nuxt does all this already

100% windows for CS Go. I'd have a beer with this guy

I mean they want to piggy back on Next.js but I don't think the direction it is going is necessary great. Headless approach still seems like a better option in the future for exactly the same reasons he told his clients. Those were valid points and still are even if they went over clients heads.

Since when Channing Tatum become a developer? btw loved the presentation, James.

serverless ✌️⭐️

is that new kinda wordpress

I stopped listening after I heard: "I would say anything to make money".

I hate webpage more than a wart that screams only on hot dates

ofc he's a cs player

so just further dig into giving facebook control of our frameworks and services... it's like entirely disregarding vendor lock-in