Would this be a helpful thing to kept up to date, as an indicator of how current the documentation is? Should we create an issue to add this date on all pages, and to add info about the tag to the README?
Will add an issue to investigate if this is automated.
Is there a way (or good way) to tag a documentation page as out of date so that someone using the docs doesn't use out of date docs (or is aware that a doc is out of date).
Do we need some sort of standard way to flag a page as "known out of date" on the site?
If someone reports the information as incorrect, we can create an issue, but if it's the backlog and we know that it is out of date on the site, do we need to do anything until the page has been made current?
Versioning - How to get rid of duplicates in the left menu without having the older versions not highlight a menu location at all?
We need to investigate a better way to display the version differences. Right now, the menu is messy, but something like the DSpace model is cumbersome.
PR acceptance checklist
Should last updated date be added to the PR acceptance checklist be added?
Adding an issue to identify what should be in the check list.
Pick facilitator / notetaker for next time
Notetaker is responsible to copy template agenda into a new agenda for next meeting and add any followup items immediately.
Next meeting 8/8
Note Taker: Drew
Note: Lynnette will be facilitating the collections sprints, so not writing documentation for this group for the next 6 weeks or so.