devhub update 7th February

We had an extra devhub meeting on Thursday to go through the site and come up with a list of tasks. We focused specifically on the code reference for now, and have broken things down into a series of tickets.

Tasks

• the styling needs to be adjusted in the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. to make it consistent with 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/. Tickets: 313, 318, & 320 (@nlarnold1) 321 (@Rarst)
• minor design adjustments on the landing page 319 (@nlarnold1)
• correct page templates to be applied to single code reference pages 322 and search results page 328 (@rarst)
• Used by and Uses information to be retrieved from parser and added to archive templates 323 (@rarst)
• the following require styling: archive pages 325, single code reference pages 329, breadcrumbs 326, and pagination 327 (@nlarnold1)
• archive pages required so that users can browse by file 330 and by version number 331 (@rarst)

Devhub docs

Getting set up locally to develop for devhub is not the easiest task in the world. Currently we have some docs on the meta wiki. @Rarst is going to go through the wp-cliWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ process with @nlarnold1 and I’ll use the log to document it in the docs handbook.

The next meeting is Tuesday as usual at 15:00 UTC.

#devhub