<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/css" href="https://www.typo3.tum.de/_assets/32ebf5255105e66824f82cb2d7e14490/Stylesheets/rss.css" ?>

<feed xmlns="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<title>TYPO3 Team</title>
	<link rel="alternate" href="https://www.typo3.tum.de/t3/"/>
	<link rel="self" href="https://www.typo3.tum.de/en/t3/news-from-typo3-team/rss.xml"/>
	<id>https://www.typo3.tum.de/en/t3/news-from-typo3-team/</id>
	<updated>2026-07-22T13:01:10+02:00</updated>
	
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-33.atom</id>
				<title>TYPO3 v14 - That&#039;s new</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-06-11T12:01:29+02:00</published>
				<updated>2026-06-11T12:01:31+02:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/typo3-v14-das-ist-neu/"/>
				<summary>With TYPO3 v14, the next evolutionary stage of the popular enterprise CMS is on the horizon—bringing noticeable changes for backend users. While version 12 (LTS) primarily introduced stability and modernization, version 14 places a stronger emphasis on usability, efficiency, and an even more modern interface. We highlight the most important differences from the perspective of editors and backend users.
</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                            
                        
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/typo3-v14-das-ist-neu/">
                            TYPO3 v14 - That&#039;s new
                        </a>
                    </h2>
                    <h4>When will we migrate our sites to v14?</h4>
<p>We are planning the migration for <strong>summer 2026</strong>. Communication will be provided well in advance.</p>
<h4>What has improved for backend users?</h4>
<h5>1. Modernized backend design</h5>
<p>TYPO3 v14 consistently continues the UI overhaul:</p><ul><li>clearer typography and reduced visual complexity</li><li>redesigned icons and consistent symbolism</li><li>optimized color scheme for better readability</li></ul><p><strong>Result:</strong> The backend feels cleaner overall and closer to modern web applications.</p>
<h5>2. Improved usability and navigation</h5>
<p>A key focus of TYPO3 v14 is user guidance:</p><ul><li>simplified and more logical menu structure</li><li>faster access to important functions (e.g., editing pages, creating content)</li><li>improved backend search functionality</li></ul><p>Editors in particular benefit from fewer clicks and reduced onboarding effort.</p>
<h5>3. More efficient content editing</h5>
<p>There are also improvements in day-to-day content work:</p><ul><li>smoother inline editing (less context switching)</li><li>faster loading times for content modules</li><li>better visual feedback (e.g., for status changes)</li></ul><p>This results in a significantly faster workflow for page maintenance.</p>
<h5>4. Enhanced dashboard and widget functionality</h5>
<p>The dashboard has been further developed:</p><ul><li>more flexible widgets (e.g., statistics, to-dos)</li><li>better personalization depending on user roles</li><li>clearer presentation of relevant information</li></ul><p>Backend users can get a quicker overview of their tasks.</p>
<h5>5. Technical improvements with indirect benefits</h5>
<p>Even if not directly visible, technical changes impact the user experience:</p><ul><li>improved overall performance</li><li>modernized framework components</li><li>more stable backend interactions</li></ul><p>Less loading time and fewer errors mean more efficient work.</p>
<h5>6. More consistent behavior and less legacy</h5>
<p>TYPO3 v14 reduces legacy complexity:</p><ul><li>more consistent backend modules</li><li>fewer differing interaction patterns</li><li>standardized UI components</li></ul><p>This makes the system easier to understand, especially for new users.</p>
<h5>Conclusion: Evolution instead of revolution</h5>
<p>TYPO3 v14 does not introduce a completely new interface, but rather a consistent evolution:</p><ul><li><strong>v12:</strong> solid foundation, modern base</li><li><strong>v14:</strong> refinement, better UX, more efficient workflows</li></ul><p>For backend users, this primarily means: <strong>fewer clicks, clearer structures, and a more modern working experience.</strong></p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-39.atom</id>
				<title>TUMFIS is now officially available</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-06-11T12:00:53+02:00</published>
				<updated>2026-06-11T12:00:56+02:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/tumfis-is-now-officially-available/"/>
				<summary>TUMFIS integrations are now officially available for TYPO3.</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/tumfis-is-now-officially-available/">
                            TUMFIS is now officially available
                        </a>
                    </h2>
                    <p>We are pleased to announce that integrations with <a href="/en/t3/documentation/extensions/tumfis/" class="ti ti-none">TUMFIS</a> are now officially available for TYPO3 after the Open Beta Phase. The following views are currently supported:</p><ul><li><a href="/en/t3/documentation/extensions/tumfis/publications-by-organisation/" class="ti ti-none">t3://page?uid=370</a></li><li><a href="/en/t3/documentation/extensions/tumfis/publications-by-organisation-grouped-by-year-with-tabs/" class="ti ti-none">t3://page?uid=428</a></li><li><a href="/en/t3/documentation/extensions/tumfis/publications-by-multiple-organisations/" class="ti ti-none">t3://page?uid=417</a></li><li><a href="/en/t3/documentation/extensions/tumfis/publications-by-person/" class="ti ti-none">t3://page?uid=371</a></li><li><a href="/en/t3/documentation/extensions/tumfis/projects-by-organisation/" class="ti ti-none">t3://page?uid=372</a></li><li><a href="/en/t3/documentation/extensions/tumfis/projects-by-person/" class="ti ti-none">t3://page?uid=373</a></li></ul><p>Each of these can be configured individually.</p>
