The TYPO3 Community Expansion Committee attended the conference again and set up a booth for the TYPO3 project, which was very well visited. As we were present at the conference for the third time, we had the opportunity to strengthen our relationships with representatives from various countries. We are confident that we can help, building up new communities in countries of the Global South.

Key Highlights of the Conference

• Economic Impact of Digitalization: A major focus was on how to measure the return on investment (ROI) of digital projects beyond cost savings, looking at contributions to national economic growth, job creation, and innovation.
• Public-Private Partnerships (PPPs): The conference emphasized the need for collaboration between governments and the private sector to build financially sustainable and widely adopted digital solutions.
• AI and Data Governance: Sessions explored the role of artificial intelligence, data, and digital infrastructure in the future of governance, including discussions on ethical use and building public trust.
• Real-World Showcases: The event featured practical case studies from countries like Estonia, Ukraine, Kenya, and Brazil. This included Ukraine's use of digital public services during wartime and a special exhibition celebrating 20 years of e-voting in Estonia.
• Cybersecurity and Resilience: There was a strong focus on cybersecurity, with Ukraine's Ministry of Defence showcasing innovations in autonomous defense systems and cyber defense.
• High-Level Participants: The event brought together over 600 participants from 80 countries, featuring speakers like the president of Estonia, Alar Karis, and the chief economist of the World Bank, Indermit Gill.

Back in February, I submitted the budget idea for Component-Based Frontend Development with Fluid, which was selected. I was very happy that you selected my idea for Q2, which allowed me to spend a lot of time on open source development over the last three months. Now the result is here: Fluid 4.3 has been released, Components have officially landed in Fluid.

What Are Components?

Fluid’s components are custom HTML-like tags based on Fluid templates that you can reuse throughout your project. The concept is similar to popular frontend frameworks like React and Vue or native Web Components, but they are server-rendered by PHP.

<my:teaserCard
    title="TYPO3"
    link="https://typo3.org"
    icon="typo3"
>
the Professional, Flexible Content Management System
</my:teaserCard>

Working With Components

Components use the existing ViewHelper syntax you are already familiar with. However, it is not necessary to write PHP code to create a component. Instead, Fluid internally routes the ViewHelper tag directly to a template file, where you define the component’s arguments — directly in Fluid.

<f:argument name="title" type="string" />

<f:argument name="link" type="string" />

<f:argument name="icon" type="string" optional="{true}" />

Why Components Matter

Components introduce a modern, component-based workflow that makes your frontend and integration work more modular, consistent and maintainable. This approach improves collaboration between different crafts, such as frontend and backend developers, by providing clear integration APIs.

Get Started With Components

You can start using components today in your Composer-based TYPO3 v13 projects by updating to the latest Fluid version. Non-Composer projects will have to wait a bit longer, because the latest Fluid release needs to be integrated into TYPO3 first.

I’ve also invested a lot of time in the documentation. A good place to start is the new chapter on Components in Fluid Explained.

Share Your Feedback

I’d love to hear your thoughts! Join the discussion in #typo3-fluid on Slack, or open an issue on GitHub if you find a bug.

I hope you will enjoy the new component capabilities of Fluid!

• TYPO3 13.4.15 LTS
• TYPO3 12.4.34 LTS

Both versions are maintenance releases only.

Further upgrade instructions

No further database upgrades are required for these maintenance releases.

Download

TYPO3 can be installed in various ways. For example the traditional way by using the source package at get.typo3.org or the modern way by setting up a project using composer, to name just two. Further details can be found in the according release notes:

• https://get.typo3.org/release-notes/13.4.15
• https://get.typo3.org/release-notes/12.4.34

Complexity and Context

Running TYPO3 in a container — especially in production — is a complex topic that requires some general background knowledge. Since we can’t cover every aspect of container infrastructure, we include links to external sources that TYPO3 developers may find helpful.

Community-Maintained Image Used

As of now, there is no official TYPO3 container image. For demonstration purposes, we’ve used the community-maintained image martinhelmich/typo3 to show how TYPO3 can run inside a container.

