Posts

Guardrails for Agentic Sitecore: What to Do Before You Let an Agent Near a CM Instance

Part 3 of the Agentic Sitecore series Previously on the blog: MCP‑Powered AI Development Workflow in Sitecore XM Cloud introduced why Model Context Protocol matters for XM Cloud. From Prompt to Production: Agentic Sitecore Workflows with MCP walked through two working setups — Marketer MCP and the open-source community server — that take a single prompt from "create this page" to a published route on Experience Edge. Both posts end at the same place: it works. This one starts from a different question, which is the one that actually comes up once a working demo turns into something a team uses every week — what has to be true before this is allowed to run against something you'd mind losing? The demo in the March post is safe by construction: one page, one component, one publish, a non-production tenant, and a person reading every response before the next prompt goes in. None of those conditions survive contact with real usage. Someone will eventually ...

Fixing Module Access in Sitecore Content Hub with a Sign-in Script

Sitecore Content Hub · C# · Sign-in Scripts Auto-Assign Modules to Users on Sign-in in Sitecore Content Hub Content Hub DAM  ·  Scripting  ·  User Management One of the most common and frustrating issues in a fresh Sitecore Content Hub project is users getting 404 errors after logging in — even though their permissions look correct. The culprit is almost always module access . This article covers why module access doesn't cascade from user groups, how to diagnose it, and how to fix it permanently using a C# Sign-in Script that auto-assigns all available modules to users on every login. Real scenario: We assigned the Content module to a user group CH.CMP.Everyone . Users in that group still got 404. Assigning the module directly to individual users fixed it. This led us to investigate and implement the sign-in script solution documented here. The Problem — Module Access vs Group Permissions In Content Hub, there are two distinct layers of acces...

Wrapping OOTB Search as a Swiper Carousel in Content Hub

Sitecore Content Hub · React · TypeScript ·  Content Hub DAM  ·  External Components  ·  Practical Implementation Sitecore Content Hub's OOTB Search Component renders asset cards with everything built in — Download, Quick View, permissions, lifecycle status. But its layout is a fixed grid. What if you need it as a horizontal carousel with a custom header? This article documents a pattern we implemented in production: an External React Component that hides the OOTB Search, waits for its cards to fully render, then moves them into a Swiper carousel — keeping all native functionality intact. Key insight: We never rebuild what the OOTB component already does. We let it do its job invisibly, then steal its output and re-present it in our own UI shell. Architecture CONTENT HUB PAGE YOUR EXTERNAL COMPONENT OOTB Search Component opacity:0 — invisible but active Renders cards · Permissions · Download · Quick View Filters ·...

AI-Powered SEO Copilot — A Sitecore Marketplace App

Image
Marketplace App AI-Powered SEO Copilot  - Inside the Sitecore Pages Editor How we embedded GPT-4-driven SEO intelligence directly into the content authoring workflow — without breaking decoupled architecture principles. By Team Sitecore Strikers — Santosh Kumar, Shrikant Sahu & Divya Singh SEO is usually the last thing on a content editor's mind — and the first thing a marketing lead complains about after a page goes live. Editors juggle deadlines, approvals, and brand voice; "is this meta description under 160 characters" is rarely top of mind. So we asked a simple question for this year's Sitecore Hackathon: what if SEO best practices showed up right where content is created, instead of after it's published? That question became the AI-Powered SEO Copilot — a Sitecore Marketplace app that lives inside the Pages Editor, analyzes content in real time, and uses Azure OpenAI (GPT-4) to generate optimized meta titles, desc...