Community blogs

Ronald van der Plas · Jun 9, 2026

SUGNL is back — and the website is now open source

On 21 May 2026, we hosted the first SUGNL session in a long time. The turnout was good, the atmosphere was great, and it was fantastic to see the Sitecore community in the Netherlands come together again. That evening confirmed what we hoped for: there is still a lot of energy around SUGNL. With that in mind, we are moving forward and taking the next steps to bring the community back to life. As part of that, we have made the SUGNL website available in an open GitHub repository. This allows the community to help build and improve the website together. Whether you want to contribute code, improve content, fix small issues, or suggest new ideas, you are very welcome to participate. SUGNL is all about the community, so we would love the website to become a community effort as well. Take a look at the repository, join in, and help us make the SUGNL platform better step by step. #bettertogether

Jeroen Breuer · Jun 2, 2026

Umbraco OpenID Connect example with lightweight external members

The Umbraco OpenID Connect example has been updated to Umbraco 17.4.2 with support for lightweight external members . This stores members from an external provider as a minimal record instead of a full content entity.

Jan Bluemink · May 31, 2026

Sitecore Content and Layout Migration Part 1: Layout Manager Pro

Jeroen Breuer · May 27, 2026

How I let Cursor build an Azure Search provider for Umbraco Search

I wanted to build an Azure Search provider for Umbraco and let Cursor do the heavy lifting. This is what that looked like from the first prompt to the final commit.

Ronald van der Plas · May 21, 2026

SitecoreAI Goes Framework-Agnostic

Last year, at SUGCON Europe, Liz Nelson spoke with us about the future of Sitecore XM Cloud, now called SitecoreAI. One of the things to me that stood out was the ambition to make Sitecore development more framework-agnostic. At this moment we only had a proper Next.js SDK and a start into a .NET SDK. The future of a framework-agnostic SitecoreAI is now. Sitecore has released documentation for framework-agnostic Sitecore development. The key message is simple: you can build a Sitecore site without using a dedicated Sitecore SDK. Sitecore manages the content, your application retrieves it through APIs, and your front end renders it using the framework or language of your choice. Sitecore has supported headless development for a while, but in practice, the front-end story was still closely connected to a specific SDKs and implementation patterns. With this new direction, teams get more freedom to use the technology that best fits their architecture, skills, hosting model, and long-term strategy. This definitely opens the door for other frameworks like Astro and Go. To the outside world this change doesn't seem like a big deal, but front-end developers are already framework agnostic. Since a headless CMS, should be headless and therefor not tied to a specific framework. This move brings SitecoreAI closer to the expectations of modern front-end teams: API-first, flexible, and less dependent on one specific framework or SDK. The CMS should manage content, structure, authoring, and experience capabilities. The front end should be free to evolve. My conclusion In my opinion, this is a good development and something that can help SitecoreAI adoption beyond the existing Sitecore community. For teams outside that ecosystem, framework support can be a deciding factor. If SitecoreAI does not fit their technology stack, they will look at other platforms. By becoming more framework agnostic, SitecoreAI lowers that barrier and gives teams more freedom to choose the front-end technology that best fits their project. At the same time, I would not describe SitecoreAI as purely headless. Sitecore itself positions it as a hybrid headless CMS, and that makes sense to me. The frontend is decoupled, but SitecoreAI can still pass layout and component information through its APIs. So while it is API-first and now framework-agnostic, it remains experience-driven rather than headless by content-only. And that is exactly where Sitecore makes the difference. It does not just expose content through APIs; it also preserves the authoring experience, page composition, and marketer control that have always been important strengths of the platform. That said, as AI becomes more involved in building front ends, the exact framework may become less important. What will matter more are strong APIs, clear content models, and flexible platform boundaries to build on. That is why this is an important step: not just toward more framework choice, but toward a more open, AI-ready future for SitecoreAI.

Ronald van der Plas · Apr 20, 2026

Vercel Security Incident (April 2026)

