Does it make sense to use snippets for customizing a theme?

I’m looking for a solution to customize my theme (Crave) in a way where my custom code is easily distinguishable from the original theme code for future theme updates. Are snippets a good way to do so?

For context: I have VS Code setup with two branches linked with Githup and Shopify (dev branch and release branch). If my theme gets updated I copy the theme files into my local repository and use a diff/merge editor to see, what’s new.

This is the point where I need something that helps me see, what are the theme dev’s changes and what is custom code I did in order to decide if I want the change, merge it or leave it out.

I’m just learning about snippets and wondering, if the {% render %} tag would be a good visual indicator when comparing code, that this is where I added something to the theme myself.

@Liddell - yes snippet would help you to keep your code completely separate and by that way you can call it multiple times in multiple pages too, it would reduce the complexity as well

What I do is to copy the templates, and rename it with a prefix and than select it from the backend for the product for example. Some of the stuff can’t be done with snippets I think.

Or am I wrong?

Also I use only branch in total. From one directory on my machine I am using “theme watch” for the preview theme and on a different directory I use “theme watch --allow-live” for the prod theme. Once the thing looks good in the preview I commit it and pull it into the prod directory.