Is This The Future Of WordPress Custom Post Types?

[@maxziebell4013]

"6 to 10 years"... I involuntarily redecorated my table with a coffee mist after that bone-dry delivery. 😂

[@WPTuts]

I couldn't resist. ;) Any my aplolgies about the coffee stained table. ;)

[@thereal_JMT_]

Maybe we're going to have a demo of etch by then 🫣

[@pierres_blog]

I think this is a good experiment and an interesting start. The ability to add custom post types, custom fields and custom taxonomies has been missing in action for a long time, for end users (power users really). I had a bad first impression after seeing the post from the Automattic developer - but I think that's because most developers can't communicate. So thank you to WPTuts for this little video.

[@WPTuts]

Let's let developers develop and educators and content creators do the explanations. 😉

[@BrianCoords]

Deep appreciation for using Lord of the Rings as your example books

[@derek-hanson]

Lots of potential. Great V1 for only 2 weeks of work. It will be interesting to see how this takes shape. I could see lots of potential with the work on data views and admin revamp. Imagine curating your admin experience around these custom content models? Could be cool. Also, than you for using a different example than “Team Member“ 😂.

[@dancielos]

I think this is great, has a lot of potential no doubt. Want to see how this turns out :)

[@antonichristian5845]

I'll say this through gritted teeth but that actually looks pretty good. I like the concept of "bindings" it makes more logical sense to my brain and the way you output it through the query loop block is pretty easy to understand. Yes it does need a lot of work but for those who are determined to use the block editor it looks promising imo.

[@Paution]

It should definitely be in Core of WP and linked to CPT models with Schema. It would make it a perfect replacement for basic usage of Metabox/ACF with better SEO thanks to Schema. I hope we won't have to wait 6 to 10 years 😅

[@Miaccount4617]

This is a game changer.

[@GregMurch]

This is excellent.

[@ManoloMacchetta]

this is something that should have been done before gutemberg.

[@drkskwlkr]

Lordy, no. The Gutenberg UI is *not* suited for CPT construction.

[@jensgur]

Or anything else in tha regard.

[@nickm1049]

The amount of blocks might get overwhelming if you have a lot of custom fields. Seems good for simple setups. But usually I take the WP editor field out of my CPTs, so I don't have to fill them out in a Gutenberg page, but rather in an admin page where it feels like I just fill out a form

[@WPTuts]

I agree - it's not a perfect solution and certainly has some obvious drawbacks. But, in it's favour, it's a far smoother implementation than the existing method of handling custom fields in WP (native).

[@nickm1049]

@@WPTuts oh for sure, much better

[@TiagoSLoureiro]

I agree, this is a step in the right direction. Unfortunately I have seen a lot of negativity towards this in the various social networks. It looks like people are just been negative for the sake of it instead of being actually critical....

[@maxziebell4013]

Yeah, I think the approach allows for a simple implementation while also accommodating more complex or individualized layouts with custom field blocks. In all the demos, they overlooked the possibility that you are actually designing the post content for a usable single view (not the template, but the content). In Paul's video, he used the custom field blocks in the loop to keep it simple. In another video by David McCan, he built a single template for the post type directly (which is also possible), but it may not be necessary in most cases. If your index template is quite plain (header, post content, footer), the post content layout from the Custom Content Model would be displayed as designed. Instead of viewing them merely as form inputs, one could leverage the design aspect of the block editor as the default single view. I hope I am making sense… it would be much easier to demonstrate than to explain.

[@WPMinute]

Unfortunately this is NOT coming to WordPress. I heard from the team and even with all the positive reaction on both of our videos, this approach is not what they are looking for.

[@WPTuts]

And why doesn't that short signted, closed mind attitude at Automattic surprise me? 😖

[@WPMinute]

@@WPTuts it’s really frustrating. I really liked this.

[@WPTuts]

@@WPMinute frustrating is definitely the word here. Not so much for the current functionality, but more for the fact that for a moment I felt that WordPress were actually listening to a large portion of it's userbase instead of ignoring their very existence.

[@BGdev305]

"6 to 10 years" for a truly final and featured pack native CPTs sounds about right. The problem is my eyes just don't like the gutenburg UI!

[@vovkasolovev]

Wordpress should have native CPT and CF, it's the basis for site development, been waiting for this since 2014. But not in this form, why pack it into a Gutenberg block editor interface? You don't need to reinvent the wheel, you need to make a similar interface as in existing plugins for this.

[@NickKask]

I'd argue that Custom Post Types are the PRESENT of WordPress...

[@markconger8049]

Anything that is usable, supported, makes website building life simpler, and can be extended by third parties is good in my view. Does this need to be part of WordPress core? I dunno. Maybe. But I didn’t think Gutenberg was worth the time and effort and still don’t. Hate it actually. So what do I know?

[@jimmucci-com]

Paul - in current state, will this plugin allow all import and exporting natively to these custom post types?

[@obito-269]

6-10 years... 👍

[@WPTuts]

If we're lucky! lol

[@Clubistetk]

Lost all hope when I saw "Automattic" in the URL

[@videographics1]

... you can see its pretty ugly, but it works. 😆🤣

[@WPTuts]

Ther's a T-Shirt design in there somewhere. lol

[@rubengarciajr]

It won't be apart of core. its just a concept.

[@Whatreally123]

I don't get the reasoning behind this when there are advanced tools like ACF available. So much time and effort spent on re-inventing the wheel. I'd rather they spend time on making other aspects of WP better and offering better blocks and more customisable blocks and features like responsive options for core blocks. Don't want to be negative but I just don't see the point.

[@WPTuts]

This isn't being coded by the core team, so nothing being developed has an impact on WordPress itself.

[@Whatreally123]

@@WPTuts thanks for clarifying that. If it's not the core team developing it, then why are people (I assume more than 1 person is contributing to this) developing this when ACF and other solutions are already there are so much more powerful and polished.

[@TobiasKarnetzke]

Everything that has to do with Gutenberg makes me feel uncomfortable.