@brandon the challenge it's not ACF itself, the challenge for the switch to #craftcms is most likely ...
- learn to use Composer, especially deploy with it (many devs still use SFTP upload to just upload the updated child theme directory)
- replacing the plug & play approach - install a theme, add plugins which already ship the frontend code and display stuff
- offer alternative to the page builder approach like Elementor, Divi, etc.
- WP has pages and blog posts structure by default
1/
@brandon Agencies and freelancers could be convinced, they maybe rely on a more professional approach like https://roots.io/sage/ already. Which is more like CraftCMS.
But the cost to switch is building a new base theme for them and getting confident in deploying and running craft + getting confident / choosing the best plugins. Just one example: Selecting a forms plugins - since this is crucial.
The pathway could be improved for making the switch? Currently it's a lot of work to start? 2/
@brandon @reitzenstein Awesome!! 🥰🎉
Just optional feedback:
As agency dev I had to implement more "reference / project directories" with filter, search, hierarchy, breadcrumb, tags, custom url slug, navigation, etc. - than I had to do news/blog sections.
Blog sections have often a similiar feature set, but you'll get these features for WP out of the box. So don't know if this will really convince devs. Building a reference/project "directory" search & filter structure is lot harder in WP.