Local Setup Examples

The TYPO3 Documentation introduces running TYPO3 in a local container setup using a Docker network that includes a MariaDB container and the martinhelmich/typo3 container. This example helps readers get started with exposing ports, enabling container-to-container communication, and mounting volumes: Classic TYPO3 demo installation using Docker only.

Since Docker Compose is commonly used in local development, we also show how to automate those setup steps: Classic TYPO3 demo installation using Docker Compose.

Extending Images and Using Docker in Production

Next, readers learn how to extend an existing image to unlock more flexibility — and take a first step toward creating their own TYPO3 images: Extending the community-maintained Docker image for TYPO3.

We’ve also started a chapter on using Docker in production: Using Docker in production. However the whole section is still experimental and we need YOUR help to improve it.

Help Shape the Future of TYPO3 Container Images

We think the TYPO3 community needs to expand the available container options — from base images with correct system requirements, to more specialized images with preinstalled site packages and example data.

You can help. Share your knowledge on running TYPO3 in containers, test the new documentation, and give us feedback. Your experience can make a real difference.

Security and Maintenance Releases

Maintenance refresh for TYPO3 13.4.14 & 12.4.33 — Minor bug fixes, regular maintenance ensures long-term stability for the LTS branches. Read the notes

Celebrating All TYPO3 Contributors

June’s Coder’s Corner numbers are still being compiled, but commits, reviews, and translations keep pouring in. Watch typo3.com for the full recap and be ready to applaud every contributor who powers the next release.

Insights from the TYPO3 Association & TYPO3 GmbH

• Mr. TYPO3 President Leads Open Website Alliance — TYPO3 joins forces with peers to champion truly open, user-controlled web standards worldwide. See initiative
   
• Best Extension of 2025 — Call for Submissions — Show the community what you’ve built and claim bragging rights at T3CON25. Enter now
   
• Five Ideas Funded for Q3 2025 — Members chose projects ranging from permission presets to search engine abstraction; check all approved ideas Project lineup
   
• T3CON25 — call for papers — Share success stories, deep-dives, or lessons learned with the wider community. Submit talk
   
• v13 certifications now available — Prove your skills with new editor, developer, consultant and integrator exams tailored to the latest LTS. Book exam
   
• T3CON24 keynote recap — Catch up on last year’s visionary talk that framed TYPO3’s strategic direction and growth markets. Read the summary
   
• AI integrations in TYPO3 v14 — Artificial Intelligence is no longer just a trend — it's becoming a key component in many CMS environments. Kick-off TYPO3 AI

Upcoming TYPO3 events

• 17 July 2025 — SparksCon — Experience over 65 top speakers on 4 stages on the Augsburg gasworks grounds. Join SparksCon
   
• 19 July 2025 — TYPO3 On Deck: Rheinische Post Boat Party — Cruise the Rhine, trade lightning talks, and enjoy sunset networking with German TYPO3 fans. Reserve a spot
   
• 6 August 2025 — Team-Leader Dialogue Day — Core initiative heads sync roadmaps, tooling needs, and mentorship opportunities ahead of Dev Days. Apply
   
• 7 August 2025 — TYPO3 Developer Days — Four days of workshops, hallway hacking, and legendary socials — T3DD25 is your chance to collaborate, learn, and make your mark. Get details
   
• 9 September 2025 — Community Sprint Q3 — Developers, designers, and docs writers gather to polish v14 tasks and tackle newcomer issues. Sign up

TYPO3 community & ecosystem insights

• Using TYPO3 for Small Projects (Parts 2 & 3) — Real-world micro-site case studies prove TYPO3’s agility even on tight budgets and timelines. Read series
   
• Crafting Tomorrow’s Tech Talent — From SysAdmin to Platform Engineer at T3CON24. Explore talk
   
• BabesGotBytes: Women in Tech — The organization empowering the next generation of women in tech shaping TYPO3 and broader open source software ecosystems. Know more
   
• GitLab Project Template Update — New CI presets and DDEV configs streamline testing, security checks, and container builds for every repo. Template update
   
