It works fine in the playground but locally (studio or docker) I don’t get the options (single, plural, etc). This is on Windows maybe I need to try a mac?
That's definitely the most confusing implementation of custom post types I've seen, but probably because I'm used to different interfaces. I do see how it's simplifying the process and putting everything you need right into the editor itself. Curious to see how this evolves!
This is a great start! It's visual custom post type and custom fields creation all in one process. It's almost like the natural progression for pattern overrides and content only editing. Those are pseudo custom fields, and now we're getting closer to actual custom posts and fields with blocks. Still not sold on the name "bindings" for linking these things together. That could use some UX writing.
Thanks for sharing. One will have to think carefully how one uses categories and tags, and how one designs the Custom Post Types to go with it. An interesting challenge.
Like to see how it can be used for portfolio post types, among other most used post types. How it can be meshed to sliders , grids of cards. And linking from posts. And other connections ie looped filtered lists from from our home pages. Keeping this key cms super power simple and flexible.
These custom fields fulfill the basic needs for creating cards, pricing tables, team presentations, and more. That's where most people use them. But this time, without any plugins. Today, I usually need 2-3 plugins to create custom post types.
It should definitely be in Core or something similar and linked to fields models with Schemas would make it a perfect replacement for Metabox/ACF with great SEO.
Interesting. I would normaly use CPTs, custom fields, relationships and so on with templates applied etc. One little hiccup in the demo though I see as a nice feature, where you stated that you can't add extra blocks and then you do! Looking a that from another angle, one can design out the CPT, in almost a fixed templated way at the top and then, if you are feeling creative keep adding free form content below. There are often times that I would have need of such a use case.
Yep for sure. In this instance you can’t add to the model on the page, but you could add additional content. I’d suspect if this matures and become real we might see that part go away or have a different way to deal with it.
@@WPMinute That is actually the part I dislike. Thinking from a client's perspective, having them complete a "form" with validation and such feels safer/better.
My way of remembering your name: the German detective series from the '80s with Götz George playing Horst Schimanski, a character known for his gritty, no-nonsense approach.
Maybe I am the only one, but I really like the “non design binding” as it is now, it makes the content can be used in any design throughout many years to come. I never understood people adding the content in the builder, locking it in. The same goes for the Gutenberg builder, I much rather have plain content in the editor that can be used, called into other designs and templates.
Having this in core would be awesome HOWEVER I was just in a TH-cam live session and Mark S said that the WP team will not be developing this any further. What’s up with this?
He did not specify how he heard this. It was in the comments during Kevin Geary’s session on August 09, 2024. A few other people commented on Mark’s comment, but Kevin did not discuss. (I’m sorry, I don’t know how to spell Mark’s last name…) A loss if Mark is correct. I watched your presentation 15 minutes prior to Kevin going live, and was looking forward to this feature, despite the less-than-stellar name.
I don't want to be too harsh; if this is an early version and the result of a sprint, it's super impressive! It's just it looks like everything that's wrong with Gutenberg: obvious and vast potential, but underwhelming UI. You're clicking all over the place - left, in the block in the middle, then in the block settings on the right... Yes, I know it's getting better once you got used to it, but this is so bad for novice users.
@@WPMinute wait? is this true? that's a bummer.. i can see the potential on developing a third party app.. If they will just build some hooks for us to developer :(
Thanks for showcasing our project! It was super fascinating (and helpful) to hear you explain it 😊
Interested to see how it progresses!
It works fine in the playground but locally (studio or docker) I don’t get the options (single, plural, etc). This is on Windows maybe I need to try a mac?
That's definitely the most confusing implementation of custom post types I've seen, but probably because I'm used to different interfaces. I do see how it's simplifying the process and putting everything you need right into the editor itself. Curious to see how this evolves!
We might need onboarding tools for all aspects 🤔
I agree but not everyone likes the odds. It's just a matter of time and everybody's gonna use it anyway 😅
Thats how you know its done by Automaticc
This is a great start! It's visual custom post type and custom fields creation all in one process. It's almost like the natural progression for pattern overrides and content only editing. Those are pseudo custom fields, and now we're getting closer to actual custom posts and fields with blocks.
Still not sold on the name "bindings" for linking these things together. That could use some UX writing.
Correct. Bindings is reminiscent of Template Parts :)
Can't wait to get native custom fields in Wordpress
Thanks for sharing. One will have to think carefully how one uses categories and tags, and how one designs the Custom Post Types to go with it. An interesting challenge.
Like to see how it can be used for portfolio post types, among other most used post types. How it can be meshed to sliders , grids of cards. And linking from posts. And other connections ie looped filtered lists from from our home pages. Keeping this key cms super power simple and flexible.
These custom fields fulfill the basic needs for creating cards, pricing tables, team presentations, and more. That's where most people use them. But this time, without any plugins. Today, I usually need 2-3 plugins to create custom post types.
Wow, what a great move by WordPress!
It should definitely be in Core or something similar and linked to fields models with Schemas would make it a perfect replacement for Metabox/ACF with great SEO.
Interesting. I would normaly use CPTs, custom fields, relationships and so on with templates applied etc. One little hiccup in the demo though I see as a nice feature, where you stated that you can't add extra blocks and then you do! Looking a that from another angle, one can design out the CPT, in almost a fixed templated way at the top and then, if you are feeling creative keep adding free form content below. There are often times that I would have need of such a use case.
Yep for sure. In this instance you can’t add to the model on the page, but you could add additional content. I’d suspect if this matures and become real we might see that part go away or have a different way to deal with it.
Frontend editing permission and we are basically in the future
Not sure this is better/easier than something like ACF but thanks for sharing.
I like the visual aspect IMO
@@WPMinute That is actually the part I dislike. Thinking from a client's perspective, having them complete a "form" with validation and such feels safer/better.
What will happen to ACF project if it is successful... This should've implemented years ago. Glad to see it now at least.
I’d say it still exists for a while. This is just a concept as of right now.
Me at 9:15 - 😑😑😑😑
My way of remembering your name: the German detective series from the '80s with Götz George playing Horst Schimanski, a character known for his gritty, no-nonsense approach.
This guy gets it
Mark, I saw your comment during Kevin Geary’s TH-cam live session on August 10 about the project not moving forward. Any more details on this?
@@tjsayers5428 Matt and I recorded a full video on it earlier today. Matt should be releasing it soon, stay tuned!
Maybe I am the only one, but I really like the “non design binding” as it is now, it makes the content can be used in any design throughout many years to come. I never understood people adding the content in the builder, locking it in. The same goes for the Gutenberg builder, I much rather have plain content in the editor that can be used, called into other designs and templates.
Fair points!
It's like Mark made an appearance in the video without needing to even be on the video 😂
I gotta stop giving him so much air time.
Having this in core would be awesome HOWEVER I was just in a TH-cam live session and Mark S said that the WP team will not be developing this any further. What’s up with this?
How does Mark S know that?
He did not specify how he heard this. It was in the comments during Kevin Geary’s session on August 09, 2024. A few other people commented on Mark’s comment, but Kevin did not discuss. (I’m sorry, I don’t know how to spell Mark’s last name…) A loss if Mark is correct. I watched your presentation 15 minutes prior to Kevin going live, and was looking forward to this feature, despite the less-than-stellar name.
It was Tuesday, August 10 (not the 9th) sorry
I don't want to be too harsh; if this is an early version and the result of a sprint, it's super impressive!
It's just it looks like everything that's wrong with Gutenberg: obvious and vast potential, but underwhelming UI. You're clicking all over the place - left, in the block in the middle, then in the block settings on the right...
Yes, I know it's getting better once you got used to it, but this is so bad for novice users.
Well the "good" news is, we found out this won't be coming into WordPress. :)
@@WPMinute wait? is this true? that's a bummer.. i can see the potential on developing a third party app.. If they will just build some hooks for us to developer :(
@@realmercs Yeah, I covered it here: th-cam.com/users/liveYZ9t5VvkhmM?si=82aSRtK0ynFvIs8W
So we don't need ACF anymore?
You still do.
This was before or after ACF stole?
Model is a JavaScript term for an object type. I guess you didn’t “Learn JS deeply” 😅
Nope