Maintainable Frontends for Symfony & Why every CMS needs MCP
Details
Hello fellow Symfonians,
we are thrilled to announce the next user group meeting of the year, featuring two insightful talks that you won't want to miss!
This time we are hosted by c-base (Rungestrasse 20
10179 Berlin).
Come by and enjoy an evening of learning, networking, and socializing with fellow Symfony and PHP developers.
Agenda:
18:30: Doors open
19:00: Welcome and Introduction
19:20: Talk 1: "Maintainable Frontends for Symfony" by Daniela Berger
19:50: Break & Snack
20:00: Talk 2: "Why every CMS needs MCP" by Roland Golla
20:40: Socializing
Talk Details:
Talk 1: "Maintainable Frontends for Symfony" by Daniela Berger
In many web projects we find more backend devs than frontend devs, sometimes significantly so.
This often leads to devs with little frontend experience being asked to do frontend development anyway, and they often end up shaping their frontends in ways that will make their lives unnecessarily hard.
One common result are frontends that are functionally unmaintainable because each change - whether it is a new feature or a bugfix - requires implementing an exception to existing code, thus making the code increasingly and unnecessarily complex.
This is especially upsetting because with a bit of experience it is possible to implement light-weight frontend components with equally elegant CSS and JavaScript that are easy to extend and to adapt to new requirements without digging oneself into a deeper hole with each PR.
And since Symfony is making frontend development steadily more accessible to backend devs with Symfony US / Stimulus, this is a good time to take a closer look at *how* to structure these frontends.
This talk aims to a) introduce core frontend concepts that backend devs might not be aware of, b) show best frontend practices both on the code level and on the architecture level, c) show a few common mistakes that can be found in inexpertly implemented frontends, and c) introduce tools that will make consistent frontend development easier.
Talk 2: "Why every CMS needs MCP" by Roland Golla
Your content team already works in ChatGPT, Claude, and Gemini. Yet the content still lands in the CMS backend manually, clumsily, slowly. MCP changes that. One sentence in chat becomes a published article. No copy pasting, no formatting, no clicking.
And the content ranks. On Google, on ChatGPT, on Perplexity, on whatever comes next. Good content written by AI directly into the CMS goes live faster and gets found.
I show you the MCP plugin for Sulu CMS: open source, built on Symfony, ready to deploy. But this is not about implementation. It is about the three questions every content team must ask: Why does every website need MCP? What does good AI content look like? And why is conversational content management better than anything you click together in a backend?
MCP makes content creation as easy as chat. If you can write, you can publish. No CMS training, no workflow, no waiting.
Live on stage: a complete workflow from idea in chat to published article in Sulu CMS. Everything open source on GitHub.
Don't miss these insightful talks, engaging discussions, and networking opportunities. We can't wait to see you at the April Symfony User Group!"
If you have any questions or accessibility requirements, please reach out to us. Also, if your company wants to be the next host for the User Group, just let us know!

