Payload CMS looks very promising to me. As someone who wants to move away from WordPress (and PHP) for a while now due to it's many incompatibility issues, slow performance and bloaty CMS, I have been on the lookout for a good CMS that offers both future-proof and customer friendly layout building but still allows for a lot of developer freedom, this looks like it might be the thing I'm looking for. By the way, great job on the beautiful CMS dashboard, it looks incredibly clean. Hope to see more videos soon, cheers!
@@morespinach9832 It is not 100% about incompatibility. But wp-graphql-yoast-seo is conflicting with WP All Impot, Media Sync. Also, developing the Wordpress gutenberg blocks is not 100% straightforward. There is no support to query menus from full block website. Maybe it was added.
I actually clicked the bell on your channel because I'm really excited to see what's coming next! Otherwise, I have YT notifications turned off. Keep up the good work; looking forward to the next bite sized tutorial.
Love the simplicity and the straightforwardness and usability, and all in the typescript ecosystem! And the three different kinds of APIs I saw in the docs (local, rest, graphql) make it very usable. Quick question: does Payload have a markdown editor for texts? Or has anyone ever made a plugin for a markdown text field?
Hey there - thank you! We really love hearing this type of feedback. We have had a few people build markdown editors right into Payload. It's pretty easy. You'd just swap in a custom React component for any given text field, where the custom component would include a Markdown editor instead of the built-in text input. Then from there, you're good to go!
I know HTML and CSS (and some SQL) and have been working with WordPress for 12 years. I'm looking to make a change in this direction to improve my development skills. Where should I start and what will I need to learn to be able to develop my own advanced web applications to replace WordPress/WooCommerce and the plethora of plugins that never actually do what you think they were advertised to do? I'm tired of the amount of work that goes into forcing WP to do things it was never intended to do. I considered learning PHP and JavaScript, but now there's all these JS libraries, CSS libraries, headless, etc. I'm not sure where to start. A lot of people seem to recommend NextJS for pulling data from WP/WC. I'm not opposed to the idea but it feels like another layer on top of a whole bunch of layers. I mean, CSS in WordPress/WooCommerce+plugins is a veritable nightmare. I need advanced ecommerce, ERP, MRP, CMS, CRM, the whole nine yards.
It's really great, I already used Strapi CMS and there wasn't this flexibility to not allow customer to access other customers content, it looks really simple with Payload ✨
Hey, really enjoyed the video! Quick question, since you have mentioned there will be upcoming videos about Payload -> Does it mean those 4 bulky videos on your channel are outdated, or can they be used to learn about payload CMS?
Hi, do payload handle the database refresh whenever we adjust/tweak collections that have data in it? just wondering the best practice if we're developing web with staging version.
This looks super promising. I've recently tried out Contentful and Sanity, but not super happy with either of them. When are you going to start making the short videos on all the features?
Hey Cody! Thanks for the compliment! We're actively working on more videos. There will be one for every big feature that Payload offers.... and we've got a ton of boilerplates / tutorials / examples coming as well. Keep an eye out!
@@payloadcms Awesome, I'll keep an eye out! Going to start the migration now using the docs in the meantime 🔥. I noticed there's a 4 part series on the channel, but I'm assuming the docs would be better to follow now that version 1.0 is available?
@@Arcayne Nahhhh actually we have had VERY few breaking changes from the time that those videos were produced up to now. Those videos are still 100% relevant. But the docs are also a great place to learn from for sure!
I have followed your instructions but when the mongodb part arrives it does not ask me for the string for the payload and the application when I do npm run dev does not connect to my local mongoDB database. Do you know how I could fix it?
All you have to do is hit the `create` endpoint! It's a POST request to `/api/my-collection`. And make sure you pass in an email / password. Here's an example: github.com/payloadcms/next-auth-frontend
@@payloadcms Panda dev here. I'm surprised when i saw Panda out of nowhere while i was investigating Payload. I still think Panda is the one of the best tools for designers and developers even though we've suspended development for more than 3 years.
Hmm, so I can have an API route in Astro that calls your login route and just have payload handle the auth? Any way to have a frontend communicate with Payload on a local server (I'm using Coolify)
Correction on "frameworks like Laravel and Rails can be great on building the back-end of your complex apps, but then you're stuck having to build the entirety of your admin panel completely by yourself" There are plenty of packages that do a fantastic job for both frameworks. Laravel has Nova which is a first-party package. It's made by the creator of Laravel especially for Laravel and does an amazing job on building admin panels. Backpack for Laravel is another great tool for that Rails has Avo (I'm the author here 👋), Active Admin, Trestle and others. Avo is a new modern product, and, like Payload, it is made for developer happiness and productivity. You're doing amazing work with Payload, but we should communicate honestly in our marketing materials.
Yeah, you let me know how much it takes you in those admins to build a rich text field with plugins that are relation aware, custom display/preview per field, custom content blocks, rest api and graphql endpoints. And please eliminate the paid packages (such as yours) because we need to be communicating honestly in our marketing materials.
Each tool is made for a specific job (Avo, payload, nova). No tool is going to be perfect for every edge-case in the Universe. For your example, for such a specific edge-case, that's definitely something that no tool is going to provide that out of the box, but they can support adding custom fields like that. In Avo, for example, you have all the support to add it and fix your use case. Wanting to get paid for something you built is normal. You can't expect to have all your problems fixed for free by some strangers on the internet. I advise you to go out there and create something of value and try to get paid for it. It's not easy and I think you'll change your point of view on that. The guys here at Payload are definitely very generous for offering something so powerful as open-source and everyone (myself included) should be grateful for that. They monetize the product in a different way. I feel a bit of hostility in your message. My last point is that we should all be a bit kinder to each other. It's easy pointing to the finger. It's more difficult to show support and build something.