Documentation meeting 28 November 2024

== Place ==
Video conference meeting using Jitsi at https://meet.jit.si/KohaDocumentationMeeting
* We are using an (open source) video conference platform for the discussion part of this meeting. You don't have to turn your camera on if you prefer not to be seen; but if you are able to use a mic it should make our conversations a lot easier!
* To join the meeting, click on the meeting link. If you are on a desktop computer, it will open in a browser window; no need to install anything. To join on a mobile device, you will need to download the Jitsi Meet app (from Google Play; from Apple Store).
* Browsers will ask for permission to use video and audio devices: check or review these settings if you have audio or video issues.
We will use an online collaboration pad to record the meeting minutes, including TODOs and ACTION information.
== Time ==
* Thursday 28th November 12:00 CET (check the date and time in your timezone)
== Attendees ==
Add your name here if you are planning to attend:
* Philip Orr, LMSCloud GmbH, Germany
* Aude Charillon, PTFS Europe, UK
* ...
== Apologies ==
Add your name here if you would like to attend but can't make it:
* Marie-Luce Laflamme, inLibro, Montréal (Canada)
* Heather Hernandez, SFMNHP Research Center, San Francisco, CA (USA)
* Caroline Cyr La Rose, inLibro, Montréal (Québec, Canada)
* ...
== Updates ==
=== What the team has been working on ===
Please add an update before the meeting about what you have worked on.
* ...[Please add an update about you have been working on]....
* Philip: checked the w3c images alt text guide. Nice alt text quick reference tree: https://www.w3.org/WAI/tutorials/images/decision-tree/
 * Philip to inform Mattermost about decision to stay with writing alt texts for images
