I don't think this is a hard problem to solve, it's just outside the scope of the site generator itself. The best way to handle it probably depends on how you deploy the site, but one option would be using the at command to either overwrite the existing site files or point a symlink to the updated version of the site: https://www.linuxjournal.com/content/schedule-one-time-comma...