More than just a search: How Chemnitz.de makes content accessible in a structured way
Anyone visiting a municipal website usually has a clear goal: to find a service, download a form or retrieve information. In practice, however, this path often leads via a search that delivers many hits - but offers little orientation. Pages, documents and news appear side by side, the information you are looking for is available, but cannot be found immediately.
This was also the initial situation at Chemnitz.de. Over the years, content has grown in different systems. With the migration from Imperia to TYPO3, not only was the CMS modernised, but the central question was also posed anew: How can content be organised so that users can find it quickly and reliably?
Rethinking findability - not just improving the search function
The key realisation: a classic search function is not enough. Large websites in particular need more than just a list of hits. Users expect orientation, filter options and clear structures. This is why Apache Solr was introduced as a solution that not only makes content searchable, but also accessible in a structured way.
What is Solr - and why was it used?
Apache Solr is a search technology that not only searches through large amounts of data, but also prepares it in a structured way. Content can be filtered according to properties, categorised and displayed in different ways. This was crucial for Chemnitz.de, as content comes from several sources. These are bundled in a common index and form the basis for searches and lists. The decision in favour of Solr was made primarily due to its scalability, flexible filter options and good integration into TYPO3.
Search and lists: two ways, one system
Users usually start by searching: they enter a term and receive hits. Unlike traditional search solutions, however, these are structured directly. Results can be filtered according to content types such as services, documents or press releases. This reduces complexity and facilitates orientation. At the same time, this principle also works without a search term. Many pages - such as events or press releases - start directly as filterable lists that can be narrowed down further. The crucial point: search and lists are based on the same logic and database. Whether users are actively searching or browsing content, they always use the same system and find what they are looking for more quickly.
Less complexity in the editorial department
This approach also has advantages for editors. Content does not have to be maintained multiple times or sorted manually. A clean structure is sufficient - the system takes care of the rest. This reduces the maintenance effort and improves findability at the same time. Content appears automatically in searches, lists and suitable contexts.
Conclusion: A good search is part of the overall architecture
The Chemnitz.de project shows: Good findability is not created by a single function, but by a common database. With TYPO3 and Apache Solr, content is bundled, structured and flexibly displayed. Users find content faster, editors work more efficiently - and the website remains clear even with increasing complexity. The most important realisation: good searches don't start in the search field, but in the structure of the content.
