My presentation from WordCamp 2016 - : qtranslate X vs. polylang - a case study

1. qTranslate X vs. polylang
CASE STUDY: A BATTLE OF TWO PLUGINS
By Miriam Goldman
WordCamp Ottawa 2016

2. Who is Miriam?
 Front-end web developer at Fuel Industries
 Involved with WordPress for 5+ years
 Latin ballroom dancer
 3rd degree black belt in karate

4. qTranslate X
 Over 100,000+ installs
 Evolution of qtranslate
 Supported by a team of developers
 Hybrid of multiple qtranslate forks
https://en-ca.wordpress.org/plugins/qtranslate-x/

5. Pros
 Easy language configuration
 Simple buttons to flip between languages in WP Editor
 Tied to a single page/post, rather than separate entries
 Works well with ACF (advanced custom fields)
 Free, no freemium

6. Cons
 Need multiple plugins to support additional infrastructure
 Examples: qtranslate slug, qtranslate support for Gravity Forms/woocommerce
 Easy to get confused as to which language you are on

9. polylang
 100,000+ installs
 Offers addons
 Supported by sole developer
https://wordpress.org/plugins/polylang/

10. Pros
 More default languages installed
 You can set the order in the language switcher
 String translations can be set separately

11. Cons
 Certain settings need the Pro upgrade
 Separate pages are created, not as clean as a switch
 Additional configuration needed to support items such as ACF

15. So…which is better?
 Depends
 Easy of use: qtranslate X
 Ability to separate languages: polylang
 FULL DISCLOSURE: Other plugins also available (WPML, for example)
 Who wins? It’s a tie, really

16. Connect with Miri
 Twitter: @mirigoldman
 Web: http://www.miriamgoldman.com
 Email: sensei.Miriam@gmail.com
THANK YOU!