Docs Chat: July 17

The following is a summary of the topics discussed:

1. DevHub:

  • Examples and voting should be coming soon. @siobhan mentioned access to view/submit examples is or will soon be extended to all editors on the make P2s.
  • @drewapicture (me) brought up the need for syntax-highlighting on hook reference examples. @siobhan pointed out that highlighting already is in place for function references though, so maybe there’s a disconnect in implementing that across the board. I’ll follow up on the meta ticket for highlighting the submissions form.

2. Handbooks:

  • Nothing much to report here. @samuelsidler mentioned it had been a slow week. Migrating the handbooks is still in the works. No word from @blobaugh or @sewmyheadon for theme/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 handbooks.

3. Inline Docs

  • I had a nice self-meeting yesterday in #wordpress-sfd, the first in a while. An update post for that is forthcoming. Chat log can be found here.
  • The 4.0 audit ticket is still open, patches welcome. See #28885.
  • Still working on various long-term initiatives to improve developer docs in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. See #28298, #28459, #28558, and others on the docs-focus report

The chat logs are available here.

#chat-recap