Best Practices for Handbooks

The following handbooks will need best practices drawn up:

  • Theme Developer – 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./UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it., 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). (https://en.wikipedia.org/wiki/Accessibility), General Best Practices
  • 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer – UI/UX, Accessibility, General Best Practices
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. – UI/UX, Accessibility, General Best Practices
  • Mobile – UI/UX, Accessibility, General Best Practices
  • Docs – Accessibility

(maybe we want a best practices doc for forum mods @ipstenu?)

Ideally, someone would take responsibility for UI/UX and would get together a group of people to draw up best practices that can be included within the handbooks. Based on people who have expressed interest in the past, here’s what I’m thinking:

  • Plugin Development Best Practices – @dougal
  • Theme development best practices – no volunteers yet
  • Theme/Plugin UX & UI- @justlikeair and/or @melchoyce
  • Accessibility for all of the handbooks – @esmi & the accessibility group
  • Core UI/UX – no one yet but maybe @helen can suggest someone?
  • Core – no one yet but maybe @nacin can suggest someone?

If I’ve mentioned you there and you’re still interested, please let me know in the comments. If you’re not mentioned but you are interested also let me know.

If you take responsibility for this, you’ll be expected to work with a group of appropriate people that you select to come up with best practices. Having a few Google Hangouts and drawing up a Google doc might be a good way to go about it. You’ll be expected to complete the best practices docs by:

  • Core, Mobile, Docs – April 26th
  • Theme Dev & Plugin Dev – July 19th

Okay, let me know!

#handbooks