Archives

Kim Parsell 6:14 am on March 1, 2014
Tags:   

Docs Chat: Feb. 27, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: @Rarst is working on fixing parser-related issues. @nlarnold1 is working on resolving issues with the handbook theme. (2/26/2014 team meeting summary)

2. Docs Issue Tracker: @otto42 unveiled the alpha version of the issue tracker earlier this week. The Docs team is providing feedback, and work continues to implement those suggestions.

3. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org: @jazzs3quence said there were some minor UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. fixes merged in this past week, and work continues on refactoring the overview. Current needs are writers to assist with tooltip creation, and people to test the plugin, and provide feedback. (2/24/2014 team meeting summary)

4. Docs Project Landing Pages: The landing pages are now complete for all four projects: Codex, Devhub, Handbooks, and Inline Docs.

5. Handbooks: Good progress was made on the PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Developer Handbook. The new outline is finished, and @hanni and @blobaugh completed migrating the existing content into the new structure. @sewmyheadon and @philiparthurmoore will be working together to get the intro completed for the Theme Developer Handbook, and begin work on the new outline. (2/27/2014 team meeting summary)

6. Contributor Events: There are two contributor events happening this weekend: the Monthly Docs Sprint at the Seattle WordPress MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. group, and the WP Contributor Day in the UK. Both events are on Saturday, March 1. If you aren’t located near either event, you can join in via the #wordpress-sfd IRC channel, and participate virtually.

#chat-recap

Kim Parsell 11:59 am on February 22, 2014
Tags:   

Docs Chat: Feb. 20, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Progress continues. Most of the template work for the code reference is done for the moment. @Rarst now has commit access to the parser repo, and will be working on changes needed for parsing the inline docs. @nlarnold1 is working on resolving issues with the handbook theme.

2. Docs Issue Tracker: @samuelsidler said we should have an initial version soon.

3. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org: Per @jazzs3quence, @brainfork will be working on redoing the help overviews due to a display issue. Work continues on adding tooltips. Version 0.6 was released Thursday – please test and provide feedback to the team. (2/17/2014 team meeting summary)

4. Docs Project Landing Pages: Landing pages were created for the Codex, DevHub, and Handbooks projects. The Code Reference falls under DevHub, and will be included there. @siobhan will be adding information to the DevHub landing page, and @hanni will be populating the Handbooks landing page.

I’ll be pulling together a to-do list of outstanding Codex tasks to include in the Codex section. We also need to look at putting together a list of Codex updates needed for the 3.9 release in mid-April.

5. Handbooks: @hanni posted the detailed plans for the Handbooks project this week.

There is now a weekly IRC chat for the Handbooks team – Thursday at 1:00 UTC (5pm PST, 6pm MST, 8pm EST on Wednesday) in #wordpress-sfd. The team held their first meeting on 2/19/2014.

@blobaugh is the new editor of the PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Developer Handbook, and is working with @hanni on a revised outline. There are also several new contributors eager to get started writing.

@sewmyheadon is the editor of the Theme Developer Handbook, and will be working with new contributors @philiparthurmoore and @nudge to move that handbook toward completion.

More contributors are needed for the Theme Developer Handbook, so if you are interested in helping, contact @sewmyheadon or @hanni via IRC, attend the weekly meeting on Wednesdays, or leave a comment on this post.

#chat-recap

Chris Reynolds 10:18 pm on February 17, 2014
Tags: ,   

AH-O₂ Update — 17 February, 2014

We’ll be releasing 0.7 this week. New in this update are initial tooltips for the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. menu items & tooltips on the Users pages.

@brainfork Will be working on reworking the help overviews. This partially came out of this ticket, where it was determined that a restructure of how the overviews are marked up may be necessary.

@ubernaut will continue to work on the spreadsheet with a focus on identifying areas for new tooltips. This makes it easier when adding the tooltips in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. to know where best to place them. The next area for focus for the spreadsheet will be the Network Admin screens. I recently opened the document up to anyone with a link to make it easier for people to jump in, flesh out areas that are bare, or claim admin pages to add tooltips to without requiring an owner to invite them to be able to edit the spreadsheet.

@nikv has volunteered to help out with adding tooltips also.

I’ve updated the tooltip documentation somewhat to add some additional details/guidance for adding new tooltips. Feedback (or edits) are welcome.
https://github.com/jazzsequence/WordPress-Admin-Help/wiki/Help-Tooltips

