Hi @louie02,
Thanks for reaching out, and welcome to the ACF community! That’s actually a fantastic question, and it’s a structural detail that every developer runs into when first setting up their content architecture.
When naming your fields, we highly recommend going with more detailed, specific names rather than keeping them too simple. Using very generic field names like “title”, “date”, or “image” can sometimes cause unexpected conflicts with native WordPress database columns or other plugins. A great best practice is to prefix your field names based on the context of where they are being used, such as “event_start_date” or “hero_background_image”.
Taking a little extra time to use descriptive names not only prevents technical conflicts but also makes your PHP templates significantly easier to read and maintain six months down the line when you need to update your code.
What kind of content setup are you currently building for your project? If you ever need to share more details privately as your build progresses, you are always welcome to open a direct support ticket with us!
Best regards,
Patroba
