2026-03-11 Documentation Working Group Agenda/Meeting Notes

Zoom Meeting Info

usually the second Wednesday of the month, 09am -10am EST / 15-16 CET / Time Zone Converter

https://openlibraryfoundation.zoom.us/j/89637604553

Meeting ID: 896 3760 4553
Passcode: FOLIO Meetings with Zoom

Attendees: @Ludwig Liebl @Laurence Mini @Molly Driscoll @Ben Taylor @Lola Estelle @Stefan Dombek @Aaron Neslin @Martina Tumulla @Julia Schauner @Alissa Hafele @Amanda Ros

Meeting recording:

Item	Who	Notes

Item	Who	Notes
Housekeeping	Ludwig	Note taker for today: Laurence Mini Next meeting is on April 8th at 9am EST / 15 CET Note taker for next meeting: Emma
Convener Role	Ludwig/ Julia	Julia will succeed Ludwig as convener of the doc wg in April.
Trillium release	Lola	Clarification on when documentation is due. The Trillium branch in Github should be created at the end of April, after which PRs can be submitted. Documentation should be completed one week before the general release date. General release date is currently May 29 (as always, this is subject to change), so documentation is due May 22.
Trillium branch of documentation		Julian is going to open the Trillium branch end of April.
Serials doc	Ben Ludwig	Do we need to discuss this? Ben via Slack Hi, to whoever writes the documentation for Serials, can I suggest an addition/clarification on publication pattern templates? I copy here what Owen Stephens told me: in Sunflower the pattern templates can only be added via the API. In Trillium there will be a UI for this. Documentation on how to add pattern templates via the API in Sunflower is at Publication pattern templates I came across this because I was confused as to how to make or access a pattern template in the UI. Thanks. And apologies if this is actually mentioned in the documentation and I have missed it. Ludwig will contact Franziska about this.
	Molly	How should we verify which Capabilities / Capability Sets should be included in the documentation? Researching capabilities is tricky. Molly shared an example of a capability which is newly exposed by the new capability system, but does not need to be documented. Agreement was that documenters should check with the POs as to which capabilities should be included. [Note, didn’t think of to say in the meeting, but I’ve generally relied on reviewing the jiras to see if any new permissions were created.]
BACKLOG		We did not discuss these backlog items today: Topic documentation archive + navigation in the different releases still open: first idea: use flower symbols from the releases on the top open Contact to Julian concerning Docsy Upgrade still ongoing: 1st step update search engine, then theme Finding a new place for "Install FOLIO", e.g. in GitHub open