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?
PayloadCMS: Open-Source, Fullstack Next.js Framework
51–60 of 86 posts
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#52Earlier quoted context omitted.
A common misconception. React is a library. 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 fi…
> React is a library Can a library have compiler?)
React Compiler is just a babel plugin for automatic performance improvement, memoization specifically, for never perfectly memoized React code.
Can library have compiler? Well why can't it? For example stdlib has a compiler, because C does.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#53Earlier quoted context omitted.
A common misconception. React is a library. 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 fi…
React hasn't been a library since they added hooks. Hooks themselves are just a solution to async code, but the implication was that react was no longer a state-based UI rendering library and became a full blown frontend framework.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#54Earlier quoted context omitted.
A common misconception. React is a library. 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 fi…
React was a library before hooks. Now it is a framework and decides when your code runs, not you. And now it is a terrible framework with server components.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#55Earlier quoted context omitted.
React hasn't been a library since they added hooks. Hooks themselves are just a solution to async code, but the implication was that react was no longer a state-based UI rendering library and became a full blown frontend framework.
Can you please guide me where this heresy is being spread?
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#56Earlier quoted context omitted.
how does it compare to Django as far as battery-included goes
NextJS instead of templates. Full-featured admin area. I'd say Payload is more akin to Wagtail than Django itself. It feels ridiculously modern compared to other CMSes I've touched, Wagtail included. Payload doesn't prescribe i18n like Django. When you need to, you can step down into NextJS and write custom endpoints and the like.
Not sure what you mean?
> When you need to, you can step down into NextJS and write custom endpoints and the like.
I don't think you were necessarily implying otherwise but one of the Django mantras is "It's just Python" - i.e. you can bypass (nearly) everything Django provides and drop down to doing whatever you want with http requests.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#57Pimcore was awesome, it was clean, considering the alternatives - it was a basically a dynamic objects store which would load dynamic blocks to generate content and theming on the frontend - and editable blocks in the admin panel. It was so relatable from a webdev standpoint, and very "hackable" - I loved it.
The idea at that time was so appealing (mind you, afaik that was before React or even Angular. Jquery was a thing at that time and ExtJS, Pepperide Farm remembers...). Now it gotten much much bigger of course, but in the beginning, it kinda reminds me of this: sleek, extensible also very relateable. Definitely not made for the size of a multi billion dollar franchise, but fun to hack around while still maintaining relatively clean code.
[1] http://web.archive.org/web/20110606024114/http://www.pimcore...
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#58PayloadCMS 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 e…
Question - does the word "enterprise" make you think that the amount we charge would make it unfeasible for your org to pay to use Payload?
I don't think it's ideal that we hide all our "premium" features behind the word "enterprise" and have been thinking of alternative words / messaging to describe that.
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#59It 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!
have you seen that?
Re: PayloadCMS: Open-Source, Fullstack Next.js Framework
#60We'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.
Performance problems are usually something related to maybe missing indexes in your database for fields that you query on often, or similar. Payload itself is super thin. Can you give me an example of where you're seeing slowdowns? Maybe I can point you in the right direction.
Also I would love to hear about where Payload is not flexible enough. Extensibility is one of our priorities so if there is something you'd like to accomplish, but can't, I will see what I can do about it!