The recent security incident at Vercel highlights a growing reality: modern composable architectures introduce new attack surfaces, especially when external platforms, AI tooling and CI/CD pipelines intersect. In this case, the breach originated from a compromised third-party AI tool connected via Google Workspace OAuth, which enabled unauthorised access to internal Vercel systems and affected a subset of customers. (The Verge) For teams running SitecoreAI (XM Cloud) with a head application hosted on Vercel, this is particularly relevant. Your frontend layer, often holding environment variables, API tokens, and integration logic, can become a high-value target. Immediate actions to take (Recommendations by Vercel) While we continue to take actions to protect Vercel systems and customers, here are best practices you should follow: Review the activity log for your account and environments for suspicious activity. You can review activity logs in the dashboard or via the CLI. Review and rotate environment variables. If any of your environment variables contain secrets (API keys, tokens, database credentials, signing keys) that were not marked as sensitive, those values should be treated as potentially exposed and rotated as a priority. Take advantage of the sensitive environment variables feature going forward, so that secret values are protected from being read in the future. Investigate recent deployments for unexpected or suspicious looking deployments. If in doubt, delete any deployments in question. Ensure that Deployment Protection is set to Standard at a minimum. Rotate your Deployment Protection tokens, if set. For help rotating your secrets or other technical support, contact us through vercel.com/help. Final thought This breach is not about Vercel alone; it’s about the increasing dependency on interconnected tooling in modern architectures. We should increasingly automate our deployments, this include automatic key rotations as well. This is a good test to see how much time it will take to rotate keys, either automatically or manually ;). For Sitecore teams, the takeaway is clear: treat your head application platform with the same security rigour as your CMS and backend systems, because in a composable world, security is only as strong as your weakest link.

Ronald van der Plas · Mar 20, 2026

SUGNL is back!

Exciting news for the Dutch Sitecore community! Together with Theo de Wolf and Bas Lijten, we're kicking off an effort to bring new life into the SUGNL (Sitecore User Group Netherlands) community. Our goal is simple: reconnect the community, share knowledge, and create a place where people can learn, get inspired, and meet others in the ecosystem again. We’re currently working on new events, fresh content, and making SUGNL an active and valuable community once more. Curious to see what’s coming? Check out the new website: https://sugnl.net or check our LinkedIn page. More to follow soon!

Jeroen Breuer · Mar 6, 2026

My Sitecore City Tour Amsterdam 2026 highlights

The Sitecore City Tour Amsterdam covered everything from SitecoreAI product updates and enterprise customer stories to a hands-on hackathon where we built and deployed our own Marketplace apps inside SitecoreAI.

Jan Bluemink · Jan 29, 2026

Tip: Get the SitecoreAI instance URL from a JWT token

Jeroen Breuer · Jan 28, 2026

Released: Umbraco Compose example project

C# client library and CLI for Umbraco Compose demonstrating cross-collection content composition with automatic reference expansion. Ready-made examples and schemas to help you explore the platform quickly.

Jeroen Breuer · Jan 21, 2026

Sitecore Technology MVP 2026!

I'm excited to share that I've earned the Sitecore Technology MVP award for the fourth time, now for the year 2026.

Jan Bluemink · Dec 14, 2025

Using the SitecoreAI Agent API Jobs Feature in Marketplace Apps

Jan Bluemink · Dec 12, 2025

Exploring the SitecoreAI Agent API Jobs Feature

Robert Hock · Dec 12, 2025

From XM Cloud to SitecoreAI CMS: Continuing the Learning Journey

The post From XM Cloud to SitecoreAI CMS: Continuing the Learning Journey appeared first on Kayee.

Jeroen Breuer · Dec 5, 2025

Migrating an enterprise Sitecore project to App Router

Migrated a real enterprise Sitecore project from Pages Router to App Router. Here are the patterns that made it work and what you need to know before attempting it yourself.

Jan Bluemink · Nov 24, 2025

Hide Wildcard in sitemap.xml with Sitecore MCP Server

Explore how to automate large-scale SitecoreAI updates with the MCP Server: task definitions, API calls, wildcard sitemap handling, LLM integration, limitations, reliability tips, and a full walkthrough video.

Robert Hock · Nov 24, 2025

My Sitecore Community Contributions in 2025

The post My Sitecore Community Contributions in 2025 appeared first on Kayee.

Jeroen Breuer · Nov 14, 2025

Sitecore MVP 2026 application

A list of my Sitecore activities for my Sitecore MVP 2026 application.

Jeroen Breuer · Nov 7, 2025

Testing the Sitecore Content SDK App Router beta

Testing the Sitecore Content SDK App Router beta with local containers. Async streaming with Suspense loads inventory data progressively without blocking the page.

Jan Bluemink · Nov 6, 2025

Sitecore Agent API for SitecoreAI a.k.a XM Cloud