ACF vs Classic Editor/Classic Theme vs Customizer API ?
ACF vs Classic Editor/Classic Theme vs Customizer API ?
[ad_1]
Why are many of us crazy about ACF plugins rather than any block editor, page editor, or page builder? If you just want some custom meta fields on a page or post, why use a page builder? Isn’t it a classic way?
simple. there is one source of truth with acf, metabox and similar – one important data in a table is used all over the site. you want to change a detail, you don’t have to edit 50 individual pages and risk mistakes – you edit it in one place.
good page builders are trying to make viable dynamic components that would be designed in one place, but appear all over the site – but it’s hard to do correctly and effectively, and there are too many obstacles.
It would be good if you could design a component, and use it all over the site. Acf and similar only cover data, but not the design
I think it comes down down to scale and consistency. I can make an acf block that I know will be consistent and I can add safeguards and restrictions to it. Also easier to lock these down to only specific pages or post types. Additionally, we can easily add page level data that flows outside of the main content area a lot easier with acf.
ACF + Elementor pro = perfection
The things you listed are not excluding each other, they can be used combined in a variety of ways. It depends on what you need to build, if your project is super simple there’s a good good chance you don’t need ACF at all
ACF is useful when you have templates with several custom fields of all sorts of types, and those values aren’t just used on that template, but for some reason they’re used across your website
First use case that comes to mind may be a directory website that lists a series of locations, for example with some advanced search features and filters.
With ACF and its fields you will save a lot of time compared to just using the native WP meta fields
In the case you’re describing, if the values are directly on the template and not used anywhere else, it still depends on what these values are, but yes it may be that you just add them there in some native way
Another thing used a lot in ACF are custom blocks. For many, that simplifies the development of custom Gutenberg blocks
simple. there is one source of truth with acf, metabox and similar – one important data in a table is used all over the site. you want to change a detail, you don’t have to edit 50 individual pages and risk mistakes – you edit it in one place.
good page builders are trying to make viable dynamic components that would be designed in one place, but appear all over the site – but it’s hard to do correctly and effectively, and there are too many obstacles.
It would be good if you could design a component, and use it all over the site. Acf and similar only cover data, but not the design
I think it comes down down to scale and consistency. I can make an acf block that I know will be consistent and I can add safeguards and restrictions to it. Also easier to lock these down to only specific pages or post types. Additionally, we can easily add page level data that flows outside of the main content area a lot easier with acf.
ACF + Elementor pro = perfection
The things you listed are not excluding each other, they can be used combined in a variety of ways. It depends on what you need to build, if your project is super simple there’s a good good chance you don’t need ACF at all
ACF is useful when you have templates with several custom fields of all sorts of types, and those values aren’t just used on that template, but for some reason they’re used across your website
First use case that comes to mind may be a directory website that lists a series of locations, for example with some advanced search features and filters.
With ACF and its fields you will save a lot of time compared to just using the native WP meta fields
In the case you’re describing, if the values are directly on the template and not used anywhere else, it still depends on what these values are, but yes it may be that you just add them there in some native way
Another thing used a lot in ACF are custom blocks. For many, that simplifies the development of custom Gutenberg blocks