Set "Last Updated" by Hugo

[bilgeyucel]

Hugo has a feature to get the latest commit that to certain file. After this PR is merged, all tutorials will have the date of the last commit as the last updated date.

Note: All tutorials will have the same last updated date at first, as all tutorial files will be updated by removing `last_updated from the frontmatter.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
haystack-home	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 20, 2023 at 2:21PM (UTC)

[TuanaCelik]

To me this looks ok, let's just see what @carlosgauci thinks as the Hugo expert. Approving for now 👍🏽

[carlosgauci]

Looks good to me, the only issue I can think of is that since the last updated time can be used to sort the tutorials, a tutorial will show as last updated even if you just update something trivial, so if you go back after a few months just to slightly change the description, won't the tutorial be listed as last updated even though the content isn't really updated for the reader?

[bilgeyucel]

Looks good to me, the only issue I can think of is that since the last updated time can be used to sort the tutorials, a tutorial will show as last updated even if you just update something trivial, so if you go back after a few months just to slightly change the description, won't the tutorial be listed as last updated even though the content isn't really updated for the reader?

Hey @carlosgauci, this might be an issue in the future. However, currently, even if there is a small change in the tutorial, as we generate a new md, we update the date, unless we revert the date manually. So, for now, we can go with this approach, and if it doesn't work, we can add custom_last_updated attribute to tutorial frontmatter. So, in the frontend, it can be {{ with or (.Lastmod) (.Params.custom_last_updated) }}