---
type: concept
title: TYPO3 Webseiten Policy
tags: [governance, web-policy, security, university-administration, compliance]
related: [typo3-backend, universitatsrechenzentrum-urz]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_typo3_webseiten.md"]
---

# TYPO3 Webseiten Policy

The **TYPO3 Webseiten Policy** governs the creation, hosting, and maintenance of all internet presences associated with the Universität Greifswald. This policy was established by a rectorate decision on April 27, 2016.

## Core Mandates

- **Sovereign/Internal Hosting**: All websites under the responsibility of the university must be operated and hosted exclusively on university-owned IT systems. The use of external hosting providers is strictly prohibited.
- **Centralized Structure**: To ensure a unified institutional identity, the university mandates a unified web presence. All official university web pages—down to the level of individual chairs (Lehrstuhlebene)—must be part of the central web presence managed via [[typo3-backend]].

## Microsite Governance

Microsites are defined as separate project or specialized web presences that exist outside the central TYPO3 structure. Their operation is treated as an exception and is only permitted if a rigorous approval process is followed.

### Approval Criteria
A request for a microsite must satisfy the following:
- **Justification/Necessity**: There must be compelling reasons or proof that the content cannot be effectively integrated into the central TYPO3 presence.
- **CMS Requirement**: A Content Management System (CMS) must be used. Self-programmed code/content is strictly forbidden to mitigate security risks and vulnerabilities.
- **Approval Workflow**:
    - **Content Approval**: Initial approval must be granted by the Press Office (Pressestelle).
    - **Legal/Privacy Approval**: Final release must be granted by the Data Protection Office (Datenschutzbüro) after reviewing the imprint (Impressum), privacy policy, and other legal requirements.

### Maintenance Responsibility
The site operator is solely and explicitly responsible for the timely update of the CMS program code to ensure security; the [[universitatsrechenzentrum-urz]] does not provide maintenance for microsite code.

## Alternative Hosting

For approved microsites or smaller projects, the URZ provides an **Alternative Webserver** (alternative web server environment) that supports other CMS platforms, such as **WordPress**.