One thing that wasn’t discussed this week (although there’s a ticket) is the fact that the arrow location for some tooltips is pointing to the wrong place. My suspicion is that this is largely a CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. issue (or an issue that can be solved with CSS) and anyone who wants to jump in and take a stab at that is welcome. There are a variety of places where this is the case and may need to be styled individually. The main issue is a lack of specific IDs/classes to hook the tooltips onto, which could be conceivably solved in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. by adding specific classes/ids to those elements.

Our next meeting will be next Monday 18:30UTC

#admin-help, #ah-o2

Kim Parsell 4:46 am on February 15, 2014
Tags:   

Docs Chat: Feb. 13, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: There’s been a lot of activity on the developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets this past week, primarily by @Rarst and @nlarnold1. Good progress is being made on the design change tickets.

2. Docs Issue Tracker: Per @samuelsidler, @Otto42 is still working on it, and making progress.

During our initial discussions about what we would like to see in the issue tracker, several things were mentioned that aren’t included in initial development. I’ll be working through those posts, gathering a list of those items and posting that list, most likely in a Meta Trac ticket. We can review the list after development is complete, and we’ve been using the tracker for awhile to see what items we may still want to add.

3. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org: Per @jazzs3quence, the team has removed the use of title attributes from the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party., based on @grahamarmfield‘s extensive accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) review of the plugin, and the fact that those attributes are being removed from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Version 0.6 of the plugin has been released, incorporating those recommendations, and is available in the repo. Please download the plugin, test, and provide feedback to the team. (2/10/2014 team meeting summary)

4. Handbooks: @hanni provided an extensive update on the status of the handbooks, and the plans now being put in place to move the effort forward at a much faster pace. @hanni will be posting the details of these plans early next week.

We also discussed the status of handbooks being produced by the other teams. @netweb brought up a post on Make/Polyglots regarding their Handbook. If you are interested in helping write the Polyglots handbook, @samuelsidler will be posting on Make/Polyglots asking for volunteers.

5. First Steps for Docs Contributors: We received some very helpful feedback from the comments, and changes have been made to incorporate that feedback. If you have not had the chance to review it, please take the time to do so, and leave your feedback so we can get this completed. (original post | draft page)

6. Docs Project Landing Pages: I’ll be creating the landing pages for each of the listed projects this weekend so that each team can begin adding the information about their respective projects. The Inline Docs landing page is a good example to follow. We would like to have these completed by February 28th.

We would also like to thank our outgoing team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts., @sewmyheadon, for all of his hard work. We look forward to your continued contributions. 🙂

#chat-recap

Eric Amundson 5:43 pm on February 11, 2014
Tags:   

Docs Chat Roundup – Feb 6, 2014

1. DevHub Progress

Lots of progress being made on DevHub including new tickets and finalization of URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org structure. Once the handbook theme is done, the handbooks will be moved over to developer.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.

2. Docs Issue Tracker

Otto says that it’s coming along. The templates are nearly done and he’s working on some UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. bits and pieces.

3. Docs Sprint

The next Docs Sprint is Saturday, March 1 at 10am PST.

Join the sprint in Seattle, or on IRC at #wordpress-sfd.

4. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org

@jazzs3quence and contributors are making progress and have pushed recent updates to the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.. Still need testers and contributors.

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team reviewed and advised a change in the way the title attribute is handled.

5. Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.

Kim Parsell is taking over as the Docs Team Rep this week. Congrats @kpdesign and thanks!

6. First Steps for Contributors draft

@siobhan put together a draft First Steps for Contributors document and has collected some feedback already and is refining the doc. We all agree that contributing to Docs will be easier once the Issue Tracker and DevHub are live.

Full IRC Logs

#chat-recap

Chris Reynolds 8:45 pm on February 10, 2014
Tags: ,   

AH-O₂ Update — 10 February 2014

a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and title attributes

It was discussed last week at the meeting — and subsequently added to the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. — that we would take the title attributes of linked elements that had them by default, so that in the future, adding tooltips to these things could be handled the same way they already were. However, since @grahamarmfield’s extensive review indicated that this may be a problem for screen readers, as well as the fact that core will be removing them, this behavior has been removed and will no longer be present in the next (or future) iteration. (Graham, if you want to run the updated (0.6.0) plugin through your screen reader program(s) that would be greatly appreciated 🙂 )

