Reading List #51


Those weeks around easter always feel a little too short, especially as I am always off on Wednesdays already, but this year I compensated a little bit by working a few hours here and there during those “off” days and overall the last two weeks felt pretty productive. We finally made the decision to switch all of our development over from Bitbucket to Github and I spent quite a few hours this week migrating a ton of old todos and ideas and adding or combining them as proper Issues in Github. Definitely felt like a much needed spring cleaning and the development of picu gained a lot of momentum through this.

Also this week, I published a little bit of a personal post about Focus and ADHD where I’ve written down a few thoughts and strategies for days when procrastination and a lack of focus strike really hard. I wasn’t sure how I will feel sharing this publicly, but the feedback I got so far shows me that this was the right decision.

Oh, and also, I turned 37 yesterday, which was nice. Thanks for all the good wishes ๐Ÿฅณ


๐Ÿ‘ฎโ€โ™€๏ธ Security Issues in Plugins

Joost started a new series in which he discusses things that are usually not covered by the “code tutorials”, but that you will encounter when building an open source plugin or theme (business). In this first post of the series, he talks about how to deal with plugin security issues if (or rather when) they come up. Worth checking out and I learned a thing or two. For example: I didn’t know about the “Upgrade Notice” that you can put in the readme.txt to display a notice inside the upgrade dashboard to tell people why they should upgrade to a new version.

Joost de Valk โ€“ How to deal with plugin security issues

๐Ÿ‘ท๐Ÿปโ€โ™€๏ธ Contributing to WordPress Core using Git

I just recently learned how easy it is to submit a small pull request to WordPress Code directly from within Github โ€“ which I always imagined to be more complicated. Actually, I never got around to contribute any code to WordPress core for the very reasons Jonathan mentions in this article, namely SVN being too big of a barrier. So my contributions so far mostly were translations, community stuff or a comment or two on a Github Issue. In this post, Jonathan explains how to setup the developer environment for WordPress and contribute a patch, all using Git.

Jonathan Bossenger โ€“ Submitting a patch to WordPress core, using Git

๐Ÿ“š Gutenberg Best Practices by 10up

10up just released their Gutenberg Best Practices with “Tutorials, resources, references and example code for all things Gutenberg.” to the public.

10up โ€“ Gutenberg Best Practices

Have a nice weekend!

Made with โค๏ธ in Switzerland