=== Review of action points ===
* See previous meeting.
* ACTION: Aude to check the config file for the manual to correct the copyright statement. It should be updated to remove the date and add a link to GPL. - ONGOING
* ACTION: David is waiting to hear from Liz if access to the web logs is possible. Will consider proposing setting up matamo.org or plausible.io Update: Posted on Koha Community Chat to get ideas. - ONGOING
* ACTION for Philip and anyone who is interested: check out the W3C Images Tutorial - DONE
* ACTION Philip: decide which quick decisions we want to make for documentation naming conventions, see below
* Ongoing projects - see section below
* Documentation workflow - see section below
* Content development guide - see section below
== Ongoing projects ==
=== Automated screenshots (Jonathan, Caroline, Aude) - Bug 34076 ===
* If we need more logins for the screenshot page, contact Joubu.
* See the Guidelines document on the Google Drive for instructions.
* Summary of actions:
** ACTION: Aude to post again in December about automated screenshots to the mailing list and Mattermost. DONE 6/12/24
** ACTION: Everybody interested - do as many screenshots as possible until the end of December. At the end of December Aude will talk to Jonathan about what happens next.
=== Re-organising the manual (David Nind) - Bug 32391 - Preview ===
* ACTION: David to post a link in Mattermost Chat on the current build - ONGOING
=== Accessibility issues in the Manual (Philip and team) - Wiki page ===
* ACTION: Philip to create GitLab issues for each of the points raised in the audit. DONE, see https://gitlab.com/koha-community/koha-manual/-/issues/50 and https://gitlab.com/koha-community/koha-manual/-/issues/49
* ACTION: David to look at controlling the focus order on manual pages (e.g. skip links for the left side menu - can we override sphinx’s html builder?) - ONGOING
* Left side menu in the manual currently has no scroll bar. If you are in a very long subsection with many subheadings, it can be difficult to scroll on the left side. ACTION: Aude will log an issue in Gitlab. DONE see Issue 47.
== Documentation workflow: issues and ideas ==
Any issues or ideas for the general Documentation workflow.
* Version notes: So far, I (Caroline) have only written the main version where a feature/change happened (i.e. 23.11, 24.05, or 24.11), not the point version (e.g. 23.11.06). That was how I understood the initial assignment. However, there has been discussion in merge request 975 that we should specify the point versions.
** Heather suggested to specify in the Manual that bugs may have been backported. Philip also talked about updating the version note wording to make it clearer. All present are happy to stick with using the first version the bug was pushed to (not the point releases it was backported to).
***DECISION: We will go with only the main versions and add clarification to the manual:
*** ACTION: Aude to add a note at the top of the What’s new page as Heather suggested. DONE (MR 999)
*** ACTION: Aude to update the Wiki to suggest the version note becomes “This feature was first introduced in version 24.05 of Koha.” DONE 29/11/24
* ...
== Content Development Guide ==
Ongoing work to create a content development guide.
* ACTION: David to research options (possibly instead of using single quotes) if a button text contains an apostrophe. Update: Still under action.
** ACTION: If anyone finds an example where the apostrophe becomes a problem, please add it to the content development guidelines page!
* ACTION: David to demonstrate Vale at an upcoming meeting. This is a way to check the manual to identify content that doesn't comply with our content development guide rules (link a code linter, but for documentation rules). Update: DONE for this meeting, actual presentation to come at a future meeting :)
** David showed off a basic implementation using the Google Style Guide, Microsoft Style Guide and RedHat style guide on about.rst, it is used on a local build from CLI with the command "vale". Suggestions and warnings can be set to be ignored so you only see errors. There is a wordlist so that e.g. systempreference names are not seen as spelling errors. Rules are set in .yml files. Not integrated with Gitlab IDE atm since Gitlab doesn't have it as an extension. VSCode has an extension for Vale. It could be used locally or added as a check to merge requests.
** ACTION: David to look at adding Git Pod functionality to Gitlab at a later date or instead adding it to automatically provide a comment on your merge request in Gitlab - ONGOING
* ACTION: Philip to add a note about how to document permissions to the content development guide (see the work Caroline did with libraries and patron permissions) - ONGOING
* Anything recently added to the page that people want to review or discuss?
** Bootstrap 5 may add style differences that could be noticeable in screenshots. Since Bootstrap 5 is still being tested / changes still being made, we will wait and if necessary add issues to gitlab / for (possibly automatic by then?) screenshots.
** ...
* Questions to cover (please add yours!)
** Use cases: how can we include more of these to better show how Koha features are used together? (postponed from a previous meeting.)
*** For use cases specific to one feature: insert as another section - see SIP2SortBinMapping: https://koha-community.org/manual/latest/en/html/circulationpreferences.html#use-case
*** For workflows that encompass several features, we could have a specific "How-to" / Tutorial section? As a step-by-step guide ("1. do this; 2. do that") which points to existing sections of the manual and re-uses existing screenshot. Will need to be mindful not to re-create the FAQs and the reasons why we thought they were not relevant anymore (make sure we date / version the workflows and review them).
**** another example: when a library has to close unexpectedly, what do they have to do?
***** things like: calendar update, postponing issues and holds, adding a message to the opac… etc.
**** another example: Koha installation checklist (Koha-US) - https://koha-us.org/learn/install-config/
**** each “How-to” should be in their own page
**** We should also add links to the “monday minutes”, "every other… " videos etc.
*** We will talk more at upcoming meetings about trying out some actual examples
** We should add a general “Community resources” page to the manual containing links to Bywater Monday Minutes, “Every other…”, french resources… etc. DECISION: Yes, we will do this! ACTION Philip: Create the page in the manual
*** It would be good to sort this page by language
*** In the last Documentation Drop-In Meeting, we had some people from Bywater (@catrinab and Sara) who were interested in adding Bywater documentation to the manual - maybe the “Community resources” page would also be interesting for them
**** ACTION Aude: get in touch with them on Mattermost DONE (Documentation Workshop). Aude will get back in touch with Catrina at some point on Documentation.
**** WebAIM article about alternative text
**** Guide aimed at social media (will find the link - it is really good)
** Decision on documenting convention: how do we refer to buttons, what do we call the "Koha side menu", "Koha top search bar"... etc. POSTPONED to next meeting
*** ACTION Philip: decide which quick decisions we want to make next meeting
**** Buttons
**** Side menu
**** Top search bar
**** …
** ...
== Anything else ==
* Pages removed from Koha community website: Test bibliography (deleted), Koha bibliography (unpublished as it's quite out of date), Other docs (unpublished) - links are still showing up sometimes. Aude will check about it.
* Roles for 25.05:
* Philip will do some advertising for documentation starting 2025. Aude and Philip to meet up again in early 2025 to discuss Drop-In Meeting times and other ways to reach people.
* ...
== Reminders ==
* Find bugs to document
** Bugzilla search for Keywords=Manual, Component=Documentation
** Bugs marked with Needs documenting status
* How to edit the Manual
== Next meetings ==
* Documentation meeting:Documentation meeting 30 December 2024
Category:Documentation
Category:Documentation IRC Meetings
Category:Documentation IRC Meetings 2024