After long break, here is the next reading list. I picked several posts and blogs, from which I learned a lot of stuff. Hopefully there is the one or the other recommendation, you will also find helpful.

TYPO3

“This month in TYPO3”

The first pick is not a single post, but a monthly post with annotated links. Peter Kraume (@cybersmog) covers many TYPO3 related topics, which happened in the previous month. If you want also get mentioned in his summary, you need to tweet it with the hash tag “#ThisMonthInTypo3” or use this Google Form.

Links to the issues:

Thanks Peter for your on-going effort!

TYPO3 releases 9.x

Since the last reading list three TYPO3 sprint releases were published. The news give a short overview over the main changes in each release:

TYPO3 V.9.4.0, TYPO3 V. 9.3.0, TYPO3 V. 9.2.0

Furthermore, I started a series of posts under the label “TYPO3 Feature Spotlight”, where I will have a deeper look into the new features, which hit our CMS. This series will also continue after the release of 9 LTS:

Site Package Tutorial

There are several ways to save a TYPO3 configuration: Keep all in the database (NOOOOOO!!!!!!), put it in files in the fileadmin directory (NOOO!!!) or create a site package (YESSS!!!). Michael Schams create an detailed tutorial, about how to create such a site package and published it on docs.typo3.org.

News: https://typo3.org/article/typo3-site-package-tutorial/

Tutorial: https://docs.typo3.org/typo3cms/SitePackageTutorial/

TYPO3 scanner

Hmm … ok, that’s not a really a reading recommendation, but a tool, which is helpful, when you upgrade a TYPO3 installation to the next version. The tool is called “TYPO3 scanner” and was created by Michiel Roos. It scans extensions for deprecations and breaking changes for version 7, 8 and 9.

The difference to the “TYPO3 extension scanner” in the Upgrade module of TYPO3 is, that it works on the command line and works also for and with older TYPO3 versions.

Check it out at https://github.com/tuurlijk/typo3scan

Upcoming Events

What would the TYPo3 community be without the regular events, where we meet face to face to code and have fun. The “TYPO3 Inc.” published a list of the upcoming TYPO3 events for the fourth quarter of 2018 https://typo3.com/blog/mark-your-calendar-typo3-events-in-q4-2018/

Also there are some release parties scheduled for the next LTS release on October 2nd:

https://wiki.typo3.org/Release_Party/TYPO3_9

If your city is not already listed, you are welcome to organize one ;-). All you need is a valid TYPO3.org account, login on the wiki and add your city with all the data about location and time.

PHP Development

phpStorm Blog

phpStorm is probably the most used IDE in the TYPO3 community. With each and every release they publish new features and bugfixes. Their blog helps to keep track of the this stuff. Furthermore they publish blog posts, where they describe single features in detail.

URL: https://blog.jetbrains.com/phpstorm/

Building Secure PHP Software

Our all goal should be to write secure software. The staff of the Paragonie Initiative compiled five chapter of topics, everybody should be concerned of, while developing software using php. The topics cover php version, dependency management and typical attack vectors.

Full article: https://paragonie.com/blog/2017/12/2018-guide-building-secure-php-software

Frontend Development

The cost of Javascript

As you probably know, I also have an ongoing series of blogposts about TYPO3 and web performance. One aspect is the handling of javascript in the different browsers and devices. Addy Osmani is digging deeper into that topic in his post on Medium.

CSS Specificity

In the beginning of the week this question by Max Stoiber raised, some discussions about CSS specificity:

The correct answer is “Both are blue”. If your answer is wrong (like mine), here are two articles shedding some more light on the topic:

CSS SpeciFishity: http://www.standardista.com/css3/css-specificity

MDN web docs: https://developer.mozilla.org/en-US/docs/Learn/CSS/Introduction_to_CSS/Cascade_and_inheritance

Beyond

How to write a good git commit message

Most of us write git commit messages every day. But what is a good and helpful commit message? Robert Painsi published some rules what should be contained in a git commit message:

https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53

Leadership

Marcus Raitner found a 10 year old project by Google, that looked for principles of good leadership. It was updated in February this year. Read here what Google thinks about good leadership: https://fuehrung-erfahren.de/en/2018/09/10-insights-from-googles-search-for-good-leadership/

I hope, that one or more recommendations have been interesting for you. If so or if you know somebody, who could profit from it, please share this post via your favorite social network.

Credits

I want to thank my supporters via patreon.com, who make this blog post possible. If you appreciate my blog and want to support me, you can say “Thank You!”. Find out the possiblities here:

I found the blog post image on pixabay . It was published by Hans under the CC0 public domain license. It was modified by myself using pablo on buffer.