• TYPO3 Surfcamp 2025 Recap — From beachfront coding to nightly bonfires, discover how waves and code fueled fresh ideas. Event photos
   
• 30 Years of PHP — a TYPO3 Tribute — PHP’s evolution and TYPO3’s role in pushing enterprise CMS boundaries. Celebrate the legacy

Share Your TYPO3 Story and Get Recognized

Built a groundbreaking extension, organized a local meet-up, or mentored newcomers? Inspire others and earn the spotlight in a future issue. Submit a Story

Appreciation of the Month

To every developer reviewing pull requests, every designer refining UX mock-ups, and every volunteer translating documentation: you make TYPO3 welcoming, secure, and forward-thinking. Your talent and generosity turn roadmaps into releases and events into friendships. Thank you for keeping the heart of TYPO3 beating strong!

TYPO3 will not include AI directly in the Core. Instead, we focus on providing clean and well-defined interfaces to integrate your LLMs, external services, or AI-powered tools at relevant points in the system.

This decision is based on several important considerations:

Flexibility and Freedom of Choice: Every organization has different requirements for AI tools. While some want to rely on established services like OpenAI or Google AI, others prefer local or specialized solutions. Developers and agencies can choose the AI solution that fits their needs through standardized interfaces.

Sustainability: AI technologies are evolving rapidly. Instead of committing to a specific technology or vendor, we're creating an architecture that can keep pace with the evolution of the AI landscape.

Privacy and Compliance: Data protection and compliance are crucial, especially in Europe. Through external integration, users can control their data and decide which information is shared with which AI services.

Overall Voting Results

Summary of the Five Selected Ideas

Starting in Q3/2025, all funded ideas are seeking to align with the high-level objectives of the strategic goals for TYPO3 v14. The following five Ideas clearly demonstrate how they contribute to the long-term vision of TYPO3. Each summarized idea with a brief explanation of their strategic impact.

• Permission Presets - UI and Exportable Presets by Łukasz Uznański will make permission management in TYPO3 easier and more accessible for non-developers through an intuitive backend UI and exportable ACL presets (€10,000).
  Strategic fit: Simplifies permission handling, improves editor workflows, and supports maintainable setups across projects.
• EXT:seal - Search Engine Abstraction Layer by Tim Lochmüller will give integrators a unified way to connect TYPO3 with different search technologies like Solr or OpenSearch, making indexing and switching between engines simpler and more consistent (€7,500).
  Strategic fit: Reduces complexity, enhances interoperability, and boosts scalability of search solutions in TYPO3.
• Side-by-side Live Preview and Page Content Editing by Tomasz Woldański will streamline the editing experience in TYPO3 by combining content editing and preview into a single, more efficient interface (€10,000).
  Strategic fit: Simplifies the content workflow, improves usability for editors, and supports better multilingual content creation.
• Favorite Content Elements by Georg Ringer will speed up content creation by letting editors save, reuse, and copy frequently used content elements via a smarter wizard interface (€5,000).
  Strategic fit: Reduces complexity and helps editors create better content faster.
• TipTap RTE Extension by Florian Langer will introduce a modern, flexible alternative to CKEditor 5, aiming to reduce development overhead and offer a more intuitive editing experience for TYPO3 users (€7,500).
  Strategic fit: Enhances the overall user experience by making rich text editing more accessible, efficient, and sustainable.

The winners will now start to work on their projects. They will be supported by the Business Control Committee (BCC). The people responsible for each idea project will report about their progress at typo3.org. If they succeed, they will be paid their allotted budget.

From the BCC’s point of view, all ideas would have been worth funding. Having a look at the voting results, we do see favorites, but the results in the main field are very close and a few more votes could have changed the overall results.

The results of the previous budgets are already published at typo3.org. In the following weeks results of all selected budgets will be published.

Timeline for Budget Ideas 2025

Q3/2025

