25. Internationale ILIAS-Konferenz

Feature Wiki

Information about planned and released features

Tabs

(Project) Static Routing

This is a project page that bundles several feature wiki pages which belong to a larger development activity for the ILIAS component Routing.

1 Aim of Project

Routing refers to the mechanism by which URL addresses, e.g. called up in the browser, are linked to specific pages and components of a web application. This enables users to operate ILIAS in the first place and navigate between the different parts of it.

The aim of this project is to fundamentally revise the routing mechanism of ILIAS in order to eliminate the key weaknesses of the current implementation:

  • Decentralised request handling
  • Non-deterministic request flow
  • Manipulation of global state
  • Non-static URL addresses

This project will get rid of these weaknesses by introducing a new routing component, which will operate in parallel to the existing mechanism for several releases, while one ILIAS component after another is being migrated towards the new component – ultimately getting rid of the current implementation. This approach ensures backwards compatibility and enables gradual migration. The main goals of this new routing component are:

  • Centralisation of request handling
  • Deterministic request flow
  • Comprehensible and static URL addresses

2 Involved Authorities and Stakeholders

  • All authorities of ILIAS components are potentially involved.
  • The Technical-Board should have stakes in this.
  • All plugin maintainers should have stakes in this.
  • All users of ILIAS should have stakes in this.

3 Timeline

  • Requirement analysis for a new routing component
  • Evaluation and analysis of existing routing solutions
  • Proof of concept and implementation of prototype
  • Feature request for the integration of a new routing component
  • Implementation and introduction of the new routing component
  • Deprecation of the previous (legacy) routing mechanism
  • Migration of one or more ILIAS component(s)
  • Implementation of assistive measures for future migrations
  • Gradual migration of several ILIAS components
  • Transforming reusable GUI layers into proper services
  • ...
  • Gradual migration of several ILIAS components
  • ...
  • ...

4 Related Feature Requests and Status

Feature Request

Suggested by

Funding

Planned Release

Status

ILIAS Routing Component  (TBD)

-

-

ILIAS 12

In Planing

...

5 Further Results

  • None yet.

6 Additional Information

...

7 General Discussion

Please discuss specific questions of feature requests on the related feature wiki pages. This discussion section is only for a general discussion of the project and its realisation.

JourFixe, ILIAS [jourfixe], 24 NOV 2025 : We highly appreciate this suggestion to improve the URL handling and to get rid of the awkward ilControl based routing. But we see the need for a sound and sustainable funding for this project as it requires a lot of workload to implement the new routing component in all existing components of ILIAS this project (also in relation and combination to other suggested and running projects). Killing, Alexander [alex] urges that, before making a final decision on any major projects, we first make a rough estimate of the approximate costs involved and whether this work can be handled by the community in view of other projects. Roeser, Nico [nicoroeser]: Existing permalink should be supported also after a component has changed to the new component to avoid errors when using URLs in print documents or other documents that are using the permalink. 

Technical Board, 16 FEB 2026 : The Technical Board acknowledges the problem of missing static routes in ILIAS and appreciates the progress already made in recent releases (e.g., permanent links, short links, ilCtrl refactorings and speaking URLs). The TB believes that this project has significant technical relevance and would have deep architectural and strategic impact. Addressing the current routing mechanism’s limitations appears to be a logical continuation of the work carried out in recent years.

At the same time, we are sceptical regarding feasibility at this stage. The proposed migration timeline of “several releases” is too imprecise, no concrete feature requests are available yet, and a comprehensive cost estimation is missing. Since virtually all GUI components would be affected, the effort would require involvement from all component authorities as well as plugin maintainers, and would demand multi-release coordination with substantial human resources and likely significant funding. We also need to assess whether the community can handle this workload alongside other ongoing long-term initiatives (e.g., LUI removal, IRSS migration).

Furthermore, the project mentions transforming reusable GUI layers into proper services, but it remains unclear how this aligns with the current ilCtrl mechanism’s strengths and the existing approach of reusable controllers (GUI classes). The impact could be massive and needs architectural clarification.

In addition, Katholische Hochschule NRW is currently funding a proof of concept (PoC) aimed at gaining a clearer picture of the concrete technical steps involved, the architectural implications, and the level of funding that would realistically be required. Based on this, we suggest postponing a final decision on prioritization until the PoC results provide a more solid foundation for evaluating feasibility and scope.

Overall, we recognize this as an important long-term goal, but cannot provide a final priority recommendation as long as key aspects remain unclear: a realistic timeline, comprehensive cost estimation with secured funding, clarification of architectural questions, and an assessment of community capacity.

Statement Privacy Clinic, 28 NOV 2025:
From the perspective of the Privacy Clinic, we have carefully reviewed the project and found no issues or concerns that would warrant any objections. As such, we fully support the proposed project and have no reservations regarding its implementation.

Statement UX/UI/A11y-Experts, 8 DEC 2025

From our perspective, we support the routing project. Above all, the understandable, static URLs would enable predictable navigation, reliable back behavior, clear link targets, consistent page titles, and clean focus management—especially for keyboard and screen reader users. We are very pleased to accompany the gradual migration.

Last edited: 25. Feb 2026, 17:41, Kunkel, Matthias [mkunkel]