Skip to main content

9b - Developer Documentation — Community Sessions & Finalization

Contractor: TBA

Main Contact: TBA

Start date: 1 September 2027

End data: 30 November 2027

RFP not published yet

Abstract​

The two recorded community sessions ensure that the "Accessibility for Joomla Developers" guide from Milestone 9a reaches developers who prefer active learning, and the recordings remain a permanent resource for new developers joining the ecosystem after the funded programme ends. Publishing the sessions before the final external audit in Milestone 10 gives the community time to ask questions, surface edge cases, and begin adopting the new patterns, turning the final audit into a validation of ecosystem-wide adoption.

Milestone 9b builds on the developer guide and reference pages from Milestone 9a, on the design system from Milestones 2a and 2b, and on the test protocols from Milestone 1a.

Scope of work​

Deliverable 1: At Least Two Recorded and Published Community Sessions​

Host a minimum of two community sessions to demonstrate the design system and provide hands-on guidance for extension developers adopting the accessible components. The sessions must:

  • Be recorded and published in a channel agreed with OSM at kick-off, such that the recordings remain a permanent, openly accessible resource after the funded programme ends
  • Be scheduled at times that give a reasonable cross-section of the global Joomla community a chance to attend live, or be split into two suitably distinct time slots
  • Be accompanied by an accessible written summary or notes for each session
  • Have themselves accessible recordings, in line with WCAG 2.2 AA where applicable (for example, accurate captions and, if a transcript channel is supported, a transcript)
  • Reflect the developer guide and reference pages from Milestone 9a, and the design system documentation from Milestones 2a and 2b
  • Include a clearly marked Q&A segment, and a documented process for collecting and forwarding feedback to OSM so that the final audit in Milestone 10 can take ecosystem feedback into account

The applicant may propose more than two sessions, more than two time slots, or additional formats (for example a hands-on workshop alongside the demonstration sessions). The minimum of two recorded sessions is the floor, not the ceiling.

Deliverable 2: Documentation and Milestone Report​

Maintain the programme documentation framework and produce the milestone completion report in the format agreed at kick-off. The documentation must also include:

  • Links to the recordings and the accompanying written summaries
  • A summary of the feedback collected during the sessions and how it was forwarded to OSM and to the Milestone 10 contractor