• 29 April 2025 — Announcement — Call for budget ideas Q3
• 21 May 2025 — Deadline for submission of budget ideas
• 1 June 2025 — Ideas will be published and voting process starts
• 17 June 2025 — Voting process ends
• 22 June 2025 — Budgets granted
• 1 July 2025 — Work on idea projects start
• 30 September 2025 — Work on idea projects end

Q4/2025

• 11 August 2025 — Announcement — Call for budget ideas Q4
• 21 August 2025 — Deadline for submission of budget ideas
• 28 August 2025 — Ideas will be published and voting process starts
• 16 September 2025 — Voting process ends
• 21 September 2025 — Budgets granted
• 1 October 2025 — Work on idea projects start
• 31 December 2025 — Work on idea projects end

Automated Setup

The setup is now completely automated. The required DDEV add-ons are installed automatically along with the Composer and npm packages. Once the repository is cloned, the following command will prepare everything for you:

ddev typo3-init

Nominate Your Favorite Extension

Is there a TYPO3 extension you couldn’t live without in 2025? One that saved you hours of work, brought new functionality to your site, or inspired you with its technical brilliance?

Let us know by submitting your nomination via this short form:

Submit Your Nomination

Deadline for submissions: 15 September 2025

Everything You Need to Know

• Nominations are open to everyone in the TYPO3 community, freelancers, agencies, and end customers
• The top 3 will be announced alongside all other shortlisted nominees on 1 October 2025
• The extension with the most submissions will be announced as the winner during the TYPO3 Award Gala on 27 November 2025. Get your tickets now!

Let’s shine a spotlight on the work and people that make our ecosystem better, one extension at a time.

We can’t wait to see your favorites!

• TYPO3 13.4.14 LTS
• TYPO3 12.4.33 LTS

Both versions are maintenance releases only.

Further upgrade instructions

No further database upgrades are required for these maintenance releases.

Download

TYPO3 can be installed in various ways. For example the traditional way by using the source package at get.typo3.org or the modern way by setting up a project using composer, to name just two. Further details can be found in the according release notes:

• https://get.typo3.org/release-notes/13.4.14
• https://get.typo3.org/release-notes/12.4.33

Security and Maintenance Releases

TYPO3 13.4.10 & 12.4.29
Early-May maintenance updates tidied edge-case bugs and refined composer-based deployments for long-term projects. Release notes

TYPO3 13.4.11 & 12.4.30
Both versions fix regressions introduced with TYPO3 v12.4.29 LTS and TYPO3 v13.4.10 LTS, related to open_basedir, Composer Mode and Path Resolving. Full details

TYPO3 13.4.12 & 12.4.31 (Security)
Critical fixes close MFA-bypass and file-upload vectors — upgrade quickly for maximum protection. Read advisory

TYPO3 13.4.13 & 12.4.32
All versions are security releases and contain important security fixes. Read the corresponding security advisories. Learn more

ELTS 9.5.51 / 10.4.50 / 11.5.44 & ELTS 9.5.52 / 10.4.51 / 11.5.45
Multiple TYPO3 ELTS versions were released. As always with our ELTS maintenance releases, the primary focus is to keep the instance stable and the backend running smoothly, regardless of current browsers changing their behaviour over time. Read more and read more

Multiple Vulnerabilities in Extensions
The TYPO3 Security Team is always working hard to not only address security issues in TYPO3 core, but also popular third-party TYPO3 extensions from TER, too. TYPO3 Security Bulletins

Insights From the TYPO3 Association and TYPO3 Company

• Trademark-Usage Guidelines — A must-read primer on domains, social handles, and ads ensures everyone protects the TYPO3 name responsibly. Read policy
   
• Digital Public Good Status — TYPO3 joins the global DPG registry, underscoring its commitment to open-source values and sustainable development goals. Press release
   
• Backing an EU Sovereign Tech Fund — The Association urges Brussels to invest strategically in open-source security and digital resilience. Letter of support
   
• One-Click TYPO3 Playground — A budget-idea report shows promising progress toward spin-up-and-learn demo instances for newcomers. See progress
   
• Vote on Q3/2025 Budget Ideas — Community members can now rank proposals that will receive funding next quarter — make your voice count. More info

