search

bssw-tutorial / bssw-tutorial.github.io

Top level web presence for the Better Scientific Software tutorial
https://bssw-tutorial.github.io/
5 stars 1 forks source link

Use more appropriate modification dates #4

Closed bernhold closed 3 years ago

bernhold commented 3 years ago

Some pages include a "Last updated" field, but at present it is really the date of the last build. That really has nothing to do with when the contents of that particular file were last changed.

Back in the old days (Subversion) there were tags you could embed in your files that svn would replace on checkout. Unfortunately that doesn't appear to be a thing for git, but we could probably script up some kind of equivalent. It would require a more complicated build process, though.

Also, for the current structure, you might want the top-level file in a directory (i.e., index.md) to reflect the most recent update date of any file in the directory. Which would be a little more complicated, but not impossible.

bernhold commented 3 years ago

https://github.com/gjtorikian/jekyll-last-modified-at looks like a potential solution.

bernhold commented 3 years ago

Installed this and modified the index and the event layout to use it. However it is not clear whether this is going to give what we want. Partly because of the way we're deploying the site. But I'm also not entirely confident what date it is getting when it appears in a layout and is being applied to another file. We'll have to see how it goes.

bernhold commented 3 years ago

Current approach really isn't working as desired. Files are "last updated" when the site was last built. Can't think of a better approach. We should just abandon it.