Загрузка видео...
Не удалось загрузить видео
Instead of taking over ACF, WP should have just had a "fields" feature. In 2004. ACF was the first plugin I installed when I had to use WP. It inspired a lot of what Payload does and we're a nice transition for WP + ACF devs looking to jump ship.
13,463 просмотров • 1 год назад •via X (Twitter)
Комментарии: 11

The timing of this WP drama couldn't be better w/ Payload v3 launching. Excited by the future of @payloadcms and have been having a great experience with it (and the team) thus far. I've done everything to avoid WP over the years, it's just crazy to consider in this day and age.

Ecommerce (Shopify) apps also need Collection / Nesting enhancement. Metafields in Shopify is blindingly difficult.

100%. how have they gotten this far without that? it's hard to do well, i'll give them that. but it's inexcusable

God I love Payload so much. Thank you for building something that let me escape from WP bodge hell

no, thank YOU for being in our community!

WP stopped evolving many years ago. Many missed opportunities ACF is just one of them, they could have had a first class Headless API support, GitOps, Migrations.

Accurate. Kinda went backwards in some spots too, like Gutenberg introducing magic HTML comments into post content. Could have made that whole API store proper JSON but nope. HTML string with magic comments.

Same! Time to move to payload!

💯 WP is nothing without ACF and Payload has it baked in.

Absolutely! Other CMSes, like Drupal, have had something like that for that long

Steps to Creating a CMS: 1. build a good fields API 2. everything else
Похожие видео
Sensitive content
“A lot of the people who identify as trans… just want to escape. I was sexually assaulted when I was 12. I also had a lot of men use me for sexual things. I was groomed as a child by people online. I didn’t want to be female because of how people treated females.”
Genevieve Gluck
128,227 просмотров • 1 год назад