Upcoming TYPO3 Events

• 5 June — WordCamp Europe
  Cross-CMS mingling, workshops, and open-source collaboration. TYPO3 ambassador will be on-site. Join the action
   
• 6 June — AltCtrlOrg
  Hear voices and ideas that might not typically fit into WordCamp schedules during this WordCamp Europe side event. Join the waiting list
   
• 13 June — Head in the Cloud
  Discover insights into the topics of Cloud & DevOps, Technology and Culture & Creativity and enjoy a day with Mittwald in Espelkamp, Germany. Register free
   
• 16 June — UN Open-Source Week
  A week-long gathering on open source, digital public infrastructure (DPI), and the development of innovative solutions to global challenges. More info
   
• 19 June — Neos Conference
  Sister CMS communities exchange ideas at a two-track conference for developers, technical leads, CTOs, and everyone willing to learn something new and wants to challenge the status quo! Attend hybrid
   
• 23 June — TYPO3 Community Sprint (Q2)
  Developers, editors, and docs writers converge to this code sprint for all TYPO3 community teams, initiatives, and those invited by them. Newcomers welcome. Sign up
   
• 26 June — TYPO3 Camp Hamburg
  Unconference sessions and Elbe river sunsets fuel northern Germany’s flagship camp. Get info
   
• 6 August — Team Leader Dialogue Day
  Team leads align roadmaps, tooling needs, and mentorship programs ahead of the Developer Days. Apply
   
• 7 August — TYPO3 Developer Days
  Four days of workshops, hallway hacking, and nightly socials — sign up now, tickets are going fast. Details

TYPO3 Community & Ecosystem Insights

• Remote Best-Practices Day — Automation tricks, CI patterns, and design tokens from April’s virtual sprint. Read summary
   
• From Local to Live — New docs outline seamless deployment steps, covering Git workflows, composer locks, and env-specific secrets. Enhance your rollout
   
• Enum Hydration in Extbase — Brotkrueml dives deep into leveraging PHP 8.2 backed enums inside domain models with minimal boilerplate. Technical guide
   
• Mastering Localization & Staging — b13 shares enterprise-scale strategies for content freezes, shadow workspaces, and progressive releases. Full article
   
• Why Accessibility Is No Longer an Option — But an Obligation — Accessibility is an opportunity to create inclusive, user-friendly, and future-proof digital experiences. Read article
   
• Digital Public Good Deep-Dive — Why DPG status elevates funding prospects and civic-tech adoption worldwide. Insight
   
• AI & Spatial Computing — How generative product previews and immersive storefronts will reshape TYPO3 ecommerce experiences. Future trends
   
• Blocking XSS in TYPO3 — Learn modern CSP headers, sanitizer usage, and safe-HTML best practices to secure front-end output. Security tips
   
• TYPO3 Content Blocks vs. Mask vs. DCE vs. Flux — Compares flexibility, learning curves, and long-term maintenance for popular page-builder approaches. Compare now

Share Your TYPO3 Story & Get Recognized!

Migrated a complex site, launched a humanitarian portal, or mentored newcomers? Tell us! Your journey could inspire thousands and feature in a future issue. Submit here

Appreciation Of The Month

Huge applause to every tester who chased regressions, every writer polishing docs, and every organizer scheduling late-night video calls across time zones. Your dedication turns security advisories into rapid fixes, ideas into funded projects, and events into lifelong memories. TYPO3 thrives because you show up, share knowledge, and welcome newcomers — thank you for powering our community journey!

As Feature Unit Roadmap Coordinator, I’ve worked closely with the Core Team, the Product Strategy Group, and the leads of our roadmap objectives to define a release schedule that’s ambitious, yet realistic — structured enough to provide orientation, but flexible enough to reflect the way we currently work.

Embracing Change: Evolving the Release Cycle

We’ve consciously chosen not to tie each sprint release to fixed feature sets. Why? Because TYPO3 is evolving — not just as a codebase, but as a collaborative platform. We want to create space for ideas to mature, for contributors to step in, and to shape the work as it unfolds. That means flexibility, not fixed expectations. 

