Sitecore Content Hub · React · TypeScript Wrapping OOTB Search as a Swiper Carousel in Content Hub · 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 Render...
Posts
AI-Powered SEO Copilot — A Sitecore Marketplace App
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...
Building an Event-Driven Webhook Pipeline in SitecoreAI - An Architectural Deep Dive
SitecoreAI Webhooks Azure Functions Azure Service Bus Event-Driven Architecture Every publish event is a signal. Here's how to build the infrastructure that actually listens. Here's a scenario most Sitecore teams have lived through. A content editor publishes an article, then walks over to a developer and says "the page hasn't updated yet." The developer checks the CDN — cached. Purges it manually. Five minutes later, another editor. Same story. The root cause isn't the CDN. It's that nothing in the system is listening for the publish event and reacting to it in real time. Content goes from the CM to Experience Edge, and then silence. Downstream systems — the Next.js frontend, the Sitecore Search index, the Content Hub asset record — have no idea something changed. SitecoreAI (the platform formerly known as XM Cloud, now part of the broader Sitecore AI product family) ships wit...