3 ms·
Thought about it as well. For my static blog, I just want to expose history of changes for each post (all my stuff is tracked by git). Haven't got onto implemen
by karlicoss 7y ago
Thought about it as well. For my static blog, I just want to expose history of changes for each post (all my stuff is tracked by git). Haven't got onto implementing that yet though.
I've only done relatively small changes so far, so hopefully that is fair to people who already shared/liked. For typos/style I just change it, for bigger additions, I'll explicitly mention when it's updated.
- tkainrad 7y agoThanks for your input. Having an automated way of exposing changes seems like a great idea. I am just not so sure If I am happy with the respective post still showing up at the bottom of my /posts page because the original date remains.
- vasco 7y ago1. Make a new post quoting the old post with whatever new findings you have. 2. On the old post, add links to the newer posts with a short note like "27/11/2019: I've since found a better way of doing this, check it out"
- tkainrad 7y agoWhat kind of changes do you think would warrant a new post? Does it make sense to write a new post if only one out of many sections is rewritten? Or do you mean to somehow make a new post with only the new information and link to the old one for the rest?