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

Add "date updated" to guidelines page #48

Open
jenniferward opened this issue Dec 5, 2024 · 4 comments
Open

Add "date updated" to guidelines page #48

jenniferward opened this issue Dec 5, 2024 · 4 comments
Milestone

Comments

@jenniferward
Copy link
Contributor

We should have a date on the guidelines page somewhere in some form, so people know when it was last updated in case we need to check something or in case the website is cited elsewhere. I don't know what the best approach would be or what should count as an "update."

I was thinking maybe a statement on the start page https://guidelines-stage.rism.info/introduction.html Last updated: 5 December 2024, or a statement on each of the individual pages?

@jenniferward jenniferward added this to the Soft launch milestone Dec 5, 2024
@jenniferward
Copy link
Contributor Author

Just pointing to a display I like: the RDA Toolkit has a section called "Recently updated instructions" with the update date on their start page: https://access.rdatoolkit.org/

grafik

It might not be practical for us to include dates for each individual field, but the overview of new content might be useful for people who aren't frequent users.

@lpugin
Copy link
Contributor

lpugin commented Dec 5, 2024

Maybe this can be pulled from the commit messages? We could mark some to be included nor not to be included by adding a flag in the commit message. We do that in Verovio where commit message can be marked as [skip-ci] not to trigger a specific action. So we could do something similar. The question, however is:

  • Which repository? (muscat-guidelines or muscat-guidelines-site) ?
  • Where would that lead? (It can easily point to the commit message, but that might not be very helpful)

@ahankinson
Copy link
Contributor

In RISM Online we take it from the tag on the “main” branch, not from the commit. This means that to publish a new version you simply need to add a new tag.

I also do it for all the various repos involved so you don’t really have to choose between guidelines or guidelines-site — do both?

@lpugin
Copy link
Contributor

lpugin commented Dec 6, 2024

Using tags is a much better way to do it.

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