Not sure if this is the right category.
I was wondering if there were any way to implement a new feature on WC that kept a log of each time you updated your skin (not description edits.) I'm particularly thinking of DX, but this might apply elsewhere. The reason would be to facilitate a component, or what have you, in DX that can automatically check your WC skin updates page to see if the skin has been updated, and then alerts the end-user that a newer version exists, so they can redownload.
As far as I know the only way to do this is to get your own website and maybe program the widget to look there. But I wanted something that tied in with my existing WC site. So, I thought I could write a script that looked through the source code of my gallery page to find the name of the skin in question, and followed the related link to the skin's main page whereupon it would check a (manually added) update list in the description for newer versions.
So long as I knew ahead of time what the name of my skin would be, and put the right phrases into the description, I think it could work. Any WC implemented update tracker component, I think, would have to rely on the skin name rather than skin ID, as the skin IDs are only generated after uploading. I also imagine the settings could be configured upon exporting (check whether or not you want to use the tracker, enter your website url, final skin name, etc.)
I especially would want this for the project I'm working on now, as I imagine suggestions would come down the line for new features and I would be updating it. I've run into this situation with the weather template, and while I don't think it's so hard to update and re-up, I'm sure there are people who DLed the first version and do not know that a newer one (with a significant change) exists. Such as it was, I had to communicate with several authors.
That said, there would have to be a way to customize the "Hey, a newer version exists!" message so you can give some skin-specific instructions. E.G, for my templates, it wouldn't make sense to tell an end-user to redownload my template when they actually downloaded someone else's widget which used the template. In that case, the author using the template would need the ability to set the Update Tracker component to check their specific widget's update list, and leave a message pointing the user to their site. So, if I change my template, the author with the template knows and goes to change their widget, which would then alert the end-user.
Does any of this make sense? Sound useful? Thoughts?