Implementation
From a technical point of view, the biggest challenge in this project was to fulfill the customer's wish for a TYPO3 headless solution. The separation between the backend on the one hand and the frontend on the other is much more visible than with conventional TYPO3 solutions.
In the backend, we opted for the standard and the recommended "headless" extension together with TYPO3. The main difference for the backend development was that JSON is passed to the frontend and TYPO3 rendering is omitted. This increases the organizational effort in the exchange and documentation of the transferred data and its naming. In addition, an Apache Solr search runs for the EKHN website, which is more comprehensive than the usual website standard with its many contents and links to topics.
In the interaction between backend and frontend, the advantage is that only frontend resources are scaled for higher availability. This is because several frontend servers can make requests to the backend server.
For the frontend, we have opted for a mixture of Next.js for processing the JSON content in combination with React for the layout. In the project, we also relied on Chakra UI.
This combination gave us the tools we needed to profitably implement the concepts previously agreed with EKHN in workshops during development.
In this project, we also repeatedly created interfaces and connections to external tools. In addition to the usual connections to Matomo or the Cleverreach newsletter tool, we also seamlessly connected lesser-known tools such as the ISIDOR mobile address directory for address book functions and Ev. Termine for event data to the website.
The most exciting challenge also lay in a news interface, which was solved with a Pocketbase database. This makes it possible to exchange news between the regional church website ekhn.de and the hundreds of parish and deanery websites, thereby increasing the reach of existing articles.
As part of the project, a number of things had to be considered with regard to accessibility, which plays an important role for the church throughout the entire project. For example, a contrast mode was developed to make the site more accessible for people with disabilities.
In the design process and layout development, precise attention was also paid to contrasts, the interplay of content elements and the size of the elements. To support this process even better, we used the open source tool "Pa11y", which provided us with additional information on the current level of accessibility during the development process.
More about the Accessibility can also be found in our blog.