Tooltip pointer positioning

There are some tooltips that have somewhat “iffy” pointer positions. There are various reasons for this, but the biggest one is specificity. If we were editing core, we could add our own classes or IDs and then target things specifically, then add a tooltip to those handles. Since we aren’t, and there are some elements that don’t have their own specific wrappers (for example, some column headings), we just do the best we can. (See https://github.com/jazzsequence/WordPress-Admin-Help/issues/45 for some examples). We may come back to these later and add CSS to the pointers so they can be moved specifically for those tooltips. Moving forward, if there’s a commit adding a tooltip where this is the case, we’ll be tagging this ticket so we can keep a general record of the tooltips that are having this issue.

What we’re working on

We are primarily focusing on the task of adding tooltips to the plugin at this point. While it is acknowledged that the actual help overview content may not be the best for an always-on (at least for some users) space that is not accessed via the help tabs, without enough interest in helping write new content for these overviews, we’ve had to move on to the more pressing task of focusing on the tooltips, all of which will be entirely new (rather than being able to pull in existing content in one form or another).

@brainfork will also be looking into adding tooltips to the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. menu items using a global tooltip doc and js file.

@zoerooney and @ubernaut will be working on updating the admin pages spreadsheet with a particular focus on identifying areas for tooltips. I’ve made this editable to anyone with a link to give more people an opportunity to contribute to this document (which hopefully won’t be a problem).

Testers and contributors are welcome — report any issues here: https://github.com/jazzsequence/WordPress-Admin-Help/issues?state=open

Pull requests are also appreciated!

As a reminder, our meeting time has changed from the time listed on the sidebar. Our next meeting will be next Monday 18:30UTC.

#admin-help, #ah-o2

Chris Reynolds 1:34 am on February 4, 2014
Tags: ,   

AH-O₂ Update — 3 February 2014

@jazzs3quence added a few tooltips to the Users pages. Adding new tooltips is pretty easy, but we may want to revisit our documentation to clarify some things
@brainfork closed out a few tickets, including positioning the tooltips so they aren’t bouncing around and setting the anchor tag title attributes to be the tooltip content where applicable (as opposed to our own custom tooltip content).

We still need testers and documentors as well as volunteers to help add tooltips. All of these tasks are pretty simple and should only require a few minutes of instruction. The pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. in the wp.org repo should get updated tomorrow with this week’s commits.

@jazzs3quence also created a page on github that’s a bit more friendly to non-techy peeps who want to just get the information and/or download the latest version (before it makes it to .org). That page is here: http://jazzsequence.github.io/WordPress-Admin-Help/

#admin-help, #ah-o2

Eric Amundson 6:41 pm on January 30, 2014
Tags:   

Docs Chat Roundup – Jan 30, 2014

1. Docs Chat Time

We’re changing the time of the weekly Docs Chat (not Support) to:

  • Thursday 4pm PST
  • Thursday 5pm Mountain
  • Thursday 6pm Central
  • Thursday 7pm EST
  • Friday Midnight UTC
  • Friday 7am ICT

The sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//docs is updated and we’ll see you next week.

2. Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.

We’re supposed to choose a new team rep this week, so please go comment on Siobhan’s post, New Team Rep (also, do we need one?).

3. Docs Sprint

The Docs Sprint is meeting this Saturday, Feb 1 at 10am PST.

Join the sprint in Seattle, or on IRC at #wordpress-sfd.

4. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org

@jazzs3quence and contributors are making progress, but still need help with:

  1. Documentation contributions for tooltips and overviews
  2. Testing and bug/issue reporting.

5. Docs Project Landing Pages

Per last week’s report, the Docs Team are creating helpful landing pages for each docs-related project that provide an overview of the project and a clear path for contributors to get involved.

Your docs project can add a page to the Projects section where @DrewAPicture posted the landing page for Inline Docs, which is a great example.

@siobhan would like to have these pages complete by Feb 28th and would like a volunteer to oversee this project and make sure it gets done.

6. Administrative Chat

@siobhan would you like to use next week’s new chat time for the Administrative Chat you’d mentioned earlier? Or, do you prefer to schedule this for another day?

Full IRC Logs

#chat-recap

Chris Reynolds 7:14 pm on January 6, 2014
Tags: ,   

AH-O₂ Update — 6 January, 2013

Help Overview Update

  • @mdbitz shared some screenshots of what he’s working on earlier in the week. These screenshots are available in the Google Group. The code isn’t quite ready to be merged yet, so the initial release on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ will just be with the tooltips.
  • The current solution involves hacking coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. — @mdbitz is trying to get it so we can pull existing help tab content from WP_Screen into the new help overview containers in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
  • The plugin will display the current help content (if it exists) for the current page, but can be overridden and new content added by the plugin
  • @mdbitz is also working on getting the overviews to work responsively. @trishasalas and @ubernaut both said they’d be willing to help with this, if needed.
  • @jazzs3quence will hide the profile option for the help overviews temporarily for the initial release

Docs input

We (still) need input from docs folks if things are going to be changed in terms of how the content is presented vs. what was proposed in the original mockups. For reference, the main points that have been discussed are here and here.

  • @nlarnold1 will attend the thursday meeting and talk to the docs team to start the discussion
  • @jazzs3quence will try to be there as well.

Tooltips

  • @ubernaut brought up the issue that tooltips may not be usable on touch devices. Is there a solution/workaround? How are other people/projects handling this?
  • keyboard shortcuts for a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) wouldn’t work, either, on touch devices
  • No new tooltip hotspots (for lack of a better word) have been added. The plugins pages do not have anything filled in in the spreadsheet
  • @ubernaut will work on filling out those areas first and pinging the Google Group
  • once that’s done, @brainfork can work on adding in those tooltip areas
  • @jazzs3quence can also help fill in the gaps in the spreadsheet so it’s not bottlenecking development

