2022 Q1 Projects

[estelle]

We will be meeting next week (January 14, 2022) to go through current OWD project proposals and ideas.
This issue summarizes them so we can discuss which projects to take on in Q1 2022 (the months January, February, March). For reference, the Q4 2021 issues is #55 and Q3 was #42.

Continued projects

These projects were started, but not completed in Q4. It makes sense to continue them in Q1.

issue#	Driver	Topic
#50	Updating DOM guides (and completing its reference)	@teoli2003
No#	Modernizing the Learning Area JavaScript modules	@wbamberg
#61	Documenting events and representing them in BCD	@foolip / @Elchi3

Completed

For reference, the following projects were completed:

issue#	Driver	Topic
#25	@wbamberg	Markdown conversation for more of MDN.
#65	@estelle	ARIA States and Properties

Potential new projects

These are projects that have been discussed before or are new proposals. We will assess them and a stack ranking exercise will determine their importance (every SC member is encouraged to propose projects and to participate in stack ranking). Preparation drivers are people who make sure we have all the information to get started with the project if it gets prioritized by the group.

Continued Projects

• Updating DOM guides (and completing its reference) @teoli2003
• Modernizing the Learning Area JavaScript modules
• Documenting events and representing them in BCD @foolip / @Elchi3
• 100% complete BCD API data (no true/null values) @foolip & @queengooborg

Projects for consideration

• Fix how MDN distributes Polyfills @teoli2003
• WebView information on MDN
• Fixing MDN page titles
• Documenting Performance APIs
• Improving Privacy Docs
• Clean up BCD data guidelines @ddbeck
• WebXR guides @dominiccooney / @Elchi3
• Web Testing strategies [Needs better definition]
• Sidebars for content architecture refresh @ddbeck
• OWD Logo
• Branding: Open Web Docs Website @estelle
• Missing HTML attributes @estelle
• Project: ARIA widget roles @estelle
• Organise Web APIs
• SVG docs need some love

Mozilla MDN projects

Mozilla shared these MDN projects for Q4 and we might want to collaborate with them.

@Rumyra / @ddbeck Please complete this section with what has been done and what is going to be done.

• Content reorg (@ddbeck)
• Documenting WebGPU (Ruth & Joe Medley)
• Demos (Ruth)
• Project Synth / contribution docs (Ruth)

[Rumyra]

Also adding:

• Organise Web APIs
• SVG docs need some love

[Rumyra]

My comments:

• Content reorg (Ruth) - I'll leave this one for @ddbeck
• Documenting WebGPU (Ruth & Joe Medley) - need to catch up with Joe about this
• Demos (Ruth) - We should still decide whether these should be held in separate repos or within content. The initial step to categorising Web APIs is proposed above as I think this will help with any reorganisation of demos
• Project Synth / contribution docs (Ruth) - static site for contribution docs is deployed and included in the meta folder within content (thanks @ddbeck ) the next stage is to move docs from the main site. (Sure Daniel has things to add here)

[dontcallmedom]

re demos, we regularly ask W3C Working Groups to produce recorded demos (typically, but not solely, as input to TPAC) (see TPAC 2021, TPAC 2020); there may be opportunities in at least nudging demo builders towards a shared repo of the underlying code for these demos if there is a community-animated one with a solid framework and visibility from MDN.

[ddbeck]

Opened a couple new BCD ones on Florian's advice before the holidays:

#80 - regularizing the structure of compat data for CSS, etc.
#79 - implementing a linter that can inspect the entirety of the compat tree, to clamp down on certain sources of incorrect data

Content reorg (Ruth) - I'll leave this one for @ddbeck

Not ready to act on this one just yet. Depends on some prioritization on our side, which isn't done yet. Much more optimistic about this for Q2.

[Elchi3]

Closing. Q2 issue is this one: #95 Feedback welcome.