Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timestamps and authors on wiki and blog post #780

Open
hannesm opened this issue Dec 7, 2022 · 3 comments
Open

timestamps and authors on wiki and blog post #780

hannesm opened this issue Dec 7, 2022 · 3 comments

Comments

@hannesm
Copy link
Member

hannesm commented Dec 7, 2022

from #777:

I'm pretty confused about two things:

  • why can such a timestamp exist? isn't it used for e.g. the atom/rss feed (do we still have an atom/rss feed with the recent website updates?)
  • is there a requirement for an author of a page? what is the meaning thereof (I understand it's nice for blog articles, but e.g. the security process / security page is basically written by the mirage core team, no?)

It also feels pretty strange to me to have dates in the "metadata", isn't it all stored in a git repository and couldn't git's data be used for figuring out a publishing and last update timestamp? as canopy did nearly a decade ago...

@TheLortex
Copy link
Member

why can such a timestamp exist?

It's integrated in blog post pages and used for the rss feed.

is there a requirement for an author of a page?

I think it's part of the template we use, but it could be made optional.

isn't it all stored in a git repository and couldn't git's data be used for figuring out a publishing and last update timestamp

I'm afraid the git metadata was lost when files were moved around for the new architecture and design.

@hannesm
Copy link
Member Author

hannesm commented Jan 9, 2023

I'm afraid the git metadata was lost when files were moved around for the new architecture and design.

That's sad, but git allows to track file moves.

@sabine
Copy link
Contributor

sabine commented Apr 24, 2024

I would close this issue because I think fixing typos should not advance the last updated at date, while significant content updates should.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants