First of all, of course, I would like to go into the technical innovations or simply show the new state, because now we have a CMS on the website. By CMS I don't mean just any CMS but the so-called SuluCMS. The decision for Sulu comes from my connection to the SymfonyCMF, which has previously taken over the persistence of content. Sulu now gives us an admin UI, various page types and a workflow for content. Those who do not expect a full stack CMS without any programming effort, i.e. anyone else who also sets up symfony applications, will find the perfect solution in SuluCMS. We continue to use the Kubernetes cluster as infrastructure for the website, which we have been provided by SysEleven to host our apps and prototypes. Of course, there is much more technology here. So just have a look at the repository.

As you can easily see, we have now created new pages in addition to the original ones. Here, for example, we want to present our projects (profileProjects that are still being listed). I was also at various conferences over the past year to present the responsibility of the developers in the climate crisis and the organization itself. A separate press area has also been set up with immediate effect.

If someone would like to see their project or conference contribution listed on our website, just speak to me in the Mattermost chat or send an email to info@develppersforfuture.org. This would also be the perfect place to point out the separation of our ticket boards again, because that's exactly what the content board was created for.

Projects that are still being listed). I was also at various conferences over the past year to present the responsibility of the developers in the climate crisis and the organization itself. A separate press area has also been set up with immediate effect.

If someone would like to see their project or conference contribution listed on our website, just speak to me in the Mattermost chat or send an email to info@develppersforfuture.org. This would also be the perfect place to point out the separation of our ticket boards again, because that's exactly what the content board was created for.