AH-O₂ Update — 13 January 2014

Tooltips

  • New tooltips to the plugin stalled primarily because not everyone was familiar with the grunt workflow. Since this adds an additional learning curve just to get started with the project, we’re dropping grunt for now so the js files (and anything else) can be edited directly which should hopefully increase the speed at which we’re able to do stuff. Grunt may be added back in later to do final tasks (like minification) or if everyone ultimately gets up to speed on grunt and decides, collectively, to start using it again. @ninnypants is going to work on pulling out the grunt dependencies (which is mostly in which js files are being called) and will also work on writing a how to tutorial for people to get started wtih grunt.
  • @trishasalas wasn’t able to work on tooltip styling this week. @ubernaut is going to pick up working on applying some basic styles to the tooltips this week.
  • we’re going to try to add an AH-O2-specific css class to the .ui-tooltip element we’re creating. For now, though, we’re just going to use .ui-tooltip. Ultimately, if the jquery-ui style guide project that @helen started working on picks up some momentum and produces canonical css rules for jquery-ui components, we’ll just use that, but for now we’ll try to use something like .ui-tooltip.ah-o2 to make sure we aren’t clashing against anyone else’s .ui-tooltip styles. @ninnypants is going to work on adding in an AH-O2 class to our tooltips.

Help Overview

  • @mdbitz wasn’t in attendance today but did submit a pull request earlier in the week for his work on the help overviews. It was a branch off an older version of the source, but I was able to get it merged today and it will be included in the next update on WordPress.org.
  • the overviews are really rough in terms of styling, and I found some issues in how the screen options component was working (or not)
  • currently the overviews display existing help tab content. this is where we need help — writing new content to fill these containers. also:
  • Do we keep the tabs or turn those into tooltips or page-specific overviews? I’d like some feedback from folks who have worked on the current help system to help guide how we handle these moving forward. For now, I advised the team to add the tabs and we can always pull them out later.

Other stuff

  • I’ve started creating tickets in the GitHub repo for things that need to get done. Feel free to report any issues you find there: https://github.com/jazzsequence/WordPress-Admin-Help/issues
  • I also added some new tags to said tickets for priority to try to direct which issues are most important
  • We have a new banner for the WordPress.org repo thanks to @ubernaut. This will be added in the next update, also:

Ah02 2x

  • I should be able to get version 0.2 up tonight — I don’t think there’s anything else that I was waiting on that’s likely to be added before the next commit.
  • @ninnypants indicated that we should add define( 'SCRIPT_DEBUG', true ) to our wp-config.php files for adding new tooltips.

Next meeting will be next Monday 17:30UTC

#admin-help, #ah-o2