Hi Rad,
This had been suggested to me earlier in this thread (see quote in bold below) and it made sense to me at the time because I didn’t want my website to get messed up when X is next updated.
So I thought whilst my website is still new and relatively ‘empty’ still, it’d be a good thing to set up that Child Theme.
Remember, it was the tweaks I was asking about, eg the Topbar change, that made your colleague make the suggestion that I create a Child Theme.
My question is; how do I know what tweaks I would like would be better off in a child theme or not ? How would I know that ?
"Hello @JezUK,
We would highly to suggest that you use a child theme1 if what you are trying to accomplish requires a template customization. This allows you to make code changes that won’t be overwritten when an X update is released. After your child theme is setup, please review how we recommend making template changes in Customization Best Practices2.
Hope this helps."
It sounds to me as though the Child Theme is a good thing to set up in practice and then my understanding is that ONLY WHEN you KNOW that your changes are going to be part of the structure which WILL be overwritten by an update, ONLY THEN do you COPY files over to the Child Theme Folders ? Is that correct ?
In which case, someone like me wouldn’t have a clue whether what they are about to change is something that will be overwritten by an update. I think that is where my first confusion lay.
Many thanks for your assistance. I appreciate your patience in trying to explain this to me