{"id":1029,"date":"2024-09-08T02:25:50","date_gmt":"2024-09-08T02:25:50","guid":{"rendered":"https:\/\/unprinted.ch\/wordpress-doubt-and-faith\/"},"modified":"2024-09-08T02:29:48","modified_gmt":"2024-09-08T02:29:48","slug":"wordpress-doubt-and-faith","status":"publish","type":"post","link":"https:\/\/unprinted.ch\/en\/wordpress-doubt-and-faith\/","title":{"rendered":"WordPress: doubt and faith."},"content":{"rendered":"\n

Since the introduction of the Gutenberg editor, a rift has opened up in the WordPress community.\nWhat was intended to be a modern, flexible tool to simplify content creation has provoked contrasting reactions.\nOn the one hand, some see it as a major step forward, a means of competing with platforms such as Wix or Squarespace.\nOn the other, many developers and experienced users find the editor neither mature nor intuitive, despite almost 10 years of development. <\/p>\n\n

I’m one of those who suffer with the publisher.\nBut I still have faith. <\/p>\n\n

Two visions of the publisher<\/strong><\/h3>\n\n

On the one hand, Kevin The Kevin Geary<\/a> is working on a project called Etch<\/strong>, which aims to dispense with the Gutenberg editor altogether by offering an alternative.\nIt’s a sentiment I partly share.\nDespite almost 10 years of development, Gutenberg is not yet complete.\nThe user experience is confusing for developers, and for end-users, there’s still a long way to go to reach a level of quality comparable to the competition. <\/p>\n\n

On the other hand, Nick Diego Nick M Diego<\/a> embraces every new development with enthusiasm.\nHe proposes projects to extend existing blocks and takes a proactive approach to getting things done.\nBy showing what’s possible, he helps the community move forward.\nAlthough he works for Automattic and may seem biased, his approach is clear and pragmatic. <\/p>\n\n

These two visions are a good representation of the tensions surrounding Gutenberg: on the one hand, those who feel frustrated by a tool that still seems to be in development; on the other, those who see each update as an opportunity to advance the WordPress ecosystem.<\/p>\n\n

My journey with WordPress<\/strong><\/h3>\n\n

I’ve been using WordPress for 20 years and have followed its evolution closely.\nNew features have often been invaluable tools, enabling me to extend the CMS and adapt it to my customers’ needs.\nIt’s been a pleasure to work with, and in the end, it’s been a win-win situation. <\/p>\n\n

But with Gutenberg, it’s different.\nMy relationship with him is less clear, and the trust is no longer the same.\nI constantly have to ask myself: should I change the way I work?<\/strong> Will this investment really improve my profitability and my customers’ experience? <\/p>\n\n

<\/p>\n\n

Key areas for improvement<\/strong><\/h3>\n\n

For me, the debate should focus on the following points:<\/p>\n\n

    \n
  1. Unified user experience<\/strong><\/li>\n<\/ol>\n\n

    Currently, WordPress administration is split between two different interfaces.\nThis gives the impression of a product in perpetual work, almost experimental.\nA single, consistent interface would boost user confidence. <\/p>\n\n

      \n
    1. Optimizing CMS management<\/strong><\/li>\n<\/ol>\n\n

      Interaction with the database, creation of post types and metadata should be central functionalities, and not managed via extensions.\nIn addition, queries should be simplified and optimized. <\/p>\n\n

        \n
      1. Responsive Design<\/strong><\/li>\n<\/ol>\n\n

        A UI base that allows designs to be easily adapted to responsive is necessary.\nWhile complex designs will always require code, there should be a minimum framework for non-technical users. <\/p>\n\n

          \n
        1. Synchronizing compositions with theme files<\/strong><\/li>\n<\/ol>\n\n

          Currently, synchronized compositions can no longer be modified directly via theme files.\nAllowing developers to manage these compositions via an IDE would greatly improve the development experience. <\/p>\n\n

            \n
          1. Multilingualism<\/strong><\/li>\n<\/ol>\n\n

            Multilingualism is a source of endless frustration.\nSolutions like WPML are often too complex and full of bugs, while Weglot is expensive.\nA native solution in the WordPress core is long overdue, and it’s about time we implemented it. <\/p>\n\n

            \n\n

            Nevertheless, I’m adapting.\nI’m closely following the development of the site editor, documenting my processes and modifying my working methods.\nThere’s an element of faith in this approach.\nI believe that the community will eventually improve the tool in the right direction. <\/p>\n\n

            WordPress has always known how to evolve, and I trust the community to keep Gutenberg moving in the right direction.\nHowever, it’s essential that the editor becomes a more coherent, intuitive, high-performance tool to enable developers and users to fully embrace it.\nFor me, the improvements proposed here are crucial steps towards achieving this. <\/p>\n","protected":false},"excerpt":{"rendered":"

            Since the introduction of the Gutenberg editor, a rift has opened up in the WordPress community. What was intended to be a modern, flexible tool to simplify content creation has provoked contrasting reactions. On the one hand, some see it as a major step forward, a means of competing with platforms such as Wix or […]<\/p>\n","protected":false},"author":1,"featured_media":1032,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[1],"tags":[35,27,17],"class_list":["post-1029","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-non-classifiee","tag-gutenberg-en","tag-tailwind-en","tag-wordpress-en"],"acf":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/unprinted.ch\/wp-content\/uploads\/2024\/09\/WP_debat.jpg?fit=1024%2C1024&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/posts\/1029","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/comments?post=1029"}],"version-history":[{"count":1,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/posts\/1029\/revisions"}],"predecessor-version":[{"id":1030,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/posts\/1029\/revisions\/1030"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/media\/1032"}],"wp:attachment":[{"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/media?parent=1029"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/categories?post=1029"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unprinted.ch\/en\/wp-json\/wp\/v2\/tags?post=1029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}