The skills I would like to acquire in the next few years. Sometimes I write down here the answers I give in some questionnaires. This one is from today.
I have been using WordPress in a very professional and daily manner for almost four years now. So this is one of the areas in which I plan to acquire/enhance my skills and experience in the coming years.
Having used WordPress as I did, and having contributed to advancing this CMS, leading releases, etc., I am now very interested in ways in which WordPress can be extended, and used in very specific contexts.
With the revolution that was the arrival of Gutenberg, the scope of WordPress has greatly expanded. So I plan to expand my expertise in combining WordPress with other technologies; such as React or GraphQL, or using WordPress in a serverless context.
One of the ways I have found to achieve these goals is to work on projects that require the use of WordPress in the unusual context; and not only as a website or blog creation tool.
I challenge myself to make it more of a highly adaptable tool.
It’s been a while since I wanted to move my sites and those of my clients to a managed WordPress hosting provider (performance addict). Now it’s done. I’m moving to Siteground.
For a few months, I have evaluated the offers of the various well-known managed WordPress hosting providers. Among others Kinsta, Bluehost, WP Engine, GoDaddy, Siteground.
Honestly, I was just a few steps away from moving to Kinsta. The price/performance ratio is excellent, with an impeccable support.
But the human factor also played a decisive role in my choice. Basically, I met Francesca Marano, who is WordPresss Community Manager at Siteground.
We e-met during the 5.3 release of WordPresss, which she directed, and for which I coordinated the documentation. I really liked her working methods. Also, I was impressed by her involvement in the WordPress community, and in her work.
I trusted her, and therefore Siteground. So there you go. Now my sites are at Siteground.
Le WordPresss Translation Day est un évènement virtuel mondial qui regroupe les personnes s’intéressent à la traduction dans l’écosystème WordPress. C’est 24 heures conférence donnés par des contributeurs WordPress de toutes les régions du monde.
Ah chose intéressante, j’ai fait ma présentation pour le WPTD juste avant d’aller sur le panel auquel je participais au WordCamp Lagos. Le sujet de la présentation c’était les bonnes pratiques pour internationaliser les thèmes et extensions WordPress.
J’ai prévu il y a quelques jours de reprendre complètement mon site personnel segbedji.com; et d’en faire un nouveau. Avec un tout autre design, et une nouvelle présentation.
L’objectif était de mettre en avant mes activités de freelance; et d’inciter les personnes qui visiteront le site à me contacter pour mes services.
Mais je mets cette idée en pause pour l’instant. Je m’y repencherai bientôt. J’ai l’intention de plutôt faire faire le nouveau site par une agence WordPresss spécialisée. Je pense à fantassin.fr actuellement.
I wrote this while sending my interest to be a guest on wp_contribute podcast. As answer to the question asking about my contribution to WordPress story
I’ve started contributing to WordPress three years ago by translating WordPress Core, plugin and themes in French, my native language.
Later, I’ve been more involved in Core team, to which I mainly contribute now, alongside with Documentation team. I then, since one year, volunteerly dedicate 10-15 hours per week to contribute to these two teams.
2019 was my more important contribution year. I’ve led the minor release 5.2.2 in June, and then have been a focus lead and documentation coordinator for the major release 5.3.
I plan to dedicate more time to contribution in 2020 and make some important work in Documentation team.
I’ve been writing #DailyNotes for 90 days now. Before that, I had already written about ten articles on the blog. So the content is starting to be quite voluminous.
It often happens that when writing a note, I refer to another one I had written before. So I had to look for it, and find it.
WordPress’ native search system is very great. It’s accurate, efficient, and I’ve almost always used it as a search system on the sites I build. But in this case, it was getting a bit complicated.
So I had to find a tool or an integration that would allow me to search more or less asynchronously.
I already knew Algolia because I saw it used on several sites, and I did some research on it. Same for ElasticSearch.
But I finally opted for Algolia because of its ease of integration, the interface which is rather simple and intuitive. Also I had the possibility to customize a lot the interface of the search results. And moreover, I had autocompletion during searches.
This is exactly what I was looking for. So I used the plugin « WP Search with Algolia » by WebDevStudios that integrated Algolia to WordPress since the team had stopped supporting integration to the CMS.
That’s the story behind the integration of Algolia into my site’s search system.
So I’m obsessed with the performance of my site segbedji.com. Obsessed by its speed, its ranking in the main SERP, its security, etc…
This is a personal matter for me. Very personal. I present myself as a talented WordPress developer. It goes without saying that my site, built with this CMS should be a credible example of what I claim to offer!
I’m going to talk today (in issue 89 of my #DailyNotes ??) about the different things I’ve had to do, and continue to do on the site.
As I said before, my site has to be fast. Very fast. Excessively fast (well, within the limits of what is possible). So I had to opt for a WordPress lite theme that I could boost with a few tricks of my own.
The opportunity was too perfect with 2020, the new official default WordPress theme, coming with 5.3 (version for which I was part of the release team, coordinating the technical documentation).
2020 was designed by the excellent Anders Norén, and its development was coordinated by Ian Belanger. I myself made some fixes to the theme during the early stages of its development.
So I started with a child theme of 2020 whose source code is currently hosted on my GitHub account.
Pictures are usually one of the biggest resources on a website. So I’m careful to upload only images that have been optimized beforehand (size, weight). So I was more than happy when the automatic sizing feature for large images came with WordPress 5.3 (kudos to our dear Andrew for the work done on this).
Images are also converted to WebP format for further optimization. Also, I now only use it when strictly necessary.
Next to it, I have the excellent, must-have WP Rocket ? for site optimization. Basically, caching, preloading the cache, minimizing and compressing script and style files are provided.
I tested for a few weeks the image preloading feature, which I then left. This because WP Rocket adds a script on the site to manage it. One less script to load, which was going to deprive ?. Not me, that’s for sure. Also, Chrome natively supports preloading since a few weeks. So as soon as I have some time, I’ll contribute to the ticket opened by Morten on Core Trac to integrate it to WordPress.
Another aspect, the plugins. The popular belief is that the more active plugins you have on a WordPress site, the slower it is. That’s not exactly true. A site with 30 active plugins can be faster and more performant than one with 3.
I’ve limited the active plugins on the site to the bare minimum. The list can be found on my legal notice page.
I have also disabled comments on the site. So no more comment scripts to load (although this is not the main reason for this action).