University of Hohenheim

Relaunch of the University of Hohenheim’s website

Relaunch of the University of Hohenheim’s website using TYPO3, with a focus on user-centred UX, scalable templates and components, and system integrations such as HISinOne. The project is being delivered using an agile approach and in close collaboration with the Communications, IT and academic departments.

University of Hohenheim
CMSTYPO3
IntegrationHISinOne (Degree Programme and Research Portal)
AuthentifizierungEnterprise SSO (SAML)
VorgehenAgile sprints with a weekly Product Owner meeting
SchwerpunkteUX, component/template system, SEO migration

Die Ausgangslage

Womit die Hochschule zu uns kam.

The University of Hohenheim’s website needed to be modernised in terms of its structure, design and technical infrastructure. This was complicated by a complex stakeholder landscape and the requirement to present key content on study programmes, research and organisation in a more data-driven way in future. Content must function at varying levels of detail for prospective students, researchers, administration and communications, whilst remaining consistent throughout.

University of Hohenheim
01

Complex stakeholder landscape

From prospective students and researchers to the administration and communications teams, content must be presented at varying levels of detail whilst remaining consistent. This requires a robust information architecture and clearly defined page types.

02

Outdated technical infrastructure

The structure, design and technical architecture of the existing website were no longer up to date. There was no scalable foundation for editorial content and further development.

03

Data-driven content from specialist systems

Course and research data was stored in HISinOne and needed to be displayed reliably on the website without compromising editorial control.

04

University-compliant authentication

Secure areas require identity management in line with enterprise standards. At the same time, this must not slow down editorial workflows.

05

Ensuring visibility in the relaunch

A relaunch carries the risk of losing existing rankings and visibility. The URL structure and migration had to be planned in such a way as to ensure that the site remained discoverable.

Das Vorgehen

Wie wir es gelöst haben.

We combine strategic restructuring with technical integration and implement changes using an agile approach in sprint cycles, working closely with the communications, IT and business departments.

01

UX design and information architecture

In UX and IA workshops, we develop a robust information architecture and validate it iteratively with stakeholders. This results in a responsive design for desktop and mobile devices, tailored to the key use cases.

02

Component and template system

We are building a scalable component and template system to serve as the basis for consistent page types. The UI is being developed iteratively and provides a solid foundation for editorial teams and future development.

03

HISinOne integration via API middleware

We integrate degree programme and research data from HISinOne via API-based middleware and optimised import and synchronisation processes. The data is displayed in page types that can be edited, such as on the degree programme portal and the research portal.

04

SSO and SAML integration

For secure areas and university-compliant access, we implement an enterprise SSO based on SAML. The identity management system meets security requirements without hindering editorial workflows.

05

TYPO3 extensions and localisation

We develop custom extensions and editorial content elements in TYPO3. In addition, we prepare the site for localisation (L10N) and multilingual functionality.

06

SEO and migration strategy

A technical migration strategy ensures visibility and search engine rankings during the transition, including through the URL structure. The SEO consultancy provides support throughout the relaunch.

Das Ergebnis

Was sich messbar verändert hat.

The relaunch integrates design, content and integrations in such a way that the university can publish content more quickly and grow in the long term.

Weitere Referenzen

Noch mehr Beweise.

Erstgespräch — 30 Minuten, ohne Pitch-Deck.

Ein ähnliches Vorhaben?