At the same level as "Manager's Guide" there is a section called "User Interface Testing", which is like acceptance testing.. i.e. manual steps for users to go through, and evaluate correctness of the application by observing the UI.
Jennifer Lindner had mentioned (before the meeting) that samvera.github.io was primarily targeted toward devloper documentation, and docs for managers may not be the best fit here, and may lead to maintainability problems if managers and non-developers are expected to submit changes, since the workflow currently requires some github knowledge.
However, those of us in attendance agreed that avoiding "yet another site with documentation" was worthy enough to keep the new content at samvera.github.io.
We talked with Jenn on Slack after the meeting and there seems to be general consensus.
Also, we pointed out to Chris Diaz that he can add metadata to make is content more discoverable through the A-Z index, as well as the quick find box.
Samvera Connect working group report
Assinged to Bess Sadler, but we ALL need to help with the content. It's only a 3 minute update, so shouldn't be too much work (see action item).
(add your items here)
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.
EVERYBODY work on the Working Group Update from Samvera Virtual Connect (summer, 2017) to include things that have happened since then so that we can present them at Samvera Connect 2017 in November at Northwestern. See: https://github.com/samvera/samvera.github.io/issues/136