<p>Please note that TUMFIS must be <strong>requested and set up for your website</strong> before use.<br />Feel free to <a href="#" data-mailto-token="wksvdy4dizy-Jdew8no" data-mailto-vector="10" class="ti mail ti-link-mail" title="TUMFIS">contact us</a> for assistance, corrections or requests.</p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-37.atom</id>
				<title>TYPO3 v12: Code Freeze and Planned Upgrade to Version 14</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-06-10T08:49:55+02:00</published>
				<updated>2026-06-11T11:46:17+02:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/typo3-v12-code-freeze-und-geplantes-upgrade-auf-version-14/"/>
				<summary>A code freeze for TYPO3 v12 is in effect from July, 1st 2026. No further feature development will take place, while preparations for the upgrade to TYPO3 v14 in summer 2026 are underway.</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/typo3-v12-code-freeze-und-geplantes-upgrade-auf-version-14/">
                            TYPO3 v12: Code Freeze and Planned Upgrade to Version 14
                        </a>
                    </h2>
                    <p>A <strong>code freeze</strong> for the current TYPO3 version 12 is in effect from <strong>July, 1st 2026</strong>. This means that no further functional enhancements, new features, or custom developments will be implemented.</p>
<p>From this point forward, only <strong>hotfixes for critical issues</strong> will be applied to ensure the continued stability and secure operation of the system. This measure is intended to stabilize the existing environment while preparing for the next major upgrade.</p>
<p>At the same time, work has already begun on the <strong>upgrade to TYPO3 v14</strong>, which is planned for <strong>summer 2026</strong>. Further details and a concrete migration timeline will be communicated at a later stage.</p>
<p>All stakeholders are asked to take this into account when planning ongoing or upcoming projects, and to refrain from submitting new requirements for TYPO3 v12.</p>
<p>If you have any questions, please <a href="#" data-mailto-token="wksvdy4dizy-Jdew8no?celtomd=Myno7Pboojo" data-mailto-vector="10" class="mail ti ti-link-mail">contact us via email</a>.</p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-35.atom</id>
				<title>Transition of TUMonline to Public REST APIs</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-06-10T07:41:30+02:00</published>
				<updated>2026-06-11T11:46:19+02:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/umstellung-von-tumonline-auf-public-apis/"/>
				<summary>Starting July 1, 2026, TUMonline will transition all services to new Public REST APIs. The change follows Campusonline requirements and is designed as a 1:1 replacement of existing legacy webservices, with a final deadline of August 6, 2026.</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/umstellung-von-tumonline-auf-public-apis/">
                            Transition of TUMonline to Public REST APIs
                        </a>
                    </h2>
                    <p>As part of an ongoing technical modernization, TUMonline and all related services will be gradually transitioned to new Public REST APIs starting <strong>July 1, 2026</strong>. This initiative follows central requirements defined by Campusonline, which has set the binding <strong>final deadline for full migration to August 6, 2026</strong>.</p>