Updating and testing the plugin

  • @jazzs3quence suggested adding support for the Github Updater plugin for access to bleeding edge updates. This was ultimately overruled — not really necessary if the maximum amount of lag between .org updates is one week and if ppl want the latest latest version, they can get it from the GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ repo.
  • .org plugin will be updated after the meeting, once a week
  • the first version of the plugin will be uploaded to WordPress.org today sometime

(Revised) Development Timeline

  • January 6 — AH-O2 to be added to wordpress.org/plugins
  • January 6 January 13 — initial help overview integration
  • January 13 — initial tooltips to be added for plugins pages
  • January 13 January 20 — initial tooltips to be added for all admin pages
  • January 20 — list of wants/needs from docs sub-team (this is on the outside, ideally we need this as soon as possible)
  • February 3 — first AH-O2 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release
  • April 15 — tentative release date for WordPress 3.9, AH-O2 is fully tested and ready for inclusion in core.

Full IRC log

#admin-help, #ah-o2

Eric Amundson 6:55 pm on December 12, 2013
Tags:   

Docs Meetup Roundup – Dec 12, 2013

1. Docs Sprint

There’s another Docs Sprint this Saturday, Dec 14th @ 10am Pacific and you can join us on IRC at #wordpress-sfd.

It’s our last scheduled sprint of the year.

2. Admin Screen Updates

WordPress 3.8 includes a makeover of the WordPress Admin, so we need to update the Administration Screen pages in the Codex.

@kimparsell will post a list of pages that need to be reviewed and updated on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//docs. Please help by grabbing one (or more) pages and updating.

3. DevHub

Still in active development. @rarst is working on the theme for the code reference and @krogsgard is working on the theme for the Handbooks.

4. Docs Issue Tracker

@Otto42 will be developing the issue tracker for Docs. Yay!

Also, Sarah Gooding posted about the Docs Issue Tracker on WPTavern.

5. Admin Help

The Admin Help project has been re-christened AH-O2.

If you’d like to help with this effort, show up on Mondays at 16:30 17:30 UTC in #wordpress-sfd, or get in touch with Chris Reynolds (@jazzs3quence).

6. Awareness of All Docs Projects

@DrewAPicture voiced a concern that the Docs Sprints have been focused almost solely on the Handbooks, while there are several other docs-related responsibilities beyond the Handbooks, like Admin Help, Codex, Inline Docs, etc.

We’ll work to make sure that all Docs projects get exposure and it’s clear how people can get involved and participate.

Since participation at the Sprints has been usually between four and ten people, often with a few new contributors, we’ll need representation from  other projects to attend meetups and/or provide instructions ahead of time, to help meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. participants get involved in the areas that suit them.

#chat-recap