DocsWP — WordPress Help

Recap for Training Team meeting June 29, 2021

Slack Log  (Requires Slack login to view. Set one up if you don’t have a Slack account.)

The agenda for the meeting can be found here

1) Introductions and Welcome

Attendance: @azhiyadev @webtechpooja @courane01 @chaion07 @evarlese @manzwebdesigns @Gudrun Frank @thisisyeasin @ashiquzzaman @paaljoachim @wpscholar

Over the past week, @theapril, @Afshana Diya, @JuanMa, @Ivan, @caseymilne have joined the Training team

2) News

@azhiyadev and @courane01 did meet to test out blocks in the widgets and thankfully didn’t run into too many issues.

Our content on Learn around using widgets at the moment should be added to the July sprint to revise.  We can use the revision tool to get the articles ready for the 5.8 version which is releasing on 20 July.

A custom plugin, #meta created for Learn and recently implemented by #docs.  It restores the workflow we had with GitHub.  We can save articles as a revision and have them approved/ready for the upcoming release.

Classic plugin is used to append to the articles, but all screenshots of the Appearance > Widgets interface and Customizer > Widgets will need to be redone, along with some content. 

Call for an audit of the existing lesson plan for the new WordPress release. Locating content to update based upon releases is an interesting thing.

@zzap and @courane01 will meet on Friday for a discovery session on how #docs audits all the help/devhub content to better identify that info for a joint proposal across teams.

#marketing has been a huge help in asking questions about what we need and helping us draft a proposal as a wider cross-team initiative.

For testing @annezazu published this one recently: https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/.

And the next office hour on Friday will open for a Zoom meeting for testing as a team if others are interested. 10am UTC.

  • This is an informal session, helps us get more familiar with what is coming, and identify what content we’d need to revise on Learn.
  • If you’re interested in joining, check the channel Friday morning at that time.

@evarlese @harishanker and @angelasjin did a ride-along session this morning.  They showed how they take workshop submissions through a vetting process and discussed all the organizing behind the scenes that happens.  Several of the #training team folks were present. We will publish the replay of the session and links to the many resources as a post on the Training team P2/blog.

3) June Sprint

For work that we already have in progress, we will be moving anything that is currently being worked on to July, which includes;

Following lesson plan have an owner, 

@paaljoachim said that “Setting up a local WordPress Development Environment for Core and Testing a Trac ticket” or a Github PR are both Lesson plans. He trashed both and submitted the workshop instead on which @azihyadev said anyone other will pick that lesson plan later to draft and will take reference from the workshop.

We have the following which are being worked on in collaboration, these will continue to stay on the list. 

4) Stakeholders Meeting

We don’t have anything formal but we are working with a few of the other Make teams – hoping to formalise something in July.

5) July Sprint

We’re in discussions with @evarlese and @Hugh Lashbrooke regarding the next steps for July. If there is anything that you feel we should aim to tackle, please let us know. I’ll get the agenda for next week up early so that people can comment. We’ll then take the next meeting to go through it.

6) Upcoming meetings

#meeting