<p>Over the past months, Campusonline has worked closely with users to further develop the interface landscape. Based on prioritized requirements, the existing legacy web services have been systematically provided as <strong>Public REST APIs</strong>. With the current release, all planned Public REST APIs for the standard legacy web services are now fully available.</p>
<p>According to the specifications, the transition is designed as a <strong>1:1 replacement of the existing interfaces</strong>. The objective is to enable a smooth migration of current integrations without functional changes, while establishing a future-proof and standardized API structure.</p>
<p>All affected systems and integrations should be updated in a timely manner to ensure uninterrupted operation beyond the migration deadline.</p>
<p>If you have any questions or encounter issues during the transition, please do not hesitate to <a href="#" data-mailto-token="wksvdy4dizy-Jdew8no?celtomd=CDWyxvsxo" data-mailto-vector="10" class="mail ti ti-link-mail">contact us via email</a>.</p>
<p>&#160;</p>
<p>&#160;</p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-22.atom</id>
				<title>TUMFIS is now available (Open Beta)</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-04-14T09:30:20+02:00</published>
				<updated>2026-04-14T11:39:41+02:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/tumfis-ist-nun-verfuegbar/"/>
				<summary>TUMFIS integrations are now available for TYPO3 as Open Beta.</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/tumfis-ist-nun-verfuegbar/">
                            TUMFIS is now available (Open Beta)
                        </a>
                    </h2>
                    <p>We are pleased to announce that integrations with <a href="/en/t3/documentation/extensions/tumfis/" class="ti ti-none">TUMFIS</a> are now available for TYPO3 as Open Beta. The following views are currently supported:</p><ul><li><a href="https://www.typo3.tum.de/t3/anleitung/extensions/tumfis/publications-by-organisation/" target="_top" class="ti ti-none">Publications By Organisation</a></li><li><a href="https://www.typo3.tum.de/t3/anleitung/extensions/tumfis/publications-by-person/" target="_top" class="ti ti-none">Publications By Person</a></li><li><a href="https://www.typo3.tum.de/t3/anleitung/extensions/tumfis/projects-by-organisation/" target="_top" class="ti ti-none">Projects By Organisation</a></li><li><a href="https://www.typo3.tum.de/t3/anleitung/extensions/tumfis/projects-by-person/" target="_top" class="ti ti-none">Projects By Person</a></li></ul><p>Each of these can be configured individually.</p>
<p>Please note that TUMFIS must be <strong>requested and set up for your website</strong> before use.<br />Feel free to <a href="#" data-mailto-token="wksvdy4dizy-Jdew8no" data-mailto-vector="10" class="ti mail ti-link-mail" title="TUMFIS">contact us</a> for assistance, corrections or requests.</p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-24.atom</id>
				<title>Structured Data and JSON‑LD available</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-03-23T08:50:17+01:00</published>
				<updated>2026-03-26T12:12:39+01:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/structured-data-jetzt-verfuegbar-seo-und-ki-ready/"/>
				<summary>We introduced Structured Data and JSON‑LD to make web content more accessible for search engines, assistive technologies, and AI‑driven services. This enhances the discoverability of TUM’s digital content and improves the overall quality of information.</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/structured-data-jetzt-verfuegbar-seo-und-ki-ready/">
                            Structured Data and JSON‑LD available
                        </a>
                    </h2>
                    <p>To further strengthen its digital presence, the Technical University of Munich is progressively integrating <strong>Structured Data</strong> based on international standards such as schema.org into web pages managed by the TYPO3 team. These structured annotations help search engines and digital systems accurately interpret TUM content, including <strong>people, organisational units, events, and scientific publications</strong>.</p>
