WordPress is changing, fast, and I’m happy about it. But I have needs that aren’t necessarily those of the community! (spoiler alert multilangue)<\/p>\n\n\n\n
After that first experience with the community at WCasia, my view of WordPress changed.<\/p>\n\n
<\/p>\n\n
My questions run deep, and Noel Tock’s<\/a> opening words<\/a> still ring true. Will WP be able to transform itself sufficiently to become the platform of tomorrow?<\/p>\n\n As Matt<\/a> explained at WordCamp Asia<\/a>, the block editor is a long-term project. It will improve and enable the platform to grow.<\/p>\n\n For my use, and from my point of view. Major improvements are needed in these 3 areas<\/strong> in the short to medium term:<\/p>\n\n Probably the trickiest for me. Being Swiss, 80% of my projects are multilingual.<\/p>\n\n Being French-speaking, if I want to be read\/understood by a wider part of the community, my content must also be available in English.<\/p>\n\n A few days ago, I tried to translate a site using twentytwentyfour with WPML. The editor templates don’t follow; and like everything else with multilingualism, it’s ultra-chronophonous to test, open, return to the editor again and again and again. The WPML solution, which I believe is the most widespread, has always been a source of infinite frustration. Polylang improves the situation somewhat, but not very happily.<\/p>\n\n There’s always weglot and Google Translate, but one is expensive and the other lacks flexibility when it comes to writing content.<\/p>\n\nMultilingual<\/strong><\/h2>\n\n