Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PayloadCMS: Open-Source, Fullstack Next.js Framework

github.com

Post reply on HN
Print view View original

41–50 of 86 posts

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#41

Post by 5Qn8mNbc2FNCiVV »

slig wrote: post #28
marpstar wrote: post #7

I'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…

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 and that is >>> any open source CMS (I've tried a few dozen since I am building a CMS myself)

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#42

Post by chilldsgn »

throwaway83yqr wrote: post #25
mzronek wrote: post #11

Earlier quoted context omitted.

They seem to recently position themselves as a Wordpress alternative. There is a blog post about migration from Wordpress to Payload including code: https://payloadcms.com/blog/how-to-migrate-from-wordpress-to... No, it's a Headless CMS, so no frontend themes and templates. They have an official demo page including a frontend, that you can base your work on: https://github.com/payloadcms/public-demo If you are lookin…

I think any solution that does not use PHP will not replace WordPress for most users, unless WP itself stagnates. "Anyone" can install Word press on a cheap shared hosting device and get started. That's why I think a real WP alternative will need to be based on PHP (Laravel?)

I've migrated from WordPress to Laravel-based CMS before. There's Statamic, but it's not free, though. It's good, my users love it and I can easily add functionality in contrast to WordPress, you'd have to install a plugin or dig into the digustingly messy code. Hated it.

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#43

Post by lmarschk »

PayloadCMS is looking really nice for us. However, for us a as a small non-profit organization with ~100 people having access to our systems the missing SSO feature (enterprise only) is really a blocker.

I understand what the idea is to make SSO an enterprise feature but I really think this hurts security for small and medium sized organizations as well (not only with this project, as this is a common pattern in my experience).

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#44

Post by YuukiRey »

We are using this at work. Generally I'm pretty happy with the configuration driven approach. You have config objects for all your collections where you define the types of the fields and everything else happens automatically.

With this comes a few gotchas. It's easy for an unassuming developer to change the name of a field (e.g., upper to lower case) and suddenly all data is gone in production since this affects the database. What you should do instead is write a migration.

I'm also not a fan of Lexical. It's very focused on being a good rich text editor but not on being a good document format for your clients. For example the way they render lists is, in my opinion, simply wrong (see https://github.com/facebook/lexical/issues/2951). Or this https://github.com/facebook/lexical/issues/6269. You also have the added complication of using the Payload flavor of Lexical, which can add its own complexities.

I haven't had time to look into its GraphQL API yet.

Documentation wise I'd compare it to working with NixOS. For some simple tasks the documentation is useful but for anything more complicated you want to look at the Payload source code. Especially when you start customizing the UI. Which generally works pretty well.

I wish they had thought about versioning the Rich Text somehow, so a client knows which version of your documents they get.

Overall I like it.

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#45

Post by bartligthart »

It looks like a top choice for me. But a big part of why I'm probably still going to use WordPress is because of the Gravity Forms plugin.

A place where it's easy to drag and drop forms, do conditional stuff, edit thank you messages, connect inputs to other stuff like spreadsheets, zapier etc.

If any CMS / plugin could fix that for Payload. Please let me know!

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#46

Post by theyknowitsxmas »

bartligthart wrote: post #45

It looks like a top choice for me. But a big part of why I'm probably still going to use WordPress is because of the Gravity Forms plugin. A place where it's easy to drag and drop forms, do conditional stuff, edit thank you messages, connect inputs to other stuff like spreadsheets, zapier etc. If any CMS / plugin could fix that for Payload. Please let me know!

Google Forms in iframe?

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#47

Post by jokethrowaway »

We've been using it for a year and we hate it.

Not flexible enough, performance problems, doesn't provide much ootb.

You're better off just writing a service from scratch, the time you are saving is minimal (this applies to most products before we get to django or wordpress imho)

We tried and abandoned keystone too.

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#48

Post by slig »

obvi8 wrote: post #40
slig wrote: post #28

Earlier 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 feel like everyone runs into this in WP dev eventually, but not everyone is honest with themselves about it. It can get messy, fast — I’ve certainly been there! I’d be interested to know what sort of work your plugins are doing. I think a lot of that ecosystem is there to fill gaps — ACFish custom field functionality, for example, is core functionality in Drupal, Payload and many others. Just another example — I lo…

Hi, thanks! Currently I've created a small plugin that replaces the download URL of products with a post meta `use_external_url`, appends the `order_id`, and signs it using HMAC. Then I have a CF worker that reads that, validates the signature and stamps the PDF file with the order number, on the fly, after the user clicks to download the file. (I tried some of available plugins but they sucked).

Also, I'd like to have more flexible bundles (possibly bundles of bundles), a more flexible transaction e-mail that offers upsells right after the user buys something, for instance: the user bought the Foo Vol. 1, right after I want to send an email offering a coupon so that they can get the discounted Vol 1, 2, and 3 with the amount they just paid discounted. (I can do that with Mailpoet or Omnisend if they buy just one product, or can implement multiple discounts and upsells with a little bit of JS running on my Windmill instance + Resend).

I feel like I'm going to re-invent a lot of stuff, and since I'm using Stripe, it shouldn't be so hard to think of a nice Products/Bundles/Downloadables/Gallery DB design and ship something ultra light that I can actually understand vs the million lines that a default WP + Woo install has, plus themes and plugins.

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#49

Post by slig »

5Qn8mNbc2FNCiVV wrote: post #41
slig wrote: post #28

Earlier 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…

Thank you, will check Saleor and Medusa!

Re: PayloadCMS: Open-Source, Fullstack Next.js Framework

#50

Post by slig »

marpstar wrote: post #36
slig wrote: post #28

Earlier 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.

Payload has an e-commerce template, but it definitely pales in comparison to WooCommerce. I can't speak to specifics, but if I were looking to migrate away from WooCommerce, I'd look at MedusaJS ( http://medusajs.com )

Medusa looks perfect, thanks for mentioning it.
Post reply on HN