Skip to content

TYPO3 for universities, chambers and public-sector clients.

Clear responsibilities. Accessible content. Long-term support.

We develop and support TYPO3 websites for universities, chambers, authorities and other public institutions. We take into account editorial responsibilities, accessibility requirements and the existing IT environment.

From long-standing projects, we know how to work together with departments, communications and IT. We align tasks, approvals and technical implementation with the requirements of your project.

Starting point

Many tasks on one shared website.

Public institutions inform different target groups and often organise content maintenance across several departments. Added to this are, for example, protected areas, several languages or data from central specialist systems.

For the website, this means: responsibilities must be mapped, content structured understandably and technical requirements taken into account. TYPO3 offers functions for this such as user rights, approval workflows and the management of several language versions.

Cultural events often also involve the collaboration of many participating institutions. We describe the special requirements of such websites on our page on culture and events.

Our stance

Beyond the project start.

A website develops further with the tasks of your institution. Content changes, new functions are added and the technical basis has to be maintained.

We document decisions and agree changes with the responsible people. This makes it clear how the system is built and what needs to be considered in further development.

What we pay attention to in working together.

Every institution brings its own requirements and processes. That is why we clarify these topics early.

We check the tender documents and clarify open questions via the intended communication channels. For our participation, we compile the required offers, concepts and available evidence in accordance with the requirements.

We take into account the requirements relevant to your institution and plan design, implementation and testing accordingly. In addition to the web pages, we also look at relevant documents and additional information offerings. We document test results and identified limitations as a basis for further work and the accessibility statement. You can find more about our approach under Digital accessibility.

A move to our infrastructure is not a prerequisite for working together. We check the technical requirements of your environment and coordinate access, responsibilities and publications with your IT or the commissioned hosting provider.

We connect TYPO3 with existing systems, for example with directory services for login or databases for job offers and events. Content from TYPO3 can also be made available for further applications.

We set up user rights and workspaces to suit the tasks of your departments and take into account the required approval workflows. Supplementary TYPO3 training helps your editorial team to use the existing functions.

We document the agreed technical foundations, responsibilities and processes. For a change of support provider, we prepare the handover of the project-relevant documents, the source code and the required access within the agreed scope.

Collaboration

How we shape working together.

We align the project procedure with your responsibilities and decision-making paths. We distinguish the offer phase from the subsequent implementation.

Requirements and offer

We check the task, the technical requirements and, where applicable, the tender documents. We clarify open points via the intended channels and prepare an offer for the requested scope of services.

Concept and coordination

After the order, we specify structure, editorial roles and interfaces with the responsible participants. We record decisions; we use workshops when they make sense for the project.

Implementation and testing

We implement the agreed services in coordinated stages and provide interim states for review. We take into account the transfer of existing content as well as accessibility and data protection checks in accordance with the requirements of the project.

Operation and further development

For the time after publication, we agree maintenance and further development as needed. We record scope, responsibilities and billing separately. More on this under Maintenance and support.

The result

A clear basis for further operation.

A clear technical structure, documented processes and suitable editorial rights make daily work and later changes easier. New requirements can be checked and scheduled in a targeted way on this basis.

We agree with you what can be retained and where additional development is necessary.

From practice

Projects for university, chamber and culture.

We have been accompanying these projects for several years with technical support and further development.

Frequently asked questions

Questions from public-sector clients.

Yes, if the task and requirements suit our services and capacities. We check the tender documents and take part via the intended procedures. This includes the required tender documents and, where applicable, presentation dates.

We take into account the relevant federal or state regulations and the technical requirements that are decisive in them. For implementation and testing, the relevant requirements of EN 301 549 and WCAG are particularly important. Depending on the requirements, documents as well as information in Easy Language or German Sign Language are also included.

We agree responsibilities and test procedures with you and document results and open points. This does not result in a blanket confirmation of full conformity; what matters is the actual fulfilment of the requirements.

In principle, yes. We already support a university website that is operated in a university data centre. For your project, we clarify the technical requirements, access routes and responsibilities in advance. We agree changes and publications with the responsible people there.

We jointly clarify who maintains which content and which approvals are required. We set up user rights and workspaces accordingly. If required, we add training on your system so that those involved are familiar with the intended processes.

That depends on the tender documents. These can include project descriptions, information on experience and qualifications, concepts, calculations as well as required declarations and evidence. Before taking part, we check which requirements we can meet and prove. We name reference contacts after prior agreement with the persons concerned.

We define contacts and responsibilities for your project. We document decisions and technical processes so that further participants can familiarise themselves with them. We manage required access securely and in accordance with the respective tasks. We agree cover and procedures during absences to suit the agreed support.

Are you planning the further development of your website?

Briefly describe your project. If a service description or tender documents already exist, feel free to tell us the planned steps and deadlines. We check whether and how we can support you.