Thank you for reaching out and posting this question!
I just wanted to help clarify that you’re not missing anything, as our guide on updating themes does suggest that the updates do not include the customizations from the previous theme. While there is some work involved when updating a theme, you don’t need to recreate anything that is set up through the admin (eg. collections, pages, blogs, or navigations). I understand this isn’t ideal and it sounds like more work is involved; however, to summarize, there is only two aspects that you’d need to redo - the customizations in the Storefront editor and any custom coding or app integrations.
That being said, themes usually don’t require updating too often and, most of the time, this is done for new features that is needed for the store. Nonetheless, some updates may also be vastly different from their predecessors, so I’m not sure if the ability to keep all the customizations or custom coding/app integrations would yield the same results every time.
Do you update your theme often and why? Which theme are you currently using?
A bit of background on this would have been helpful for you!
I’m developing a new theme and I’m using the theme customisation to edit content on the home page.
After digging into this further, the customisation gets stored in the same file as where the blocks are setup, so obviously when I push an update to the theme, it will wipe it.
This means I need to pull down the theme before doing any work on it.
Having the content and the cms bundled together like this into one file is not the best at all and I was pretty shocked when I realised that was what was happening.
I was hoping that I can do a theme update for a theme I am also developing that will retain all the settings. If there are no settings for any settings added, it should just set those new settings to the defaults.