Appears to be open-core only https://payloadcms.com/enterprise
PayloadCMS: Open-Source, Fullstack Next.js Framework
71–80 of 86 posts
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#72Looks like I really have to buy into React in order to choose this... Kind've a non-starter.
What frontend libraries do you use?
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#73Appears to be open-core only https://payloadcms.com/enterprise
Hmm, one clarification - there is no enterprise Payload version. All of our enterprise features are just plugins - which anyone could build.
In this way, would you consider WordPress to be open-core as well, considering the amount of paid plugins there are available?
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#74Appears to be open-core only https://payloadcms.com/enterprise
Hmm, one clarification - there is no enterprise Payload version. All of our enterprise features are just plugins - which anyone could build. In this way, would you consider WordPress to be open-core as well, considering the amount of paid plugins there are available?
Maybe just one feedback item for the site: "Visual Editing" shows up at the top of a few use case pages, and in other spots around the site. When you click on it, it's not very obvious you've been brought to the "enterprise" site. Just a clearly different nav bar on the enterprise pages, or callout badge on Enterprise features would be good.
I feel like a few people could be convinced that visual editing is part of the open source base product, not the enterprise plugins.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#75Appears to be open-core only https://payloadcms.com/enterprise
Hmm, one clarification - there is no enterprise Payload version. All of our enterprise features are just plugins - which anyone could build. In this way, would you consider WordPress to be open-core as well, considering the amount of paid plugins there are available?
> In this way, would you consider WordPress to be open-core as well, considering the amount of paid plugins there are available?
Because several of those are sold by Automattic, the company that owns wordpress, I have made that argument before, yes.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#76Earlier quoted context omitted.
Hey, in my opinion it is fair to have some features behind a paywall for an open core model (although I am not a fan of it, but I really understand the reasons). But personally, I think having core security features (which I believe SSO is, e.g. also for small orgs) behind such paywall is not really helping the product. Using a free plugin developed independently from the core product does incur other issues e.g. dur…
Fair. Good feedback. For what it's worth, we are actively looking at our licensing model trying to make it easier for situations exactly like yours. Might have some updates for you soon.
yes making it working for all basic needs is the key to expand into a huge user space, from where you can find paid users much easier.
or it probably won't fly, there are also still many options.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#77This CMS appears to be a breath of fresh air amid the toxicity in the WordPress world.
Considering devs are looking at complaints/features in this thread, I will post one: In WordPress, I can copy a plugin folder from one old project into a new one and enable it in the ui without touching code or cli. I see the benefit of defining plugins through a cli tool, but I also like the copy-paste folder structure of early 00's software.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#78I've been using Payload for 18 months. They're only recently (with the upcoming v3 release) really piggy-backing on Next.js' server and routing. Before that, it was "just" a really nice headless CMS built on Node/TypeScript. This 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…
Still very very far from Wordpress, just the Yoast SEO plugin is worth the drama in wordpress.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#79This CMS appears to be a breath of fresh air amid the toxicity in the WordPress world. Considering devs are looking at complaints/features in this thread, I will post one: In WordPress, I can copy a plugin folder from one old project into a new one and enable it in the ui without touching code or cli. I see the benefit of defining plugins through a cli tool, but I also like the copy-paste folder structure of early 00…
You should try Directus! I'm using it for a project right now and it's very nice. It has the plugin folder you mention too.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#80Earlier quoted context omitted.
How easy/hard would you consider the amount of work needed to create a ecommerce for digital products using Payload? I'm currently using WP + Woo but the plugins that I'm using aren't flexible enough and I'm re-inventing some of them, so might as well re-invent some more and learn Next.
I wouldn't recommend it, I've seen it abused as a database a few times and it was never good. It really is barebones and mostly for content and the UI/features show that. You're better of using anything else, if you want a UI ontop maybe a tool like Pocketbase is better suited or you go the route of using an actual e-commerce tool like Saleor or Medusa. Both are good, definitely better than homebrewing your database…
Medusa looks amazing. Is there any catch?