We’ve also learned from the past that tying sprint releases tied to predefined features created high expectations — often leading to considerable pressure on those responsible, which is difficult to manage in an open source community.

TYPO3 v14 Sprint Releases

Here are the dates for the TYPO3 v14 releases:

• 14.0 – 25 November 2025 – Breaking Changes
• 14.1 – 20 January 2026 – Feature Integration
• 14.2 – 31 March 2026 – Feature Freeze
• 14.3 – 21 April 2026 – LTS Release

Balancing Ambition and Realism

The release schedule reflects both ambition and realism. We’ve seen firsthand that larger features often require structural changes — and with that, more time and flexibility to get things right. By placing the .0 release a bit later than usual, we give ourselves the space to handle those fundamental shifts early on, where they belong. Releasing too early would reduce our flexibility — and in past cycles, this has often meant postponing entire features by a full version.

Of course, a later .0 release gives extension developers slightly less time to adapt their code. That’s a valid concern, but we believe it’s in the best interest of the product overall, allowing cleaner and more future-proof changes to be introduced with enough attention, reducing the risk of multiple follow-up improvements and implementation adaptations. 

Rethinking Collaboration: The Way We Work Has Changed

TYPO3 is currently undergoing one of the most important internal evolutions in years. With the introduction of unit-based team structures, we’re moving away from isolated development tracks, toward integrated, cross-functional collaboration from day one.

Achieving each roadmap objective typically requires collaboration between multiple units. Each objective has a responsible person assigned, and as Unit Roadmap Coordinator for the Feature Unit it is my job to collaborate with them and connect their goals with the teams that will realize them. This includes defining concrete tasks and deliverables, helping with concept validation, and ensuring efforts are aligned and transparent.

The units enable disciplines like UX, development, documentation, and marketing to collaborate throughout the project lifecycle. This avoids situations where documentation or communication become last-minute topics, rushed at the very end of the process.

This change also allows for more flexible and task-specific contributions. Contributors can join specific initiatives without committing to long-term expectations, making it easier to align personal and business goals with TYPO3's broader roadmap. In some cases, it will even be possible to apply for dedicated funding to support work on roadmap objectives.

What's Coming in TYPO3 v14?

We're currently transforming the strategic roadmap goals into clearly defined features. While we won’t make promises we can’t keep, we’re already deep in planning, prototyping, and coordination across multiple teams. Several initiatives are already moving forward as part of the v14 cycle. We are already working on:

• Core migration towards Schema API and Record API
• Dashboard Settings API
• Unified Scheduler Task Registry
• Breadcrumb Component
• Fresh look and feel
• Content Blocks improvements

Other features and concepts are being explored in parallel, each with their own coordination across different teams and units. We’re actively evaluating concepts, preparing prototypes, and keeping room for feedback and iteration.

Get Involved — DevDays and Beyond

A great opportunity to see all of this in action will be at the TYPO3 Developer Days, this August. During the Contribution Night, contributors — new and experienced alike — will be able to join focused initiatives, meet project leads, and directly contribute to the TYPO3 v14 cycle.

Whether you're interested in a particular topic or just want to help fix some bugs, this will be the place to connect and get involved.

Here’s how you can help even beyond the event:

• Fix Core Issues — Every bug you squash helps free up capacity for larger roadmap topics.
• Submit feature requests — Especially if they align with the current roadmap objectives.
• Let us know your availability — Even partial availability helps us plan better. Reach out to me via email or Slack.

I’m excited about what’s ahead, not just because of what TYPO3 v14 will include, but because of how we’re building it: together, transparently, and with focus.

If you have questions, ideas, or want to get involved in any way, feel free to reach out to me directly. I’m happy to help connect you with the right people or opportunities.

See you on the road to v14.

Starting with Q3/2025, we are seeking contributions that align with the high-level objectives for TYPO3 v14.

As a part of the democratic processes of the TYPO3 Association, an email with a voting link has been sent to all members. The four community ideas with the most votes will be granted their share of this quarter’s idea budget. The member poll is open until 16 June 2025.

