Skip to main navigation Skip to main content Skip to page footer
Superheroes wanted: How easy it is to improve TYPO3

Superheroes wanted: How easy it is to improve TYPO3

Have the article read aloud.

Loading the Elevenlabs Text to Speech AudioNative Player...
| Estimated reading time : min.
This article was automatically translated using DeepL. Therefore, inaccuracies may occur.

The TYPO3 Documentation Team is urgently looking for support from the community. Everyone - from beginners to professionals - can make a valuable contribution and good documentation is crucial for the success of open source software.

The TYPO3 Documentation Team is currently looking for "superheroes" for their documentation. As someone who has been working with TYPO3 almost daily since 2006, I can only say: this is a damn important thing.

Why? Because poor documentation is one of the reasons why many people dismiss TYPO3 as "too complicated". The problem is often not the system, but the fact that information is difficult to find or outdated.

The team around Lina Wolf, Sarah McCarthy and Garvin Hicking are aware of this. They know: Good documentation makes the difference between frustration and success with new TYPO3 projects.

The beauty of it: you don't have to be a documentation pro. Even small contributions help. Correcting a typo, improving an unclear code example or rewriting a confusing explanation - all valuable.

It's easy to get started: you'll find the "Edit on GitHub" button on every documentation page. Click on it, make your change, done. The team checks everything before it goes live. You can't break anything.

What’s really pressing right now:

  • Instructions for creating extensions
  • Running TYPO3 with Docker
  • Classic vs. composer mode explained in an understandable way
  • Polishing up the ViewHelper reference

They are looking for experienced Fluid people, especially for ViewHelpers. If you regularly build Fluid templates, this would be your chance to help others and give something back at the same time.

Every month there are meetings in the Slack channel #typo3-documentation. Plus live sessions where you can join in directly.

You can find the complete guide at "How to Document TYPO3". The original article has all the details.

I think it's great how TYPO3 works as a community. Everyone can contribute, everyone is needed.

Have you ever contributed to open source documentation? Or does the idea of contributing to TYPO3 appeal to you?

Back

Comments under articles are disabled. If you have a question or addition, please send me an e-mail.

Hi, I'm Wolfgang.

I have been working with TYPO3 since 2006. Not in theory, but in real projects with real deadlines. I've probably had the problems you're having three times already.

At some point, I started putting my knowledge into video courses. Not because I like being in front of the camera, but because I kept hearing the same questions over and over again. There are now hundreds of videos. Every single one was the result of a specific question from a specific project.

What makes me different from a YouTube tutorial: I not only know the solution, but also the context. Why something works. When it doesn't work. And which mistakes you can avoid because I've already made them.

As a member of the TYPO3 Education Committee, I make sure that the certification exams are kept up to date. What is tested there flows directly into my courses.