WordPress Multilingual: WordCamp Antwerp 2016
•Descargar como PPTX, PDF•
0 recomendaciones•914 vistas
Presentation for WordCamp Antwerp 2016
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (18)
Destacado
Destacado (20)
Similar a WordPress Multilingual: WordCamp Antwerp 2016
Similar a WordPress Multilingual: WordCamp Antwerp 2016 (20)
Último
Último (20)
WordPress Multilingual: WordCamp Antwerp 2016
- 2. Andrés Cifuentes WPML Supporter | WPML Training
- 3. WordPress Multilingual Creating and maintaining Multilingual WordPress sites
- 4. Number of users (millions) 851 704 245 Users growth in Internet 2000-2015 505.0% 2,080.9% 1248.4% ¿Why? http://www.internetworldstats.com/stats7.htm
- 5. It is the opportunity to bring new users ¿Why?
- 6. Mobile first Content first User first Considerations: Content
- 7. Considerations: Content Original Content SEO taskHuman Translation
- 9. Multilingual vs Localised Considerations: Content
- 11. Languages UI and admin language Plugins and themes Language switcher URL structure SEO Considerations: Structure
- 13. Localize everything (slugs, CPTs, admin texts...) Considerations: Developers Follow the Codex
- 14. Considerations: Developers Plugin HandbookTheme Handbook
- 15. WordPress Multilingual Choose a solution
- 16. Multilingual Press qTranslate / qTranslate X WPML Polylang xili-language WordPress Multilingual Choose a solution
- 17. WordPress Multilingual Choose a solution Each language in its own WordPress installation
- 18. WordPress Multilingual Choose a solution All languages in a single post
- 19. WordPress Multilingual Choose a solution One language per post
- 20. WordPress Multilingual What is the right solution?
- 21. WordPress Multilingual Think the day after
- 22. Check if it is compatible. If you are not sure, consult the support. WordPress Multilingual Recommendations
Notas del editor
- Apesar del rápido crecimiento de sitios en inglés, es considerablemente remarcable el crecimiento de sitios en Chino y español. http://www.internetworldstats.com/stats7.htm
- One of the biggest challenges facing us as web designers/developers is making our websites fully multilingual. Gone are the days when a localised version of a site would be enough. The web has become a global marketplace where people now hunt for products not available in their domestic market or are looking for cheaper vendors abroad. Number of users whose native language is not English continues growing. It is more impact communicating with people in their own language. This shows a user focus approach. People prefer to buy in their native language. one third of the world population has internet access most people don’t use the Internet in English Internet use is growing fastest where English isn’t spoken companies trading globally improve their productivity by 34% the majority of the Internet users prefer to buy products on websites in their native tongues
- http://googlewebmastercentral.blogspot.com/2010/03/working-with-multilingual-websites.html Google is able to determine your site’s main language. Help Google using with Titles, headers, meta descriptions. Translate your content accuarate. Don’t use automatic translation. Tahsin Tahil Oliviu Stoian
- http://googlewebmastercentral.blogspot.com/2010/03/working-with-multilingual-websites.html Google is able to determine your site’s main language. Help Google using with Titles, headers, meta descriptions. Translate your content accuarate. Don’t use automatic translation. Arthur Shlain Geoffrey Joe Creative Stall
- Creative Stall John Caserta Chris Kerr
- There are three types of files used in the gettext translation framework. These files are used and/or generated by translation tools during the translation process, as follows:
- There are three types of files used in the gettext translation framework. These files are used and/or generated by translation tools during the translation process, as follows:
- Before getting started, you’ll need to consider the following. … Google has some detailed information on what it expects to see with multilingual sites. It wants the language to be obvious. That means not mixing languages on a single page. Google also suggests blocking automated translations from search engines, since they can be so unreliable that they confuse search engine crawlers.
- Here we show what is the right way to make a site multilingual and we emphasize the importance of all elements to be translated
- http://codex.wordpress.org/ http://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/ https://codex.wordpress.org/I18n_for_WordPress_Developers TMD
- https://codex.wordpress.org/I18n_for_WordPress_Developers https://developer.wordpress.org/themes/functionality/internationalization/ https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/ Grunt.js grunt-checktextdomain https://www.npmjs.com/package/grunt-checktextdomain https://www.crowdcast.io/e/wptranslationday/5 Yorlmar Campos
- Here we say what are the general steps to be done to turn a site into multilingual.
- https://codex.wordpress.org/Multilingual_WordPress
- https://codex.wordpress.org/Multilingual_WordPress Pros: Each language site is a regular WordPress install with regular posts (postmeta and external db is used for translation data) If you turn off the plugin the content continues to work fine, albeit without knowledge of its sources/translations. Cons: Separate sites create more management needs which might be undesirable.
- https://codex.wordpress.org/Multilingual_WordPress Pros: Side by side editing is easily implemented. Less things to break. There are no additional tables and much fewer things to modify in WordPress. Number of records in the database stays the same. Cons: Uninstall can be complicated, as the database needs to be cleaned from multilingual contents. SEO
- https://codex.wordpress.org/Multilingual_WordPress The database contents for posts remain unmodified (easy install and uninstall). Everything gets translated by default. If a post includes custom fields, they're attached to that post, so they are already associated with the language. Some plugins use - for theme's displayed terms - the language files (.mo) delivered with localizable themes. In WordPress, localization is based in GNU gettext technology. So when a single post is in french, plugin switch all the terms of the theme in the same language (here french). The files can be completed with the specific terms of the site (categories titles, widget, links...). No need to re-translate all, just add specific terms and translations in target languages. Other plugins that analyze contents (like related posts) keep working correctly. Cons: More complex architecture. The plugin needs to hook to many WordPress functions and filter them so that only contents that matches the language is returned. Additional tables are required by some plugins - normally, to hold the translation grouping. Newer plugins likely use a custom taxonomy or post meta fields instead. May cause excessive database grow and slow performance as a result. A WooCommerce-based site having a 100,000 products will have 500,000 records after translating to 5 languages. All product metas (could be tens of those per product, and also transients will be duplicated, too, so the database might become huge).
- Your product will continue growing It will be manage for different users. Your client will be happy not being asking for help. Credit: Artem Kovyazin, RU