The final results will be published by the end of June, so the winners can start their work on 1 July 2025. To receive the money, they must complete their work on or before 30 September 2025.

The deployment process in TYPO3 projects can vary greatly depending on the setup. Composer-based installations, CI/CD pipelines, version control, and deployment using tools like Deployer or rsync all play a role. For those new to TYPO3 or deploying a project for the first time, this can raise a lot of questions. The Seamless Deployment project aims to provide clarity — offering clear explanations, structured workflows, and best practices directly within the official documentation.

Current Progress

Over the past few weeks, Lina has revised, restructured, and expanded a wide range of documentation content. The goal is to make the deployment section in the TYPO3 documentation more consistent, accessible, and easier to understand.

Here are some key updates:

• A new central landing page for all deployment-related topics
• Guides for popular tools like Deployer and rsync
• Installing TYPO3 on a server
• Configuring environments
• Installing TYPO3 with Composer
• Version control of TYPO3 projects using Git
• Creating a TYPO3 project from the official GitLab template
• CI/CD: Automatic deployment for TYPO3 projects
• Classic mode installation

Additionally, improvements have been made to get.typo3.org, the central starting point for TYPO3 installation and downloads:

• The official GitLab template is now referenced and linked
• A link to demo.typo3.org has been added in the Try it Out Online section
• Permalinks for each installation type have been added to simplify sharing and referencing
• Instructions for installing a Site package have been updated and clarified

The project is still ongoing. Additional content will be added and the structure will continue to improve in the coming weeks. Feedback from the community is highly encouraged and appreciated.

Test Week in June — Help Wanted!

A test week is planned for 9–15 June 2025, during which the revised documentation pages will be tested and evaluated. We’re looking for TYPO3 users — regardless of experience — who are interested in reviewing the content and providing feedback.

If you’d like to participate, please register your interest now:

Register to Test TYPO3 Deployment Methods  — Help Improve the Docs!

Alternatively, you can reach out to Lina Wolf or Sven Finner via TYPO3 Slack, join the conversation in the #typo3-documentation channel, or send an email to t3-doc(at)haake.digital.

Every bit of feedback helps us improve the documentation further.

Get Involved

The Documentation Team is always looking for more support, especially for future projects. With the help of the community, the team provides high-quality, comprehensive documentation for TYPO3. We warmly invite you to get involved! Reach out to the Documentation Team or join the discussion in the #typo3-documentation Slack channel.

• TYPO3 13.4.13 LTS
• TYPO3 12.4.32 LTS

Both versions are maintenance releases only.

These releases aim to address regressions in the previous v13.4.12 and v12.4.31 releases concerning step-up authentication and file mime-type handling (see https://forge.typo3.org/issues/106772 for details).

Further upgrade instructions

No further database upgrades are required for these maintenance releases.

Download

TYPO3 can be installed in various ways. For example the traditional way by using the source package at get.typo3.org or the modern way by setting up a project using composer, to name just two. Further details can be found in the according release notes:

• https://get.typo3.org/release-notes/13.4.13
• https://get.typo3.org/release-notes/12.4.32

The team currently provides the Tea example (tea) extension, which serves as an example on how to write an Extbase extension following best practices. The main focus is on automated tooling for higher quality. This involves testing, static code analysis, CI and more. The long goal is to attract more people to join the team and also focus on other best practice areas.

Collaboration in action

The remote day happened within the TYPO3 Slack channel of the team. We gathered for an initial kick-off huddle then jumped into the concrete open tasks. Some worked together, some worked by themselves.

We switched to using runTests.sh for prepare-release, PHP linting and code quality checks in GitHub. Also we cleaned up the GitHub actions and created a bug report issue template.

Join us next time

We invite everyone to join our remote days, happening on the first Monday of each month. Our next Remote Day will be on Monday, 2 June at 11:00 Europe/Berlin time. We will meet in our TYPO3 Slack channel #best-practice-team. Check out our Regular Remote Day page to find out all the details.

We can’t wait to have you on board!