In an effort to ultimately remove all (unnecessary) third-party code (especially paid), we should remove ACF Pro. While it is easily affordable at $49/yr and makes development much quicker, we'll get more value out of keeping our efforts aligned with what's happening in WordPress Core—without third-party help.
Also, the less third-party code we use means the less known security vulnerabilities our code contains for attack. It also means our code only contains necessary features, which also reduces vectors of vulnerability.
We're currently using ACF (Pro) for the following functionalities and data:
Portfolio post type custom fields
[ ] Create custom editor panels and postmeta
[ ] Migration script to copy ACF field values to custom postmeta values
[ ] Deploy: Spot-check the portfolio posts on production to ensure the ACF field values match the custom panel values
In an effort to ultimately remove all (unnecessary) third-party code (especially paid), we should remove ACF Pro. While it is easily affordable at $49/yr and makes development much quicker, we'll get more value out of keeping our efforts aligned with what's happening in WordPress Core—without third-party help.
Also, the less third-party code we use means the less known security vulnerabilities our code contains for attack. It also means our code only contains necessary features, which also reduces vectors of vulnerability.
We're currently using ACF (Pro) for the following functionalities and data: