Siobhan 2:10 pm on September 11, 2014
Tags:   

Devhub Update 11th September 2014

Thanks to everyone who attended the devhub chat! Here’s what we discussed:

Parser

I’ve been throughout the issues on 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 be the repository owner. https://github.com/ and marked any that are devhub related. There aren’t that many. If I’ve missed any let me know.

Code reference

  • @coffee2code ran the parser for WP 4.0 (thanks!)
  • the workflow has been implemented for editing parsed content in the code reference. If anyone wants to help test let us know.
  • parsed content has been moved to metadata so the main post editing area can be used for curated content
  • lots of the code reference archive pages need some sort of filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to allow users to only pull up the information they need. Opened ticket 601
  • @siobhan to write user contributed notes content
  • @coffee2code is working on implementing voting

The Great MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.
We’re approaching the point at which we can migrate content from the Codex to the code reference. Some considerations:

  • all code reference pages in the Codex will need to be redirected to their equivalent page in the code reference.
  • we’ll need to develop a style guide for formatting explanations. I’ve opened a ticket for discussion of it 602
  • we’ll need to develop a workflow for moving content over from the Codex

Handbooks

No outstanding technical issues. @samuelsidler is working on migrating the content.

IRC Logs

#devhub