Whenever I develop a website from scratch, I take the mobile-first strategy. I believe that targeting small screens from the start teaches us how to deliver company messages more efficiently. With progressive enhancement, we reveal more content as more space is available to use on the screen.
From my experience, developing WordPress themes for the last six years, I have an observation regarding WordPress as a content management system. I noticed that there should be a balance between giving the flexibility to update the site but also restraining the future web administrators from changing whatever they wish (which eventually could make the site ineffective and difficult to use).
Looking at the Wood Republic website from the project’s perspective, there was a need for different page templates to get across the right message depending on the context. I was considering developing custom blocks for new content areas. However, it will involve me writing instructions and recommendations for the Wood Republic team about each element’s location. I was worried that making all blocks available to use at any point will impact the site’s consistency. I was hesitant assigning custom fields (via the Advanced Custom Fields Pro plugin) to page templates, but because the Product edit view in WooCommerce still looks like the old WordPress editor, I decided to take that path.
During the development phase, when Kamila and Joanna were updating products using the new layout and fields, they have already noticed the benefits of not using the previous page builder. They both admitted that the editing process for them as web administrators got quicker and more intuitive.
When I was looking into the translations plugins, WordCamp Bristol 2019 happened. During the event, I had a chat with one of the sponsors, Weglot, who offers fast API website translations. We tested the plugin on our staging environment, and we very pleased that all pieces of text were interpreted by default. Translated content can be modified manually if necessary.