Is This The Future Of WordPress Custom Post Types?

Is This The Future Of WordPress Custom Post Types?

WPTuts

3 месяца назад

6,617 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

@joineri8806
@joineri8806 - 26.09.2024 04:59

I love this because my clients really love Guternberg. Being able to use this instead of normal form is really a big step up.

Ответить
@vovkasolovev
@vovkasolovev - 16.09.2024 01:03

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.

Ответить
@jimmucci-com
@jimmucci-com - 13.09.2024 14:37

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

Ответить
@BGdev305
@BGdev305 - 12.09.2024 01:27

"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!

Ответить
@Paution
@Paution - 11.09.2024 23:27

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 😅

Ответить
@ManoloMacchetta
@ManoloMacchetta - 11.09.2024 23:15

this is something that should have been done before gutemberg.

Ответить
@kylesandstrom853
@kylesandstrom853 - 11.09.2024 22:18

I wish they would just start from scratch to a certain extent, it's these layers on layers that don't make sense. If they want WYSIWYG Webflow and others destroys them and I don't think they'll catch up building on top of this.

Ответить
@markconger8049
@markconger8049 - 11.09.2024 21:38

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?

Ответить
@GregMurch
@GregMurch - 11.09.2024 20:39

This is excellent.

Ответить
@Whatreally123
@Whatreally123 - 11.09.2024 20:08

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.

Ответить
@rubengarciajr
@rubengarciajr - 11.09.2024 19:01

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

Ответить
@kcdrummaster
@kcdrummaster - 11.09.2024 17:58

I’ve been following your content for a while, and it’s been incredibly helpful—thanks for that! You know what would be amazing? A video that covers the 'Best WooCommerce Store Setup.

I’m currently in the process of updating my store, and with so many plugins out there, it can be tough to figure out which ones I really need to create an efficient and user-friendly experience.

I’m using Elementor with a basic storefront, but I keep wondering if I should switch to ShopEngine or ShopLentor for a better experience—or is there something even better? And is CartFlows worth adding for funnels?

A video with your insights on what makes the 'best WooCommerce store' would be super valuable. I haven’t come across anyone breaking it down like that, and I think it could help a lot of people in the same position!

Ответить
@Miaccount4617
@Miaccount4617 - 11.09.2024 17:53

This is a game changer.

Ответить
@RichardWadeUK
@RichardWadeUK - 11.09.2024 17:31

Great overview mate... I've always wondered why WordPress never had its own native tool for creating post types. It's good to see them stepping into this area, however, I don't understand why they are trying to reinvent the wheel and change the process that everyone is already familiar with when using ACF/JetEngine/Metabox etc... I can see this getting fragmented, and ultimately partially developed over a very long time (6 to 10years is probably soon on for v1! 🤣). Watch this space I guess.

Ответить
@TobiasKarnetzke
@TobiasKarnetzke - 11.09.2024 17:15

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

Ответить
@Clubistetk
@Clubistetk - 11.09.2024 17:06

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

Ответить
@dancielos
@dancielos - 11.09.2024 17:04

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

Ответить
@drkskwlkr
@drkskwlkr - 11.09.2024 16:50

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

Ответить
@vaughanprint
@vaughanprint - 11.09.2024 16:34

Unfortunately I have heard the same thing as Matt below, I'ts not actually going to make it to Wordpress. That said it is an interesting implementation and one little happy accident in it's making is that can continue to layout ad-hoc content below the main templated area, so top templated hero and continue with other content.

But, and there is always a but when it comes to how we should now take Wordpress as a serious platform for all sorts of sites. Nowhere in the whole gameplan is there some sort of common framework for all tools to work from and this is again demonstrated in this experimental plugin. It ties in with interoperability and standards, or lack thereof, such as proper markup with semantic tags. We don't know wether an application of a CPT here can be further extended by activating something like ACF along side it. In fact turning on and off any of the CPT/Custom field/ Relationships solutions should be seamless and in fact those should be more or less refundant because core should be making this functionality with feature set part of the install, if Wordpress wants to consider itself a heavy hitter beyond its blogging roots. Same goes for content and layout tools, block editor/FSE or builders, whatever you want to call them. They should be able to work interchangably on the same markup and css.

Ответить
@BrianCoords
@BrianCoords - 11.09.2024 16:30

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

Ответить
@NickKask
@NickKask - 11.09.2024 16:17

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

Ответить
@WPMinute
@WPMinute - 11.09.2024 16:11

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.

Ответить
@videographics1
@videographics1 - 11.09.2024 15:54

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

Ответить
@pierres_blog
@pierres_blog - 11.09.2024 15:40

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.

Ответить
@derek-hanson
@derek-hanson - 11.09.2024 15:23

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“ 😂.

Ответить
@obito-269
@obito-269 - 11.09.2024 15:19

6-10 years... 👍

Ответить
@antonichristian5845
@antonichristian5845 - 11.09.2024 15:12

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.

Ответить
@nickm1049
@nickm1049 - 11.09.2024 15:01

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

Ответить
@TiagoSLoureiro
@TiagoSLoureiro - 11.09.2024 14:43

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
@maxziebell4013 - 11.09.2024 14:12

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

Ответить