Admin Help: 14 October 2013

We had a good meeting today and did a lot of fine-tuning of some of the ideas that have been tossed around.

One admin help path to rule them all

Last week, we had decided to try to let things roll with the two different ideas that were presented (a help page and a contextual help box with pop-ups/tooltips). This week, after some discussion, we’ve scrapped that idea in favor of rolling with the mockups that @veraxus presented.

A few notes:

  • We’d like to add links to the codex on the update screen and the dashboard welcome box
  • We haven’t yet decided whether tooltips or modals would be best for contextual help. @trishasalas will do some user testing on Verify to try to get some feedback. It’s worth noting that this may be guided by content — modals give us more room to have more detailed descriptions but require a user action. Tooltips are arguably more “in your face” but disappear if you move your cursor, so are best used if the message is fairly succinct. They are both good for different things.None of this help content is actually written, so it’s hard to know which would be the best option right now.
  • Help icons for metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes should be floated left of the title, since floating right interferes with the toggls
  • Help icons for options should be floated right with some sort of uniform alignment

Keeping up to date with other initiatives

Helen Hou Sandi is working on styling the default jquery-ui css to be more integrated into the general WordPress dashboard styles. That work is going into this:

Mel Choyce has been working on CEUX and MP6 and general admin updatedness. At least some of that stuff can be seen here:
with updates and stuff available here:

Additionally, if we’re talking about icons (and we sort of are), we should be looking at Mel’s Dashicons icon font which is bundled with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and used for all the icons:
…until further notice, that’s what we have to work with as far as an icon set (though presumably ideas for new icons or porting specific icons from Genericons could be suggested to Mel) since there are no plans to bundle Genericons with core at this time.

As we start moving forward, we should keep these things in mind as much as possible and try to keep what we’re doing in line with what they are doing, e.g. if Helen is working with jQuery UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. — which has tooltips — we can use those jquery tooltips instead of something else. Likewise with modals, if we decide to go that route.

Let the coding begin

I think we’re ready to start writing some code. The tentative plan is to start with a 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. repo and move that into the Contextual Help 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 that’s already on .org when we have something to show/use/test. I will post a link to the repo just as soon as either @veraxus or I set something up. 🙂

#3-9, #admin-help