Meta Team Update: September 12

A few things currently in progress, but no major news to report. Here’s where we’re at for various projects:

  • 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. A spec is almost ready to be published. Meanwhile, work continues. We’re bringing in @krogsgard to help with on the development side.
  • (devhub): Weekly meetings are starting next week. Some design work has been done for the handbooks, though more remains. We still need developers interested in contributing to the code reference to pop in and own some tickets. 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 Plugin Directory or can be cost-based plugin from a third-party developer handbook needs an editor to push it forward.
  • Documentation Issue Tracker: I posted a spec for an issue tracker yesterday and would love some feedback on it. Next up will be creating some basic designs for it. If you’re an interested designer, let us know.

Outside of that, there’s also work being done to integrate @merty’s GSoC profile improvements, which should be done soon.

There are still pending questions for the plugin, support, and 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). ( teams, as mentioned last week.