Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

What is the Responsibility of Plugin Developers?

2.411 Aufrufe

Veröffentlicht am

At WordCamp Singapore and Tokyo 2016. As a WordPress plugin developer, I talked about my opinion on the responsibility of plugin developers.

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

What is the Responsibility of Plugin Developers?

  1. 1. What is the Responsibility of Plugin Developers? Takayuki Miyoshi
  2. 2. https://profiles.wordpress.org/takayukister/
  3. 3. I am Takayuki Miyoshi, WordPress plugin developer.
  4. 4. I have been involved in the WordPress community in a lot of roles.
  5. 5. Translation Contributor Support Team Support Contributor Core Contributor WordPress.tv Contributor WordCamp Speaker Community Team Translation Editor Plugin Developer
  6. 6. I'm from Fukuoka, Japan
  7. 7. I'm from Fukuoka, Japan Me, too!
  8. 8. The original Wapuu was created by a Fukuoka-based illustrator and introduced at WordCamp Fukuoka 2011.
  9. 9. https://wapuu.jp/
  10. 10. https://wapuu.jp/
  11. 11. Wapuutopia Fukuoka =
  12. 12. I have 10 years experience in plugin development. Contact Form 7 and Bogo are my most favorite plugins.
  13. 13. Contact Form 7 manages contact forms.
  14. 14. Bogo makes your sites multilingual.
  15. 15. https://wptavern.com/contact-form-7-passes-40-million-downloads
  16. 16. Last month Contact Form 7 passed 40,000,000 downloads. WP Tavern wrote an article about it.
  17. 17. What is the Responsibility of Plugin Developers?
  18. 18. WordPress allows plugins to do everything. Plugins can make WordPress better or worse.
  19. 19. WordPress gives us great opportunities. What should we do for WordPress?
  20. 20. What is the Responsibility of Plugin Developers?
  21. 21. The Responsibility of Plugin Developers Is to Keep WordPress Accessible for Everyone.
  22. 22. WordPress Core is Designed to Be Accessible for Everyone. Plugins Should Follow It.
  23. 23. Let's Look at Two Aspects. Accessibility Localization &
  24. 24. Is Your Plugin Accessible?
  25. 25. Can you read this? Ensure Enough Contrast. Low-contrast text is hard to read.
  26. 26. form action="http://example.com/donut" metho p> <input type="radio" name="flavor" id="choc <label for="choc">Chocolate</label><br/> <input type="radio" name="flavor" id="crea <label for="cream">Cream Filled</label>< <input type="radio" name="flavor" id="hone <label for="honey">Honey Glazed</label>< <input type="submit" value="Purchase Donut </p> </form> Label Correctly.
  27. 27. form action="htt p> <input type="radio" name="flavor" id="choc <label for="choc">Chocolate</label><br/> <input type="radio" name="flavor" id="crea <label for="cream">Cream Filled</label>< <input type="radio" name="flavor" id="hone <label for="honey">Honey Glazed</label>< <input type="submit" value="Purchase Donut </p> </form> If your form isn't correctly labeled, screen reader users have no idea what to input into the fields.
  28. 28. https://make.wordpress.org/accessibility/2016/03/21/wordpress-goes-wcag/
  29. 29. The WordPress Accessibility Team announced that all new or updated code released into WordPress core must conform with the WCAG 2.0 guidelines.
  30. 30. WordPress core code ensures a specific level of accessibility. Plugins should follow it.
  31. 31. https://make.wordpress.org/accessibility/handbook
  32. 32. WordPress Accessibility Handbook provides essential information for plugin developers.
  33. 33. Is Your Plugin Multilingual-Ready?
  34. 34. Translation
  35. 35. https://translate.wordpress.org/projects/wp-plugins/contact-form-7/stable/ja/default
  36. 36. translate.wordpress.org makes collaborative translation possible.
  37. 37. __( "You are not allowed to upload files of this type.", 'contact-form-7' ) Make Text Translatable with __() Function.
  38. 38. __( $text, $domain ) _e( $text, $domain ) _x( $text, $context, $domain ) _ex( $text, $context, $domain ) _n( $single, $plural, $number, $d _nx( $single, $plural, $number, $ You can also use variant functions.
  39. 39. Text Direction
  40. 40. https://ar.wordpress.org/
  41. 41. In some languages, text is written Right-to-Left.
  42. 42. Add New Post page in English
  43. 43. Add New Post page in Arabic
  44. 44. Add New Post page in Chinese
  45. 45. Add New Post page in Hebrew
  46. 46. Add New Post page in Japanese
  47. 47. Add New Post page in Persian
  48. 48. In some languages, text is written Right-to-Left (RTL) and pages may have a different layout.
  49. 49. Do your plugins work correctly in RTL languages? Many plugins add blocks into the admin screen.
  50. 50. If you set these properties in your plugin's stylesheet, you may need to change the 'left' to 'right' in RTL languages: • text-align: left • margin-left: • padding-left: • border-left: • left:
  51. 51. If you set these properties in your plugin's stylesheet, you may need to change the 'left' to 'right' in RTL languages: • text-align: right • margin-right: • padding-right: • border-right: • right:
  52. 52. WordPress function is_rtl() tells if the site language is RTL. if ( is_rtl() ) { wp_enqueue_style( 'style-rtl', '/css/style-rtl.css' ); } Make an additional stylesheet for RTL and load it when the site language is RTL.
  53. 53. We looked at two aspects today but of course these are not the only things we need to learn. Accessibility Localization &
  54. 54. These are not about cool programming techniques, but it doesn't mean it's not important for developers. ACTUALLY, IT’S REALLY IMPORTANT!
  55. 55. The Responsibility of Plugin Developers Is to Keep WordPress Accessible for Everyone. This is what I keep in mind when creating a plugin.

×