PayloadCMS: Open-Source, Fullstack Next.js Framework
1–10 of 86 posts
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#2Yo dawg, i heard you like frameworks!
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#3Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#4So let me get this straight... PayloadCMS is a framework, for Next.js which is a framework for the React framework. Yo dawg, i heard you like frameworks!
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#5Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#6I get it takes care of content and they mention Stripe, so that is good. But is this WP compatible layer or this is accidental use of shorthand for something else?
It is more like those templates that people use to jumpstart sites, I think this can be very useful.
I don't want to sound too complainy over the free code you can get and examine yourself, maybe adding thumbnails of 3 templates would be fantastic.
Overall some clarity would be great, maybe developer should talk to someone outside his little circle and explain and see what they should include.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#7This was obviously posted in the wake of the WordPress drama, but I landed on Payload while feeling stagnant after 10+ years building on WordPress. Everything else I was doing was 100% TypeScript, my entire professional career had been working with metadata driven data structure, I felt right at home with Payload.
It's just enough structure (full admin area, API, GraphQL) to make scaffolding a basic site (with authentication) quite easy. I had built an app using Next 13 before Payload began integrating directly and using the local API (versus making HTTP calls to a server endpoint) is very clean. It feels like WordPress (i.e. you're editing "client" code on the "server") but with a LOT less cruft.
Because it's headless, anything goes on the front end. One big reason that WP got so big was because of the theming capabilities. Payload has extensibility by way of plugins, but it's (obviously...) not as robust as what's available in the WP plugin repo. It'll be interesting to see how these alternatives fare against the more prescriptive tools like Ghost (which does support theming, but does not support custom fields in any way, shape, or form).
That being said, I'm all in on Payload moving forward. If you're curious, go straight to the v3 beta -- it's very close to release and plenty stable, in my opinion. Happy to answer questions.
(Not affiliated with Payload, just a big admirer of their work)
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#8So let me get this straight... PayloadCMS is a framework, for Next.js which is a framework for the React framework. Yo dawg, i heard you like frameworks!
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#9So let me get this straight... PayloadCMS is a framework, for Next.js which is a framework for the React framework. Yo dawg, i heard you like frameworks!
These are examples for React frameworks: https://react.dev/learn/start-a-new-react-project#production...
Next.js is a React framework.
If Payload is a framework or not is debatable. I think it's more like a data layer around a database for a any js app and an Admin Panel (that uses Next.js now). It might be called a framework for your own Headless CMS, because it is code first. So you basically code the panel and the data structure yourself.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#10So let me get this straight... PayloadCMS is a framework, for Next.js which is a framework for the React framework. Yo dawg, i heard you like frameworks!
Yes? I think this is great. IMO our goal should be to enable building higher-level abstractions on lower-level ones.