<p>By using <strong>JSON‑LD</strong>, the format recommended by Google, the structured data can be added cleanly and independently of the visible layout. This leads to <strong>improved visibility in search results</strong> and increases the likelihood of <i>rich results</i>, such as enhanced displays of researcher profiles or upcoming events. At the same time, modern AI‑driven search and assistance systems can better recognise and classify TUM’s digital information.</p>
<p>Within TUM’s system landscape, JSON‑LD offers additional advantages:</p><ul><li>Data from <strong>TUMonline and TUMFIS</strong>—including organisational structures, chairs, staff profiles, and publications—can be provided in a standardised and consistent manner.</li><li>Research information becomes easier to link with external platforms, thanks to adherence to internationally recognised metadata standards.</li><li>Editorial maintenance remains efficient since JSON‑LD is embedded separately from the visual layout and remains stable during design or template updates.</li></ul><p>Furthermore, Structured Data improves <strong>accessibility</strong> on TUM websites. Assistive technologies can interpret content more precisely when it is semantically structured, providing a better user experience for all visitors.</p>
<p>By enhancing the use of Structured Data and JSON‑LD, TUM is investing in a future‑proof digital foundation that combines technical robustness, editorial efficiency, and significantly improved online visibility.</p>
<p><strong>What do you have to do?</strong> Nothing, the feature is automatically available!</p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-20.atom</id>
				<title>New functions: Image cropping and Anchor links</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-02-25T13:52:15+01:00</published>
				<updated>2026-02-25T14:11:47+01:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/neue-funktionen-bildzuschnitt-und-anker/"/>
				<summary>We are expanding the options for (chief) editors: image cropping and improved anchor management!</summary>
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/neue-funktionen-bildzuschnitt-und-anker/">
                            New functions: Image cropping and Anchor links
                        </a>
                    </h2>
                    <p>Please find further details in our documentation:</p><ul><li><a href="/en/t3/documentation/content-elements/text-media/image-cropping/" class="ti ti-none">Image cropping documentation</a></li><li><a href="/en/t3/documentation/content-elements/anchors/" class="ti ti-none">Anchor management documentation</a></li></ul>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-16.atom</id>
				<title>New Security Concept - User Accounts</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2026-01-21T10:29:44+01:00</published>
				<updated>2026-01-21T11:17:05+01:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/neues-sicherheitskonzept-useraccounts/"/>
				
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/neues-sicherheitskonzept-useraccounts/">
                            New Security Concept - User Accounts
                        </a>
                    </h2>
                    <p>Many user accounts are either not used or haven’t been used for a long time, for example, because the person has left the university, changed departments, or no longer needs the account. The account cleanup process takes place in two steps: </p>
<p> <strong>Step 1 - Deactivation</strong></p>
<p> If a content editor/manager/editor-in-chief has not logged in for more than six months, the account will be automatically deactivated.&#160;</p>
<p>If you wish to reactivate your account, please first contact your editor-in-chief. If you encounter issues, feel free to reach out to us as well. </p>
<p><strong>Step 2 - Deletion</strong></p>
<p>If the account that was deactivated in Step 1 is not reactivated, it will be deleted after an additional six months without further notice.&#160;</p>
<p>Should you need an account again, simply register for the backend once more.</p>
				</div></content>
			</entry>
		
			<entry>
				<id>https://www.typo3.tum.de/t3/news-18.atom</id>
				<title>We are in OTRS!</title>
				<author>
					<name>TYPO3 Team</name>
				</author>
				<published>2025-08-01T10:49:00+02:00</published>
				<updated>2026-01-29T10:55:54+01:00</updated>
				<link rel="alternate" type="text/html" href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/wir-sind-in-otrs/"/>
				
				<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
                     
                    <h2>
                        <a href="https://www.typo3.tum.de/en/t3/anleitung/extensions/news/default-layout/article/wir-sind-in-otrs/">
                            We are in OTRS!
                        </a>
                    </h2>
                    <p>Since August 2025, your support requests have been processed as tickets, just like you are familiar with from the IT support. Please feel free to continue emailing us at <a href="#" data-mailto-token="wksvdy4dizy-Jdew8no" data-mailto-vector="10" class="mail ti ti-link-mail">typo3@tum.de</a>.</p>
				</div></content>
			</entry>
		
	
</feed>

