The old TUBAF website was based on the Drupal content management system (CMS) version 6.x from 2014. This technical basis was outdated, so the Rectorate decided not to bring the website back online for security reasons after the cyberattack in January 2023. Instead, the cyberattack was used as an opportunity to implement the plans that had been in place for some time to revise the website. An external service provider was commissioned to support the TUBAF project team. The result was a completely revamped website, both technically and visually, with Drupal 10 as the underlying CMS.

At the start of the web relaunch project in April, the priority was to create content that was relevant for prospective and current students. In order to be able to put this content online quickly, some technical and infrastructural issues had to be postponed - in particular the implementation of the group module. This makes it possible to organise editors into groups and only grant them access rights to their own group content (e.g. content from a specific institute). Without this group module with the associated authorisation model and media directory, there is only a so-called "central area" in which each individual editor can edit all content on the website. It is therefore understandable that the editorial team here had to be kept as small as possible.

The editorial team of the central area created the most important content for the above-mentioned target groups as well as important basic information on the structural units (e.g. contacts, links to blogs). However, the complete website can only be set up by the structural units themselves. It can be assumed that the amount of content will increase dramatically with the rollout of the system.

No. Many important milestones have been achieved in recent months and TUBAF's visibility has been gradually restored following the cyberattack. Nevertheless, there are still numerous open tasks and potential for optimisation. There will therefore continue to be regular technical and visual updates.

The old TUBAF website will be retained until further notice to give editors the opportunity to move their content to the new website. In addition, the old website will temporarily function as an intranet, i.e. it should be used for pages that should only be accessible internally. We anticipate a period of at least one year until the old website can be switched off.

The revision of the intranet is a topic whose complexity is likely to significantly exceed that of the web relaunch - especially if added value in the sense of an employee portal with personalised information and access to relevant applications and functions is actually to be created. The project team is continuously collecting ideas for this project and also examining initial variants for implementation. However, the current priority is to revise the external web presence. A start date for the "Intranet" project has therefore not yet been set and still requires some conceptual preparatory work.

Accounts currently still have to be created manually by the administrators. The connection to Shibboleth is in progress so that it will soon be possible to log in with the central user data. The group admins will then assign corresponding editorial rights to the users.

A form will soon be made available that group administrators can use to request their "old" groups, i.e. independent areas on the new website. You will find the link on this page.

The processing of applications for the creation of groups is based on a defined prioritisation list, e.g. faculties will receive their own area first, then the institutes, then professorships and then other areas. There were around 300 groups in the old system. So please understand if it takes some time to set up your group.

As a rule, the request to set up a group is submitted by the person who was the group admin in the corresponding group in the old system. A corresponding list is available. However, as there can always be changes in responsibility (people leaving the service due to age, job changes, etc.), this list is not binding, meaning that applications can also be submitted by other people in the relevant structural unit.

Currently, it is not yet possible to create password-protected areas in the new Drupal system. The old website can be used as an alternative for the time being, as it is only accessible internally, and the content can be uploaded there and linked accordingly.

Yes, in the glossary you'll find the agreed translations.

To the glossary

Please read the current version of the editorial guidelines and the information on this page first. If possible, seek advice from a key user with further web knowledge in your environment. If this does not answer your questions, we offer web consultation hours several times a week from the start of the rollout. In exceptional cases, please contact the web team at webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de) (redirection to the ticket system).

Despite intensive testing, the new CMS is not yet free of bugs. We therefore welcome your support in discovering bugs/errors. Please report these to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de) with as meaningful a description as possible and a screenshot or link to an example page.

Note: If something does not work as you were used to in the old Drupal, it is not necessarily a bug. So please check whether it is actually a bug that makes working in the system considerably more difficult or impossible or whether it is just a change for the user. In the short project duration and also due to the big leap from Drupal 6 to Drupal 10, it is not possible to reproduce the old system that has grown over the years 1:1.

You must be an editor in an area. Then you can create events for it. These are then automatically displayed in the central event calendar.

Note: It is not yet possible to display events in multiple areas.

In future, the contact details of contact persons are to be maintained centrally so that, for example, the contact box is automatically updated on all pages on which it is integrated when the telephone number changes. Contact persons can currently only be created by admins and super editors. Please send requests to create contact persons to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de).

Please send an email to webteam [at] tu-freiberg [dot] de (webteam[at]tu-freiberg[dot]de) and specify which contact details should be changed. The contact boxes on the website will then update automatically when the change has been made in the central database.