As you may already know, the Board launched a process to generate ideas for the 2021 Budget. We have received so many great ideas that we’d like you to help us select from them.
The first remote accessibility sprint took place from 21st to 23rd of October 2020 and it was successful indeed. During these three productive days we focused on knowledge sharing, addressing open issues, and creating a practical checklist for developers. An accessible TYPO3 improves the experience of every user of TYPO3
Just before the Developer Days 2019, a small group was formed to look into setting up a formal body to ensure the wellbeing of everyone in the community—so-called ombudspersons. Now, we’re asking for your input.
Keeping up with changes is challenging at the best of times. There are some good tools to help keep track of changes, but they still require tedious manual labor. What if you had a tool that would not only keep you but also your codebase up to date? That’s where Rector comes in! There are 69 fixed rules so far, and you can help us add more.
After one meeting in person early this year, all our subsequent sprints were forced into remote calls due to the ongoing pandemic. Nevertheless, we’ve used the sprint dates we had already agreed upon to tackle our duties from home.
Meet BabesGotBytes, an organization based in South Africa that provides tech education to young girls in rural townships. TYPO3 Association is sponsoring its mission with hardware and financial aid.
TYPO3 has a reputation for being an exceptionally stable, robust, and reliable enterprise content management system. We achieve this by following a strict deprecation policy and backwards-compatibility promise. This article provides an insight into this topic for integrators and developers. I also explain when and why a TYPO3 upgrade is a no-brainer.
The TYPO3 Association met online on the 21–22 September for this year’s third virtual retreat. The entire board was present and worked together to review the year and look ahead to 2021.