diff --git a/.claude/commands/new-post.md b/.claude/commands/new-post.md
new file mode 100644
index 0000000..b4f4382
--- /dev/null
+++ b/.claude/commands/new-post.md
@@ -0,0 +1,33 @@
+Create a new blog post MDX file for this Next.js + Contentlayer2 blog.
+
+The user will provide a title (or ask them for one if not given). Then:
+
+1. Convert the title to a kebab-case filename: `data/blog/kebab-case-title.mdx`
+2. Use today's date in `YYYY-MM-DD` format
+3. Ask the user for a one-paragraph summary if they haven't provided one
+4. Create the file with this exact frontmatter structure:
+
+```mdx
+---
+title: 'Title Here'
+date: 'YYYY-MM-DD'
+tags: []
+draft: true
+summary: ''
+layout: DaveLayout
+images: []
+authors: ['default']
+---
+
+Write your introduction here.
+```
+
+Set `draft: true` so it doesn't publish until the user is ready.
+Leave `tags: []` empty — the user will add tags as they write.
+
+After creating the file, tell the user:
+
+- The file path created
+- To run `yarn dev` to preview it at `http://localhost:3000/blog/[slug]`
+- To change `draft: false` when ready to publish
+- **Before publishing:** add at least one image to `images: []` — posts without an image fall back to the generic site banner for social sharing. Store images at `public/static/images/posts/YYYY/post-slug-name/` and reference as `/static/images/posts/YYYY/post-slug-name/image.png`.
diff --git a/.claude/settings.local.json b/.claude/settings.local.json
new file mode 100644
index 0000000..c5a9c62
--- /dev/null
+++ b/.claude/settings.local.json
@@ -0,0 +1,7 @@
+{
+  "permissions": {
+    "additionalDirectories": [
+      "c:\\Dave\\Projects\\DaveGoosem.github.io\\.claude"
+    ]
+  }
+}
diff --git a/CLAUDE.md b/CLAUDE.md
new file mode 100644
index 0000000..28c1cda
--- /dev/null
+++ b/CLAUDE.md
@@ -0,0 +1,73 @@
+# DaveGoosem.com — Claude Code Context
+
+## Stack
+
+- **Framework**: Next.js 14 (App Router), TypeScript
+- **Content**: Contentlayer2 — MDX files in `data/blog/` and `data/authors/`
+- **Styles**: Tailwind CSS 3 (class-based dark mode, Space Grotesk font)
+- **Deployment**: Vercel
+- **Package manager**: `yarn` — never use `npm install` or `npm run`
+- **Comments**: Giscus (GitHub Discussions), configured via env vars
+- **Search**: kbar (local `public/search.json`, regenerated on build)
+- **Analytics**: Google Analytics via Pliny
+
+## Key Commands
+
+```bash
+yarn dev          # start dev server
+yarn build        # production build + postbuild (RSS, search index)
+yarn lint         # ESLint with auto-fix
+```
+
+## Path Aliases (tsconfig.json)
+
+| Alias                    | Resolves to               |
+| ------------------------ | ------------------------- |
+| `@/components/*`         | `components/*`            |
+| `@/data/*`               | `data/*`                  |
+| `@/layouts/*`            | `layouts/*`               |
+| `@/css/*`                | `css/*`                   |
+| `contentlayer/generated` | `.contentlayer/generated` |
+
+## Key Directories
+
+| Path                    | Purpose                                |
+| ----------------------- | -------------------------------------- |
+| `app/`                  | Next.js App Router pages               |
+| `components/`           | Shared React components                |
+| `layouts/`              | Blog post layout templates             |
+| `data/blog/`            | MDX blog posts (41 posts)              |
+| `data/authors/`         | Author MDX profiles                    |
+| `data/siteMetadata.js`  | Site-wide config (title, URL, socials) |
+| `public/static/images/` | Static image assets                    |
+| `scripts/`              | postbuild.mjs (RSS + search index)     |
+
+## SEO & Structured Data
+
+The following are already implemented — do not duplicate or replace them:
+
+- **Canonical URLs** — set in `generateMetadata()` in `app/blog/[...slug]/page.tsx` via `post.canonicalUrl ?? computed URL`
+- **`BlogPosting` JSON-LD** — generated by Contentlayer in `contentlayer.config.ts` (includes `publisher`, `mainEntityOfPage`, `author`). Injected in `app/blog/[...slug]/page.tsx`
+- **`BreadcrumbList` JSON-LD** — injected alongside BlogPosting in `app/blog/[...slug]/page.tsx`
+- **`WebSite` JSON-LD** — injected in `app/layout.tsx` (covers all pages)
+- **Publisher logo** — uses `DaveGoosem.com_Logo_Black.png` (not the white variant) so it is legible on white backgrounds as Google requires
+- **Sitemap** — `app/sitemap.ts`, auto-generated, excludes drafts
+- **Robots** — `app/robots.ts`, auto-generated
+
+## Constraints
+
+- Do not add API routes — this is a static/SSG blog with no backend
+- Do not add a database or server-side state
+- Contentlayer2 auto-generates TypeScript types on `yarn build` / `yarn dev` — do not edit `.contentlayer/` manually
+- ESLint uses flat config (`eslint.config.mjs`) — not `.eslintrc`
+- External links require `target="_blank"` and `rel="noopener noreferrer"` (enforced by ESLint)
+
+## Gotchas
+
+**Contentlayer scans all of `data/`** — any plain `.md` file placed inside `data/` (e.g. a `CLAUDE.md`) must be added to `contentDirExclude` in `contentlayer.config.ts` → `makeSource()`, otherwise Contentlayer warns and skips it at startup.
+
+**Content Security Policy** — `next.config.js` contains a hand-written CSP string. If you add any external script, font, frame, or image source (e.g. a new analytics provider, embed, or CDN), add its hostname to the appropriate CSP directive in that file or the browser will silently block it.
+
+**Remote images** — `next/image` only proxies domains listed in `next.config.js` → `images.remotePatterns`. Currently only `picsum.photos` is allowed. Add new domains there before using external image URLs in posts or components.
+
+**Bundle analysis** — run `ANALYZE=true yarn build` to open the webpack bundle visualiser. Useful before committing large new dependencies.
diff --git a/app/CLAUDE.md b/app/CLAUDE.md
new file mode 100644
index 0000000..d443274
--- /dev/null
+++ b/app/CLAUDE.md
@@ -0,0 +1,43 @@
+# App Router — Claude Code Context
+
+## Route Structure
+
+| Route               | File                            | Notes                                    |
+| ------------------- | ------------------------------- | ---------------------------------------- |
+| `/`                 | `app/page.tsx`                  | Home (recent posts via `Main.tsx`)       |
+| `/blog`             | `app/blog/page.tsx`             | Post listing                             |
+| `/blog/[...slug]`   | `app/blog/[...slug]/page.tsx`   | Individual post — slug from MDX filename |
+| `/blog/page/[page]` | `app/blog/page/[page]/page.tsx` | Paginated listing                        |
+| `/tags`             | `app/tags/page.tsx`             | All tags                                 |
+| `/tags/[tag]`       | `app/tags/[tag]/page.tsx`       | Posts by tag                             |
+| `/about`            | `app/about/page.tsx`            | About page                               |
+| `/projects`         | `app/projects/page.tsx`         | Projects page                            |
+
+## Blog Post Rendering
+
+Posts flow: MDX file → Contentlayer2 (generates typed object) → `app/blog/[...slug]/page.tsx` → layout component (e.g. `DaveLayout`).
+
+## SEO & Metadata
+
+**For static pages** (`/about`, `/projects`, `/tags`, etc.) — use `genPageMetadata()` from `app/seo.tsx`:
+
+```ts
+import { genPageMetadata } from 'app/seo'
+export const metadata = genPageMetadata({ title: 'Page Title', description: '...' })
+```
+
+**For blog posts** — metadata is generated dynamically in `app/blog/[...slug]/page.tsx` via `generateMetadata()`. It reads from the post's Contentlayer fields directly — do not duplicate it elsewhere.
+
+**Do not write raw `<meta>` tags** — always go through the Next.js Metadata API or `genPageMetadata()`.
+
+**Structured data (JSON-LD)** — blog posts render two `<script type="application/ld+json">` blocks: `BlogPosting` (from Contentlayer's `structuredData` computed field, enriched with author in `page.tsx`) and `BreadcrumbList` (built inline in `page.tsx`). The root layout renders a `WebSite` schema. Do not add duplicate schema blocks.
+
+**Auto-generated files** (do not edit manually):
+
+- `app/tag-data.json` — tag counts, written by Contentlayer's `onSuccess` callback
+- `public/search.json` — kbar search index, written by the same callback
+- `robots.ts` and `sitemap.ts` generate `/robots.txt` and `/sitemap.xml` at build time
+
+## No API Routes
+
+This is a static blog — there are no `/api/` routes. Do not add them.
diff --git a/app/blog/[...slug]/page.tsx b/app/blog/[...slug]/page.tsx
index cfc29ed..711541c 100644
--- a/app/blog/[...slug]/page.tsx
+++ b/app/blog/[...slug]/page.tsx
@@ -52,6 +52,7 @@ export async function generateMetadata({
       url: img.includes('http') ? img : siteMetadata.siteUrl + img,
     }
   })
+  const canonicalUrl = post.canonicalUrl ?? `${siteMetadata.siteUrl}/${post.path}`
 
   return {
     title: post.title,
@@ -74,6 +75,9 @@ export async function generateMetadata({
       description: post.summary,
       images: imageList,
     },
+    alternates: {
+      canonical: canonicalUrl,
+    },
   }
 }
 
@@ -110,6 +114,21 @@ export default async function Page({ params }: { params: Promise<{ slug: string[
     }
   })
 
+  const breadcrumbSchema = {
+    '@context': 'https://schema.org',
+    '@type': 'BreadcrumbList',
+    itemListElement: [
+      { '@type': 'ListItem', position: 1, name: 'Home', item: siteMetadata.siteUrl },
+      { '@type': 'ListItem', position: 2, name: 'Blog', item: `${siteMetadata.siteUrl}/blog` },
+      {
+        '@type': 'ListItem',
+        position: 3,
+        name: post.title,
+        item: `${siteMetadata.siteUrl}/${post.path}`,
+      },
+    ],
+  }
+
   const Layout = layouts[post.layout || defaultLayout]
 
   return (
@@ -118,6 +137,10 @@ export default async function Page({ params }: { params: Promise<{ slug: string[
         type="application/ld+json"
         dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
       />
+      <script
+        type="application/ld+json"
+        dangerouslySetInnerHTML={{ __html: JSON.stringify(breadcrumbSchema) }}
+      />
       <Layout content={mainContent} authorDetails={authorDetails} next={next} prev={prev}>
         <MDXLayoutRenderer code={post.body.code} components={components} toc={post.toc} />
       </Layout>
diff --git a/app/layout.tsx b/app/layout.tsx
index f6092ae..df74e6b 100644
--- a/app/layout.tsx
+++ b/app/layout.tsx
@@ -58,6 +58,27 @@ export const metadata: Metadata = {
   },
 }
 
+const websiteSchema = {
+  '@context': 'https://schema.org',
+  '@type': 'WebSite',
+  name: siteMetadata.title,
+  url: siteMetadata.siteUrl,
+  description: siteMetadata.description,
+  author: {
+    '@type': 'Person',
+    name: siteMetadata.author,
+    url: siteMetadata.siteUrl,
+  },
+  potentialAction: {
+    '@type': 'SearchAction',
+    target: {
+      '@type': 'EntryPoint',
+      urlTemplate: `${siteMetadata.siteUrl}/blog?q={search_term_string}`,
+    },
+    'query-input': 'required name=search_term_string',
+  },
+}
+
 export default function RootLayout({ children }: { children: React.ReactNode }) {
   return (
     <html
@@ -76,6 +97,10 @@ export default function RootLayout({ children }: { children: React.ReactNode })
       <meta name="theme-color" media="(prefers-color-scheme: dark)" content="#000" />
       <link rel="alternate" type="application/rss+xml" href="/feed.xml" />
       <body className="bg-white pl-[calc(100vw-100%)] text-black antialiased dark:bg-gray-950 dark:text-white">
+        <script
+          type="application/ld+json"
+          dangerouslySetInnerHTML={{ __html: JSON.stringify(websiteSchema) }}
+        />
         <ThemeProviders>
           <Analytics analyticsConfig={siteMetadata.analytics as AnalyticsConfig} />
           <SpeedInsights />
diff --git a/app/tag-data.json b/app/tag-data.json
index 6019344..06fa45e 100644
--- a/app/tag-data.json
+++ b/app/tag-data.json
@@ -1 +1,41 @@
-{"atomic-design":1,"sitecore":38,"headless-cms":1,"multi-site":2,"design-systems":1,"azure":5,"cloud":7,"xmcloud":8,"sitecoreai":8,"pages":1,"saas":6,"sxa":4,"jss":9,"headless":11,"devops":2,"searchstax":2,"solr":6,"cicd":4,"vercel":4,"helix":3,"react":1,"nextjs":5,"architecture":5,"sitecore-send":2,"cdp":1,"aws":1,"accessibility":1,"security":1,"storybook":2,"unit-testing":2,"aspnet":1,"seo":1,"github-workflows":1,"composable":1,"dxp":1,"ai":1,"strategy":1}
\ No newline at end of file
+{
+  "atomic-design": 1,
+  "sitecore": 39,
+  "headless-cms": 1,
+  "multi-site": 2,
+  "design-systems": 1,
+  "azure": 5,
+  "cloud": 7,
+  "xmcloud": 8,
+  "sitecoreai": 8,
+  "pages": 1,
+  "saas": 6,
+  "sxa": 4,
+  "jss": 9,
+  "headless": 11,
+  "devops": 2,
+  "searchstax": 2,
+  "solr": 6,
+  "cicd": 4,
+  "vercel": 4,
+  "helix": 3,
+  "react": 1,
+  "nextjs": 5,
+  "architecture": 5,
+  "sitecore-send": 2,
+  "cdp": 1,
+  "search": 1,
+  "sitecore-search": 1,
+  "aws": 1,
+  "accessibility": 1,
+  "security": 1,
+  "storybook": 2,
+  "unit-testing": 2,
+  "aspnet": 1,
+  "seo": 1,
+  "github-workflows": 1,
+  "composable": 1,
+  "dxp": 1,
+  "ai": 1,
+  "strategy": 1
+}
diff --git a/components/CLAUDE.md b/components/CLAUDE.md
new file mode 100644
index 0000000..7488b4e
--- /dev/null
+++ b/components/CLAUDE.md
@@ -0,0 +1,23 @@
+# Components — Claude Code Context
+
+## Import Aliases
+Use `@/components/` not relative paths when importing from outside this directory.
+
+## Wrapper Components — Always Use These
+| Use this | Instead of |
+|----------|-----------|
+| `@/components/Link` | `next/link` directly |
+| `@/components/Image` | `next/image` directly |
+
+The wrappers add security attributes to external links and handle the blog's image conventions.
+
+## MDX Components
+`MDXComponents.tsx` maps HTML elements and custom tags to React components for use inside MDX blog posts. Register any new component here if it needs to be usable in MDX.
+
+## Styling
+- Use Tailwind utility classes — no custom CSS unless in `css/tailwind.css`
+- Dark mode: use `dark:` prefix (class-based, toggled by ThemeSwitch)
+- Typography in post body is handled by `@tailwindcss/typography` (the `prose` class applied by layouts)
+
+## Social Icons
+Located in `components/social-icons/` — add new icons there, not inline in Header/Footer.
diff --git a/contentlayer.config.ts b/contentlayer.config.ts
index 4ea401c..be36895 100644
--- a/contentlayer.config.ts
+++ b/contentlayer.config.ts
@@ -106,6 +106,18 @@ export const Blog = defineDocumentType(() => ({
         description: doc.summary,
         image: doc.images ? doc.images[0] : siteMetadata.socialBanner,
         url: `${siteMetadata.siteUrl}/${doc._raw.flattenedPath}`,
+        mainEntityOfPage: {
+          '@type': 'WebPage',
+          '@id': `${siteMetadata.siteUrl}/${doc._raw.flattenedPath}`,
+        },
+        publisher: {
+          '@type': 'Organization',
+          name: siteMetadata.title,
+          logo: {
+            '@type': 'ImageObject',
+            url: `${siteMetadata.siteUrl}/static/images/Logos/DaveGoosem.com_Logo_Black.png`,
+          },
+        },
       }),
     },
   },
@@ -132,6 +144,7 @@ export const Authors = defineDocumentType(() => ({
 
 export default makeSource({
   contentDirPath: 'data',
+  contentDirExclude: ['blog/CLAUDE.md'],
   documentTypes: [Blog, Authors],
   mdx: {
     cwd: process.cwd(),
diff --git a/data/blog/CLAUDE.md b/data/blog/CLAUDE.md
new file mode 100644
index 0000000..d3698b3
--- /dev/null
+++ b/data/blog/CLAUDE.md
@@ -0,0 +1,71 @@
+# Blog Posts — Claude Code Context
+
+## Creating a New Post
+
+- File name: `kebab-case-title.mdx` in this directory (`data/blog/`)
+- Contentlayer picks up all `*.mdx` files here automatically — no registration needed
+
+## Frontmatter Schema
+
+```yaml
+---
+title: 'Your Post Title'
+date: 'YYYY-MM-DD'
+lastmod: 'YYYY-MM-DD'
+tags: ['XMCloud', 'Sitecore', 'Next.js']
+draft: true
+summary: 'One-paragraph summary displayed on listing pages and in RSS.'
+layout: DaveLayout
+images: ['/static/images/posts/YYYY/post-slug-name/og-image.png']
+authors: ['default']
+canonicalUrl: ''
+---
+```
+
+### Field notes
+
+| Field          | Required | Notes                                                                                 |
+| -------------- | -------- | ------------------------------------------------------------------------------------- |
+| `title`        | yes      | Displayed in `<h1>` and `<title>`                                                     |
+| `date`         | yes      | ISO format `'YYYY-MM-DD'` — original publish date, never change it                    |
+| `lastmod`      | no       | ISO format — set when substantially updating a post; drives `dateModified` in JSON-LD |
+| `tags`         | yes      | Array of strings; see tag list below — casing matters                                 |
+| `draft`        | yes      | `true` while writing, `false` to publish                                              |
+| `summary`      | yes      | Also used for OG description and RSS — write a complete sentence                      |
+| `layout`       | no       | Default: `DaveLayout` — see `layouts/CLAUDE.md` for differences                       |
+| `images`       | no       | **Must be non-empty before publishing.** First entry is the OG/social share image     |
+| `authors`      | no       | Defaults to `['default']` (David Goosem)                                              |
+| `canonicalUrl` | no       | Only set if this post was originally published elsewhere                              |
+
+## Images
+
+Store images at:
+
+```
+public/static/images/posts/YYYY/post-slug-name/image.png
+```
+
+Reference in MDX body as:
+
+```md
+![Alt text](/static/images/posts/YYYY/post-slug-name/image.png 'Optional title')
+```
+
+**The `images:` frontmatter field must be non-empty before setting `draft: false`.** It drives the OpenGraph/social share image — empty means the site falls back to the generic banner. Ideal OG dimensions: 1200×630px.
+
+If no purpose-built banner exists, promote the first meaningful body image:
+
+```yaml
+images: ['/static/images/posts/YYYY/post-slug-name/image.png']
+```
+
+## Contentlayer Gotcha
+
+Contentlayer scans the entire `data/` directory. Any `.md` file here (including instruction files like this one) must be listed in `contentDirExclude` in `contentlayer.config.ts`, otherwise Contentlayer logs a warning and skips it. The current exclude list is at the top of `makeSource()`.
+
+## Common Tags (existing — keep casing consistent)
+
+`XMCloud`, `Sitecore`, `JSS`, `SXA`, `SaaS`, `Next.js`, `Vercel`, `Azure`, `AWS`,
+`CI/CD`, `Accessibility`, `SEO`, `Search`, `Solr`, `Architecture`, `Helix`
+
+> ⚠️ **Tag casing is enforced by display** — use exactly the capitalisation above. In particular: `Solr` (not `SOLR`), `Next.js` (not `NextJS`), `XMCloud` (no space or hyphen).
diff --git a/data/blog/federated-search.mdx b/data/blog/federated-search.mdx
index 1394722..79fe389 100644
--- a/data/blog/federated-search.mdx
+++ b/data/blog/federated-search.mdx
@@ -1,7 +1,7 @@
 ---
 title: Federated Search with External Data and Sitecore
 date: '2020-08-18'
-tags: ['Sitecore', 'Helix', 'SOLR']
+tags: ['Sitecore', 'Helix', 'Solr']
 draft: false
 summary: In this article we look at how you might develop a Federated Search with data using both Sitecore Content and numerous other external data points.
 layout: DaveLayout
diff --git a/data/blog/indexing-external-data-with-sitecore.mdx b/data/blog/indexing-external-data-with-sitecore.mdx
index a12d424..aff7467 100644
--- a/data/blog/indexing-external-data-with-sitecore.mdx
+++ b/data/blog/indexing-external-data-with-sitecore.mdx
@@ -1,7 +1,7 @@
 ---
 title: Indexing External Data for use with Sitecore
 date: '2020-07-16'
-tags: ['Sitecore', 'SOLR']
+tags: ['Sitecore', 'Solr']
 draft: false
 summary: In this article we'll take a look at a realtively simple way in which you can utilise Sitecore to look after managing the indexing of external data for you using Solr as the Search Provider.
 layout: DaveLayout
diff --git a/data/blog/integrating-the-search-sdk-into-your-jss-nextjs-solution.mdx b/data/blog/integrating-the-search-sdk-into-your-jss-nextjs-solution.mdx
new file mode 100644
index 0000000..b910540
--- /dev/null
+++ b/data/blog/integrating-the-search-sdk-into-your-jss-nextjs-solution.mdx
@@ -0,0 +1,573 @@
+---
+title: 'Sitecore Search End-to-End: Integrating the Search SDK into Your JSS Next.js Headless Solution'
+date: '2026-04-13'
+tags: [Sitecore, Search, Sitecore Search]
+draft: false
+summary: 'A comprehensive guide to integrating Sitecore Search into a JSS Next.js headless solution — covering CEC setup, SDK options, front-end integration, multi-site source scoping, and a disciplined environment promotion workflow.'
+layout: DaveLayout
+images: []
+authors: ['default']
+---
+
+If you're running a Sitecore JSS Next.js headless front end, adding Sitecore Search is a natural next step in the composable DXP story. Unlike Solr — which comes bundled with on-premise Sitecore but requires you to manage infrastructure, scaling, and version compatibility — Sitecore Search is a fully SaaS-based AI-powered search platform. You configure it through a browser, it crawls your sites, and you integrate the results into your front end via a React SDK. No servers. No Solr topology decisions.
+
+That said, there are real gotchas around multi-site setups, managing multiple environments, and the currently limited ability to promote configuration changes from non-prod to prod. This post walks through all of it end-to-end — from setting up the Customer Engagement Console (CEC) through to wiring up your JSS components, handling multi-site source scoping, and maintaining a sane dev-to-prod promotion workflow.
+
+---
+
+## How Sitecore Search Fits Into the Composable Stack
+
+Before diving into implementation, it's worth being clear about where Sitecore Search sits relative to your other products. In a typical Sitecore JSS headless stack, you're looking at something like this:
+
+- **Sitecore CMS** — content management and authoring, delivering content via GraphQL (Experience Edge or inline)
+- **Vercel / hosting** — hosting your Next.js JSS head(s)
+- **Sitecore Personalize** — behavioural targeting and experimentation
+- **Sitecore Search** — content discovery, typeahead, search results pages
+
+Sitecore Search is independent of your CMS's GraphQL/Edge delivery. Rather than querying your content tree directly, it crawls your _live website_ (or non-prod equivalent) and builds its own index. This is important to understand early — your Search index is populated from rendered web pages, not directly from Sitecore content items. That has implications for what you index, when you index it, and how your non-prod crawl targets are configured.
+
+---
+
+## The Two SDK Options (and Which to Use)
+
+As of 2025/2026 there are two SDK paths for integrating Sitecore Search into your React/Next.js app, and most articles mix them up without explaining the difference.
+
+**Option 1: `@sitecore-search/react` + `@sitecore-search/ui`**
+
+This is the original SDK. You install the core React SDK and optionally the UI components package — a pre-built kit of around 15 widget components (PreviewSearch, SearchResults, etc.) built on top of styled-components.
+
+```bash
+npm install @sitecore-search/react @sitecore-search/ui
+```
+
+**Option 2: `@sitecore-cloudsdk/search`**
+
+This is the newer Cloud SDK approach, part of the broader `@sitecore-cloudsdk` family that also handles CDP and Personalize integrations. It uses an Edge Context ID rather than a standalone API key, and is the direction Sitecore is moving for all new headless builds.
+
+```bash
+npm install @sitecore-cloudsdk/core @sitecore-cloudsdk/search
+```
+
+**Which should you use?** For a new project targeting the latest composable Sitecore stack, lean towards `@sitecore-cloudsdk/search` as it aligns with the unified Cloud SDK direction. However, if your team is already familiar with the `@sitecore-search/react` SDK, or you're referencing the official Starter Kit, the older SDK is still fully supported and better documented at the time of writing. This post primarily uses the `@sitecore-search/react` SDK as it has more community examples and a more developed UI kit — but the CEC configuration and multi-environment concepts apply to both.
+
+---
+
+## Part 1: CEC Setup — Do This Before Writing Any Code
+
+The Customer Engagement Console (CEC) at `cec.sitecorecloud.io` is where all search configuration lives. Every attribute, source, crawler, and widget is managed here. Critically, **this is also where your biggest operational challenge lives** — and we'll come back to that in the environment management section.
+
+### Understanding Your Environments in the CEC
+
+The CEC operates with a concept of separate domain instances — typically a **Non-Production** instance and a **Production** instance. Each is a completely separate tenant with its own sources, attributes, API keys, and widget configuration.
+
+The licensing model for Sitecore Search typically provides one production instance and one non-production instance. The Search non-prod instance is used by _all_ your non-prod environments (dev, QA, UAT) simultaneously — there is no per-environment isolation built in. Your production instance is used only by your live production environment.
+
+This gives you an architecture that looks like this:
+
+```
+┌─────────────────────────────────────────────┐
+│         Sitecore Search: Non-Prod CEC       │
+│  Sources: dev.site-a.com, dev.site-b.com    │
+│  API Key: <non-prod-api-key>                │
+└─────────────────────────────────────────────┘
+        ↑               ↑              ↑
+    JSS DEV          JSS TEST         JSS UAT
+  Vercel (DEV)    Vercel (TEST)   Vercel (UAT)
+
+┌─────────────────────────────────────────────┐
+│           Sitecore Search: Prod CEC         │
+│  Sources: site-a.com, site-b.com            │
+│  API Key: <prod-api-key>                    │
+└─────────────────────────────────────────────┘
+        ↑
+   JSS Production
+   Vercel (production)
+```
+
+The implication is that any widget tuning, boosting rules, facet configuration, or document extractor changes you make in the Non-Prod CEC need to be **manually replicated** into the Prod CEC when you're ready to go live. More on managing this process below.
+
+### Step 1: Define Your Attributes
+
+Before setting up sources or widgets, define your domain attributes. Think of these as the fields your content will be indexed with. Navigate to **Administration → Domain Settings → Attributes**.
+
+Sitecore ships a few default entities (Content, Product, Category, Store). For a typical JSS/content site you'll be working with the **Content** entity. Common attributes to set up:
+
+| Attribute     | Type      | Features                                    |
+| ------------- | --------- | ------------------------------------------- |
+| `title`       | String    | Textual Relevance, Return in API Response   |
+| `description` | String    | Textual Relevance, Return in API Response   |
+| `url`         | String    | Return in API Response                      |
+| `image_url`   | String    | Return in API Response                      |
+| `type`        | String    | Facets, Return in API Response              |
+| `category`    | String    | Facets, Suggestions, Return in API Response |
+| `date`        | Timestamp | Sorting, Return in API Response             |
+| `site_name`   | String    | Facets (critical for multi-site)            |
+
+> ⚠️ **Important:** The "Will be used in" feature settings on an attribute **cannot be changed after creation**. If you need to add Facet support to an attribute you've already created without it, you must delete it and recreate it. Plan your attribute schema carefully before you start indexing.
+
+You'll also need a suggestions block. Ensure the field used for title suggestions is named `title_context_aware` or configure your suggestion block to point to your `title` attribute. This is what powers the typeahead experience.
+
+### Step 2: Set Up Your Sources
+
+A **Source** is a crawler configuration targeting a website (or set of pages). For each site in your multi-site setup, you'll create a separate source pointing at each head.
+
+Navigate to **Sources → Add Source** and select **Web Crawler (Advanced)**. This is the option you want — it supports multi-language, JavaScript rendering, and gives you the most control over document extraction.
+
+Key settings to configure for each source:
+
+**Triggers — how the crawler knows what to crawl**
+
+Using your sitemap is the most reliable trigger. Most sites already expose `/sitemap.xml` for SEO purposes, so reuse it here. The crawler will enumerate all pages in the sitemap and crawl each one.
+
+```
+Trigger type: Sitemap
+URL: https://dev.site-a.com/sitemap.xml
+```
+
+**Scan Frequency**
+
+Configure how often the crawler re-indexes your site. For non-prod you might set this less frequently (weekly is fine), while for production you'll want to balance freshness against crawl cost.
+
+**Document Extractors**
+
+This is where most of the custom logic lives, and is the most common area that differs between implementations. Extractors define how the crawler maps page content to your attributes. You'll use the **JS Extractor**, which runs a Cheerio-based script against the crawled HTML.
+
+A basic extractor for a JSS site might look like this:
+
+```javascript
+function extract(request, response, document) {
+  const $ = document.content
+
+  // Pull from meta tags that your JSS head renders
+  const title = $('meta[property="og:title"]').attr('content') || $('title').text() || ''
+
+  const description =
+    $('meta[property="og:description"]').attr('content') ||
+    $('meta[name="description"]').attr('content') ||
+    ''
+
+  const imageUrl = $('meta[property="og:image"]').attr('content') || ''
+
+  // Use a data attribute on your layout for structured type data
+  const type = $('body').data('page-type') || 'content'
+
+  // Site name — critical for multi-site filtering
+  const siteName = $('body').data('site-name') || 'default'
+
+  return {
+    title,
+    description,
+    image_url: imageUrl,
+    type,
+    site_name: siteName,
+  }
+}
+```
+
+> 💡 **Tip:** In your JSS layout component, render `data-site-name` and `data-page-type` attributes on `<body>` using your SXA site settings. This gives your crawler reliable structured metadata to extract without needing to scrape visible content. This is especially important in multi-site solutions where you want to filter results per-site at query time.
+
+You can test your extractor JS against live HTML using the [Cheerio playground](https://try.cheerio.js.org/) before saving it in the CEC. This will save you a lot of unnecessary re-crawl cycles.
+
+**Excluding Pages from Search**
+
+Not every page should appear in search results — search pages themselves, landing pages, gated content, etc. The cleanest approach is to add a custom meta tag to those pages:
+
+```html
+<meta property="excludeFromSearch" content="true" />
+```
+
+Then in your document extractor, check for it and return `null` to prevent indexing:
+
+```javascript
+function extract(request, response, document) {
+  const $ = document.content
+
+  const exclude = $('meta[property="excludeFromSearch"]').attr('content')
+  if (exclude === 'true') return null
+
+  // ... rest of extraction
+}
+```
+
+In Sitecore, create a `_Search` base template at the Foundation layer with an `excludeFromSearch` checkbox field. Add it as a base template on your Page template, and render the meta tag conditionally in your JSS layout.
+
+Optionally if you exclude the page from Sitemap it won't be crawled as well given we're using the sitemap for our crawling.
+
+### Step 3: Configure Widgets
+
+Widgets are the reusable search UI configurations — they define things like which facets are displayed, how results are sorted, and what boosting rules apply. You need at least two:
+
+- **PreviewSearch** — the typeahead/inline search widget that shows as users type
+- **SearchResults** — the full results page widget
+
+Create each widget in **Widgets**, noting the `rfk_id` assigned to each. This ID is how your React components connect to the right widget configuration.
+
+For PreviewSearch, ensure your suggestions block is configured and pointing to the right attributes. For SearchResults, configure your facet fields (map them to the attributes you set up with Facet enabled).
+
+> ⚠️ Another important quirk: the widget **"Will be used in"** setting cannot be changed after creation (just like attributes). Set it correctly — typically "Search" for SearchResults and "Preview Search" for typeahead.
+
+---
+
+## Part 2: Front-End Integration
+
+With the CEC configured and content indexed, it's time to wire up the front end. Here's the setup for a JSS Next.js application using `@sitecore-search/react`.
+
+### Installation
+
+```bash
+npm install @sitecore-search/react @sitecore-search/ui styled-components
+```
+
+### Environment Variables
+
+You'll need different values for each environment tier. In your `.env.local` (and in Vercel's environment variable settings per deployment):
+
+```env
+# Non-prod environments (dev, QA, UAT)
+NEXT_PUBLIC_SEARCH_ENV=staging
+NEXT_PUBLIC_SEARCH_CUSTOMER_KEY=your-non-prod-customer-key
+NEXT_PUBLIC_SEARCH_API_KEY=your-non-prod-api-key
+
+# Production (set separately in Vercel prod environment)
+# NEXT_PUBLIC_SEARCH_ENV=prod
+# NEXT_PUBLIC_SEARCH_CUSTOMER_KEY=your-prod-customer-key
+# NEXT_PUBLIC_SEARCH_API_KEY=your-prod-api-key
+```
+
+> 📝 `NEXT_PUBLIC_SEARCH_ENV` accepts specific values: `prod`, `staging`, `prodEu`, or `apse2`. It is _not_ a free-text label — it maps to Sitecore's actual API endpoint regions. For Australian/APAC implementations, `apse2` is the relevant value.
+
+### WidgetsProvider Setup
+
+The `WidgetsProvider` is the root component that initialises the Search SDK and manages all communication between your widget components. It should wrap the parts of your application that use search — typically at the layout level.
+
+In your JSS `Layout.tsx`:
+
+```tsx
+import { WidgetsProvider, PageController } from '@sitecore-search/react'
+
+const searchConfig = {
+  env: process.env.NEXT_PUBLIC_SEARCH_ENV as string,
+  customerKey: process.env.NEXT_PUBLIC_SEARCH_CUSTOMER_KEY as string,
+  apiKey: process.env.NEXT_PUBLIC_SEARCH_API_KEY as string,
+}
+
+export default function Layout({ layoutData }: LayoutProps) {
+  return (
+    <WidgetsProvider {...searchConfig}>
+      {/* Your existing layout markup */}
+      <Header />
+      <main>{/* page content */}</main>
+      <Footer />
+    </WidgetsProvider>
+  )
+}
+```
+
+### Building the PreviewSearch (Typeahead) Component
+
+The PreviewSearch widget is the typeahead experience in your site header. It's the most visible part of Search and the trickiest to get right in a multi-site setup.
+
+Create a Sitecore rendering in the CMS and a corresponding component in your JSS app:
+
+```tsx
+// components/search/PreviewSearch.tsx
+import { usePreviewSearch, widget } from '@sitecore-search/react'
+import { PreviewSearch as PreviewSearchUI } from '@sitecore-search/ui'
+import { useRouter } from 'next/router'
+
+interface PreviewSearchProps {
+  rfkId: string // Pass this from your Sitecore rendering parameters
+}
+
+const PreviewSearchComponent = ({ rfkId }: PreviewSearchProps) => {
+  const router = useRouter()
+
+  const {
+    widgetRef,
+    actions: { onItemClick, onKeyphraseChange },
+    queryResult: { data: { suggestion: { title_context_aware: suggestions = [] } = {} } = {} },
+  } = usePreviewSearch({
+    query: (query) => query.getRequest().setSearchQueryHighlightFragmentSize(100),
+  })
+
+  const handleSubmit = (value: string) => {
+    router.push(`/search?q=${encodeURIComponent(value)}`)
+  }
+
+  return (
+    <PreviewSearchUI.Root ref={widgetRef}>
+      <PreviewSearchUI.Input
+        onChange={(e) => onKeyphraseChange({ keyphrase: e.target.value })}
+        onEnterKeyphrase={handleSubmit}
+      />
+      {suggestions.length > 0 && (
+        <PreviewSearchUI.Suggestions>
+          {suggestions.map((suggestion, index) => (
+            <PreviewSearchUI.SuggestionItem
+              key={index}
+              onClick={() => handleSubmit(suggestion.text)}
+            >
+              {suggestion.text}
+            </PreviewSearchUI.SuggestionItem>
+          ))}
+        </PreviewSearchUI.Suggestions>
+      )}
+    </PreviewSearchUI.Root>
+  )
+}
+
+// Widget wrapping connects this component to the CEC widget configuration
+export const PreviewSearch = widget(
+  PreviewSearchComponent,
+  PreviewSearchUI.Default,
+  'preview-search'
+)
+```
+
+> 💡 The `rfk_id` you pass here must match the ID assigned to your widget in the CEC. For multi-site, you can either create separate widgets per site in the CEC and pass different `rfk_id` values per site, or use one shared widget and filter results using a source filter at query time.
+
+### Building the Search Results Page
+
+Create a `/search` page in your Next.js app and a Search Results component:
+
+```tsx
+// components/search/SearchResults.tsx
+import { useSearchResults, widget, FilterEqual } from '@sitecore-search/react'
+import { SearchResults as SearchResultsUI, Pagination, FacetList } from '@sitecore-search/ui'
+import { useRouter } from 'next/router'
+
+interface SearchResultItem {
+  id: string
+  title: string
+  description: string
+  url: string
+  image_url?: string
+  type?: string
+  site_name?: string
+}
+
+const SearchResultsComponent = () => {
+  const router = useRouter()
+  const keyphrase = (router.query.q as string) || ''
+
+  const {
+    widgetRef,
+    actions: { onResultsPerPageChange, onPageNumberChange, onFacetClick },
+    state: { page, itemsPerPage },
+    queryResult: {
+      data: { total_item: totalItems = 0, facet: facets = [], content: results = [] } = {},
+    },
+  } = useSearchResults<SearchResultItem>({
+    query: (query) => {
+      query
+        .getRequest()
+        .setSearchQueryKeyphrase(keyphrase)
+        // Multi-site: filter to only show results from this site
+        .addSearchQueryFilter(
+          new FilterEqual('site_name', process.env.NEXT_PUBLIC_SITE_NAME as string)
+        )
+    },
+  })
+
+  return (
+    <div ref={widgetRef}>
+      <p>
+        {totalItems} results for "{keyphrase}"
+      </p>
+
+      <div className="search-layout">
+        {/* Facets sidebar */}
+        <aside>
+          {facets.map((facet) => (
+            <FacetList key={facet.name} facet={facet} onFacetClick={onFacetClick} />
+          ))}
+        </aside>
+
+        {/* Results */}
+        <main>
+          {results.map((result) => (
+            <article key={result.id}>
+              {result.image_url && <img src={result.image_url} alt={result.title} />}
+              <h3>
+                <a href={result.url}>{result.title}</a>
+              </h3>
+              <p>{result.description}</p>
+            </article>
+          ))}
+
+          <Pagination
+            currentPage={page}
+            totalItems={totalItems}
+            itemsPerPage={itemsPerPage}
+            onPageChange={onPageNumberChange}
+          />
+        </main>
+      </div>
+    </div>
+  )
+}
+
+export const SearchResults = widget(
+  SearchResultsComponent,
+  SearchResultsUI.Default,
+  'search-results'
+)
+```
+
+Add `NEXT_PUBLIC_SITE_NAME` to your Vercel environment variables, set per-site/per-head deployment. This is the filter that scopes search results to the current site — essential in a multi-site setup where all sites share the same non-prod Search instance.
+
+### The `@sitecore-search/ui` Bundle Size Gotcha
+
+Before you commit to using the full `@sitecore-search/ui` package in production, be aware of a meaningful performance trade-off. Including the full UI kit has been reported to drop Lighthouse performance scores significantly, with "Reduce unused JavaScript" appearing as a red flag in audits. The package ships all widget templates together without deep tree-shaking support.
+
+Your options:
+
+1. **Use the UI kit but measure it.** Run a Lighthouse audit with and without the package. If your score drops below acceptable thresholds, move to option 2.
+2. **Use only the SDK hooks (`@sitecore-search/react`) and build your own UI.** The hooks (`usePreviewSearch`, `useSearchResults`) are lean and give you full control. Pair with your existing Tailwind components.
+3. **Hybrid approach.** Use the SDK hooks directly for components in your critical rendering path (header PreviewSearch), and use the UI kit for the lower-priority search results page where the performance impact is less significant.
+
+For most client builds, option 2 — using the SDK hooks with your own Tailwind-styled components — produces the best balance of performance and design consistency with the rest of your site.
+
+---
+
+## Part 3: Multi-Site Source Scoping
+
+If you're following a proper multi-site setup (as covered in previous posts), you have multiple Next.js heads, each deployed to their own Vercel project. Here's how to manage Search across them cleanly.
+
+### One Source Per Site Per Environment Tier
+
+In the CEC, create a source for each site:
+
+**Non-Prod CEC sources:**
+
+- `Site A — Non-Prod` → crawls `dev.site-a.com`
+- `Site B — Non-Prod` → crawls `dev.site-b.com`
+
+**Prod CEC sources:**
+
+- `Site A — Prod` → crawls `site-a.com`
+- `Site B — Prod` → crawls `site-b.com`
+
+All non-prod environments (dev, QA, UAT) share the non-prod CEC and its sources, connected via the same non-prod API key. Each Vercel deployment has its own env var pointing to the appropriate CEC key.
+
+### Scoping Results Per Site at Query Time
+
+As shown in the Search Results component above, add a `FilterEqual` on `site_name` using the `NEXT_PUBLIC_SITE_NAME` environment variable. Set this per Vercel deployment:
+
+```
+# Site A Vercel project (all environments)
+NEXT_PUBLIC_SITE_NAME=site-a
+
+# Site B Vercel project (all environments)
+NEXT_PUBLIC_SITE_NAME=site-b
+```
+
+And in your document extractor, ensure `site_name` is populated consistently:
+
+```javascript
+// In your CEC document extractor
+const siteName = $('body').data('site-name') || 'default';
+return { ..., site_name: siteName };
+```
+
+In your JSS layout, render the data attribute:
+
+```tsx
+// _document.tsx or Layout.tsx
+<body data-site-name={process.env.NEXT_PUBLIC_SITE_NAME}>
+```
+
+This creates a clean chain: Vercel env var → rendered HTML attribute → crawled by Search → indexed as `site_name` attribute → filtered at query time per-site.
+
+### Separate Widgets or Shared Widgets?
+
+For PreviewSearch, you can use the same CEC widget across all sites (the `rfk_id` is identical in both CEC instances) since the site scoping is handled at the source/filter level. However, if your sites have meaningfully different facet schemas or boosting rules, create separate widgets per site and pass the appropriate `rfk_id` from Sitecore rendering parameters.
+
+---
+
+## Part 4: Environment Promotion — The Manual Problem
+
+This is the part of Sitecore Search that will catch you off guard if you're not prepared for it.
+
+**There is currently no automated way to export configuration from the Non-Prod CEC and import it into the Prod CEC.** This applies to sources, document extractors, widget settings, boosting rules, facet configuration — all of it. Each change made in Non-Prod must be manually replicated in Prod.
+
+The Sitecore team has confirmed this migration capability is on their roadmap, but until it ships, you need a disciplined process to manage it.
+
+### A Workable Promotion Workflow
+
+The approach that works best in practice combines source control discipline for extractor code with a structured release note process for everything else.
+
+**1. Version control your document extractor scripts**
+
+Even though extractor scripts don't run as part of your code deployment, keep them in your repository. Create a folder structure like:
+
+```
+/search-config
+  /extractors
+    site-a.js
+    site-b.js
+  /widgets
+    preview-search-config.md
+    search-results-config.md
+  CHANGELOG.md
+```
+
+When you modify an extractor in the Non-Prod CEC, also update the file in source control and commit it with a meaningful message. This gives you a versioned history and makes it obvious what needs to be replicated to Prod.
+
+**2. Maintain a Search Config CHANGELOG**
+
+For changes that can't be captured in code (widget facet settings, boosting rules, sort configuration), maintain a `CHANGELOG.md` in your `/search-config` folder:
+
+```markdown
+## [Unreleased — Pending Prod Promotion]
+
+### Non-Prod CEC Changes
+
+- Added `category` facet to SearchResults widget
+- Boosted documents with type=article by 1.5x
+- Updated site-a extractor to extract `author` field
+
+## [2025-03-15] — Promoted to Prod
+
+- Added `type` facet to SearchResults widget
+- Updated sitemap trigger URL for Site B
+```
+
+Tie this to your sprint/release process. Before any production deployment, the promotion checklist includes: apply all `[Unreleased]` Search config changes to the Prod CEC, then move them to a dated `Promoted to Prod` entry.
+
+**3. Use the CEC API Explorer to validate parity**
+
+The CEC's **Developer Resources → API Explorer** lets you fire search queries against both your Non-Prod and Prod instances and compare responses. After promoting changes, use this to verify your results, facets, and suggestions match expectations before signing off.
+
+**4. Synchronise crawls to your deployment timeline**
+
+When you deploy a significant change to content structure (new page types, new meta attributes, changed URL patterns), trigger a manual re-crawl in the CEC after deployment. Don't rely on the scheduled crawl to pick it up — especially for Prod. Navigate to **Sources → [Your Source] → Scan Now** after each significant content or structure deployment.
+
+### Non-Prod Source Targets and Environment Isolation
+
+One practical problem with sharing a single non-prod CEC across dev, QA, and UAT is that the Search sources point at specific URLs. If your dev environment is at `dev.site-a.com`, your CEC non-prod source crawls that URL. QA at `qa.site-a.com` is not crawled.
+
+A few options for managing this:
+
+**Option A — Accept it.** Dev gets the most up-to-date non-prod index (since its URL is the crawl target). QA and UAT use the same non-prod API key and index, which is "good enough" for testing the integration even if it's not crawling QA-specific content.
+
+**Option B — Multiple sources in one non-prod CEC.** Create a source per environment URL (`dev.site-a.com`, `qa.site-a.com`). All index into the same non-prod domain. Use an additional `env_name` attribute in your extractor to tag documents by source environment, and filter by it in your non-prod head deployments.
+
+**Option C — Treat non-prod Search as best-effort.** Accept that Search integration testing is done primarily against dev, and use QA/UAT for testing the UI integration (does the component render, do results appear) rather than validating the indexed content quality. Reserve content quality validation for production after a controlled go-live.
+
+Most teams end up with a mix of A and C in practice — and that's fine, as long as the team understands the limitation and doesn't treat non-prod search results as representative of what prod will show.
+
+---
+
+## Wrapping Up
+
+Sitecore Search is a genuinely capable product and integrates well with a JSS/Next.js head, but it rewards teams who plan their CEC configuration carefully and establish a disciplined promotion process early. The key things to take away:
+
+- **Set up your attribute schema before you start indexing** — you can't change feature flags on existing attributes.
+- **Use a shared non-prod CEC instance across all non-prod environments**, scoped by environment variable in your Vercel deployments.
+- **Filter results by `site_name` at query time** — this is what keeps multi-site search clean.
+- **Keep your document extractor scripts in source control** — they're your most important Search configuration artefact and the CEC offers no versioning.
+- **Manually maintain a promotion changelog** until Sitecore ships native CEC config export/import. Be disciplined about it and tie it to your release process.
+- **Measure the bundle impact of `@sitecore-search/ui`** before committing to it in production — consider using the SDK hooks with your own Tailwind components instead.
+
+The next natural step from here is wiring Sitecore Search analytics into Sitecore Personalize — the click and conversion events tracked by Search become audience signals you can act on in Personalize. That's a topic for a follow-up post.
diff --git a/data/blog/sitecore-custom-facets-returns-single-words.mdx b/data/blog/sitecore-custom-facets-returns-single-words.mdx
index 92fec1d..574cb81 100644
--- a/data/blog/sitecore-custom-facets-returns-single-words.mdx
+++ b/data/blog/sitecore-custom-facets-returns-single-words.mdx
@@ -1,7 +1,7 @@
 ---
 title: Sitecore Custom Facets with 'text' field type returns single words from Solr
 date: '2020-08-25'
-tags: ['Sitecore', 'SOLR']
+tags: ['Sitecore', 'Solr']
 draft: false
 summary: This article describes an issue you may encounter when you are trying to use the faceting capability of Solr. It touches on the way you can use the Sitecore Search API to generate Solr queries which contain facets using Sitecore's FacetOn() LINQ to Sitecore capability.
 layout: DaveLayout
diff --git a/layouts/CLAUDE.md b/layouts/CLAUDE.md
new file mode 100644
index 0000000..06a863d
--- /dev/null
+++ b/layouts/CLAUDE.md
@@ -0,0 +1,28 @@
+# Layouts — Claude Code Context
+
+## Post Layouts (used in blog post frontmatter)
+
+| Layout       | Comments    | Hero image             | Author sidebar | Prev/Next | Use when                      |
+| ------------ | ----------- | ---------------------- | -------------- | --------- | ----------------------------- |
+| `DaveLayout` | Off         | Yes — from `images[0]` | Yes            | Yes       | **Default for all new posts** |
+| `PostLayout` | On (Giscus) | Yes — from `images[0]` | Yes            | Yes       | Want Giscus comments enabled  |
+| `PostBanner` | On (Giscus) | Full-bleed banner      | No             | No        | Feature/visual-heavy posts    |
+| `PostSimple` | On (Giscus) | No                     | No             | No        | Minimal/short-form posts      |
+
+`DaveLayout` is the default set in `app/blog/[...slug]/page.tsx`. Giscus is configured via env vars — see `data/siteMetadata.js`.
+
+## System Layouts (not for posts)
+
+| Layout               | Used by                                      |
+| -------------------- | -------------------------------------------- |
+| `ListLayout`         | `app/blog/page.tsx` — paginated post listing |
+| `ListLayoutWithTags` | `app/tags/[tag]/page.tsx` — filtered by tag  |
+| `AuthorLayout`       | `app/about/page.tsx` — author profile        |
+
+Do not reference these in blog post frontmatter.
+
+## Adding a New Layout
+
+1. Create `layouts/YourLayout.tsx` — follow the `LayoutProps` interface pattern from an existing layout
+2. Register it in the `layouts` map in `app/blog/[...slug]/page.tsx`
+3. It becomes available as a `layout:` value in post frontmatter
diff --git a/layouts/DaveLayout.tsx b/layouts/DaveLayout.tsx
index 86c8a54..73a6fea 100644
--- a/layouts/DaveLayout.tsx
+++ b/layouts/DaveLayout.tsx
@@ -145,6 +145,14 @@ export default function PostLayout({ content, authorDetails, next, prev, childre
             </div>
             <footer>
               <div className="flex flex-wrap">
+                <div className="w-1/4 pl-1 pt-1 sm:w-1/4 md:w-1/4 xl:w-1/2">
+                  <Image
+                    src={'/static/images/Logos/2026-Sitecore_MVP_Technology.png'}
+                    alt="2026 Sitecore Technology MVP"
+                    width={500}
+                    height={500}
+                  />
+                </div>
                 <div className="w-1/4 pl-1 pt-1 sm:w-1/4 md:w-1/4 xl:w-1/2">
                   <Image
                     src={'/static/images/Logos/2025-Sitecore-MVP-Technology.png'}
diff --git a/package-lock.json b/package-lock.json
index a478ef5..9083663 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -18,7 +18,7 @@
         "github-slugger": "^2.0.0",
         "gray-matter": "^4.0.2",
         "image-size": "1.0.0",
-        "next": "15.5.10",
+        "next": "15.5.15",
         "next-contentlayer2": "0.5.8",
         "next-themes": "^0.3.0",
         "pliny": "0.4.1",
@@ -185,7 +185,6 @@
     "node_modules/@algolia/client-search": {
       "version": "5.48.0",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@algolia/client-common": "5.48.0",
         "@algolia/requester-browser-xhr": "5.48.0",
@@ -300,7 +299,6 @@
       "version": "7.29.0",
       "dev": true,
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@babel/code-frame": "^7.29.0",
         "@babel/generator": "^7.29.0",
@@ -1828,7 +1826,6 @@
     "node_modules/@citation-js/core": {
       "version": "0.7.21",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@citation-js/date": "^0.5.0",
         "@citation-js/name": "^0.4.2",
@@ -2055,7 +2052,6 @@
     "node_modules/@effect-ts/core": {
       "version": "0.60.5",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@effect-ts/system": "^0.57.5"
       }
@@ -3661,13 +3657,15 @@
       }
     },
     "node_modules/@next/env": {
-      "version": "15.5.10",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/env/-/env-15.5.15.tgz",
+      "integrity": "sha512-vcmyu5/MyFzN7CdqRHO3uHO44p/QPCZkuTUXroeUmhNP8bL5PHFEhik22JUazt+CDDoD6EpBYRCaS2pISL+/hg==",
       "license": "MIT"
     },
     "node_modules/@next/swc-darwin-arm64": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-15.5.7.tgz",
-      "integrity": "sha512-IZwtxCEpI91HVU/rAUOOobWSZv4P2DeTtNaCdHqLcTJU4wdNXgAySvKa/qJCgR5m6KI8UsKDXtO2B31jcaw1Yw==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-15.5.15.tgz",
+      "integrity": "sha512-6PvFO2Tzt10GFK2Ro9tAVEtacMqRmTarYMFKAnV2vYMdwWc73xzmDQyAV7SwEdMhzmiRoo7+m88DuiXlJlGeaw==",
       "cpu": [
         "arm64"
       ],
@@ -3681,9 +3679,9 @@
       }
     },
     "node_modules/@next/swc-darwin-x64": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-15.5.7.tgz",
-      "integrity": "sha512-UP6CaDBcqaCBuiq/gfCEJw7sPEoX1aIjZHnBWN9v9qYHQdMKvCKcAVs4OX1vIjeE+tC5EIuwDTVIoXpUes29lg==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-15.5.15.tgz",
+      "integrity": "sha512-G+YNV+z6FDZTp/+IdGyIMFqalBTaQSnvAA+X/hrt+eaTRFSznRMz9K7rTmzvM6tDmKegNtyzgufZW0HwVzEqaQ==",
       "cpu": [
         "x64"
       ],
@@ -3697,9 +3695,9 @@
       }
     },
     "node_modules/@next/swc-linux-arm64-gnu": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-15.5.7.tgz",
-      "integrity": "sha512-NCslw3GrNIw7OgmRBxHtdWFQYhexoUCq+0oS2ccjyYLtcn1SzGzeM54jpTFonIMUjNbHmpKpziXnpxhSWLcmBA==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-15.5.15.tgz",
+      "integrity": "sha512-eVkrMcVIBqGfXB+QUC7jjZ94Z6uX/dNStbQFabewAnk13Uy18Igd1YZ/GtPRzdhtm7QwC0e6o7zOQecul4iC1w==",
       "cpu": [
         "arm64"
       ],
@@ -3713,9 +3711,9 @@
       }
     },
     "node_modules/@next/swc-linux-arm64-musl": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-15.5.7.tgz",
-      "integrity": "sha512-nfymt+SE5cvtTrG9u1wdoxBr9bVB7mtKTcj0ltRn6gkP/2Nu1zM5ei8rwP9qKQP0Y//umK+TtkKgNtfboBxRrw==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-15.5.15.tgz",
+      "integrity": "sha512-RwSHKMQ7InLy5GfkY2/n5PcFycKA08qI1VST78n09nN36nUPqCvGSMiLXlfUmzmpQpF6XeBYP2KRWHi0UW3uNg==",
       "cpu": [
         "arm64"
       ],
@@ -3729,9 +3727,9 @@
       }
     },
     "node_modules/@next/swc-linux-x64-gnu": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-15.5.7.tgz",
-      "integrity": "sha512-hvXcZvCaaEbCZcVzcY7E1uXN9xWZfFvkNHwbe/n4OkRhFWrs1J1QV+4U1BN06tXLdaS4DazEGXwgqnu/VMcmqw==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-15.5.15.tgz",
+      "integrity": "sha512-nplqvY86LakS+eeiuWsNWvfmK8pFcOEW7ZtVRt4QH70lL+0x6LG/m1OpJ/tvrbwjmR8HH9/fH2jzW1GlL03TIg==",
       "cpu": [
         "x64"
       ],
@@ -3745,9 +3743,9 @@
       }
     },
     "node_modules/@next/swc-linux-x64-musl": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-15.5.7.tgz",
-      "integrity": "sha512-4IUO539b8FmF0odY6/SqANJdgwn1xs1GkPO5doZugwZ3ETF6JUdckk7RGmsfSf7ws8Qb2YB5It33mvNL/0acqA==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-15.5.15.tgz",
+      "integrity": "sha512-eAgl9NKQ84/sww0v81DQINl/vL2IBxD7sMybd0cWRw6wqgouVI53brVRBrggqBRP/NWeIAE1dm5cbKYoiMlqDQ==",
       "cpu": [
         "x64"
       ],
@@ -3761,9 +3759,9 @@
       }
     },
     "node_modules/@next/swc-win32-arm64-msvc": {
-      "version": "15.5.7",
-      "resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-15.5.7.tgz",
-      "integrity": "sha512-CpJVTkYI3ZajQkC5vajM7/ApKJUOlm6uP4BknM3XKvJ7VXAvCqSjSLmM0LKdYzn6nBJVSjdclx8nYJSa3xlTgQ==",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-15.5.15.tgz",
+      "integrity": "sha512-GJVZC86lzSquh0MtvZT+L7G8+jMnJcldloOjA8Kf3wXvBrvb6OGe2MzPuALxFshSm/IpwUtD2mIoof39ymf52A==",
       "cpu": [
         "arm64"
       ],
@@ -3777,7 +3775,9 @@
       }
     },
     "node_modules/@next/swc-win32-x64-msvc": {
-      "version": "15.5.7",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-15.5.15.tgz",
+      "integrity": "sha512-nFucjVdwlFqxh/JG3hWSJ4p8+YJV7Ii8aPDuBQULB6DzUF4UNZETXLfEUk+oI2zEznWWULPt7MeuTE6xtK1HSA==",
       "cpu": [
         "x64"
       ],
@@ -3871,7 +3871,9 @@
       }
     },
     "node_modules/@npmcli/map-workspaces/node_modules/brace-expansion": {
-      "version": "2.0.2",
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.1.0.tgz",
+      "integrity": "sha512-TN1kCZAgdgweJhWWpgKYrQaMNHcDULHkWwQIspdtjV4Y5aurRdZpjAqn6yX3FPqTA9ngHCc4hJxMAMgGfve85w==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -3879,11 +3881,13 @@
       }
     },
     "node_modules/@npmcli/map-workspaces/node_modules/minimatch": {
-      "version": "9.0.5",
+      "version": "9.0.9",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.9.tgz",
+      "integrity": "sha512-OBwBN9AL4dqmETlpS2zasx+vTeWclWzkblfZk7KTA5j3jeOONz/tRCnZomUyvNg83wL5Zv9Ss6HMJXAgL8R2Yg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
-        "brace-expansion": "^2.0.1"
+        "brace-expansion": "^2.0.2"
       },
       "engines": {
         "node": ">=16 || 14 >=14.17"
@@ -3931,7 +3935,6 @@
     "node_modules/@opentelemetry/api": {
       "version": "1.9.0",
       "license": "Apache-2.0",
-      "peer": true,
       "engines": {
         "node": ">=8.0.0"
       }
@@ -3959,7 +3962,6 @@
     "node_modules/@opentelemetry/core": {
       "version": "1.30.1",
       "license": "Apache-2.0",
-      "peer": true,
       "dependencies": {
         "@opentelemetry/semantic-conventions": "1.28.0"
       },
@@ -4110,7 +4112,6 @@
     "node_modules/@opentelemetry/sdk-trace-base": {
       "version": "1.30.1",
       "license": "Apache-2.0",
-      "peer": true,
       "dependencies": {
         "@opentelemetry/core": "1.30.1",
         "@opentelemetry/resources": "1.30.1",
@@ -4126,7 +4127,6 @@
     "node_modules/@opentelemetry/sdk-trace-node": {
       "version": "1.30.1",
       "license": "Apache-2.0",
-      "peer": true,
       "dependencies": {
         "@opentelemetry/context-async-hooks": "1.30.1",
         "@opentelemetry/core": "1.30.1",
@@ -4455,7 +4455,6 @@
       "version": "8.1.0",
       "dev": true,
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@babel/core": "^7.21.3",
         "@svgr/babel-preset": "8.1.0",
@@ -4588,14 +4587,6 @@
         "node": ">=4"
       }
     },
-    "node_modules/@trysound/sax": {
-      "version": "0.2.0",
-      "dev": true,
-      "license": "ISC",
-      "engines": {
-        "node": ">=10.13.0"
-      }
-    },
     "node_modules/@types/concat-stream": {
       "version": "2.0.3",
       "dev": true,
@@ -4678,7 +4669,6 @@
       "version": "18.3.28",
       "devOptional": true,
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@types/prop-types": "*",
         "csstype": "^3.2.2"
@@ -4740,7 +4730,6 @@
       "version": "8.55.0",
       "dev": true,
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@typescript-eslint/scope-manager": "8.55.0",
         "@typescript-eslint/types": "8.55.0",
@@ -4873,7 +4862,9 @@
       }
     },
     "node_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansion": {
-      "version": "2.0.2",
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.1.0.tgz",
+      "integrity": "sha512-TN1kCZAgdgweJhWWpgKYrQaMNHcDULHkWwQIspdtjV4Y5aurRdZpjAqn6yX3FPqTA9ngHCc4hJxMAMgGfve85w==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -4881,11 +4872,13 @@
       }
     },
     "node_modules/@typescript-eslint/typescript-estree/node_modules/minimatch": {
-      "version": "9.0.5",
+      "version": "9.0.9",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.9.tgz",
+      "integrity": "sha512-OBwBN9AL4dqmETlpS2zasx+vTeWclWzkblfZk7KTA5j3jeOONz/tRCnZomUyvNg83wL5Zv9Ss6HMJXAgL8R2Yg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
-        "brace-expansion": "^2.0.1"
+        "brace-expansion": "^2.0.2"
       },
       "engines": {
         "node": ">=16 || 14 >=14.17"
@@ -4979,7 +4972,6 @@
     "node_modules/acorn": {
       "version": "8.15.0",
       "license": "MIT",
-      "peer": true,
       "bin": {
         "acorn": "bin/acorn"
       },
@@ -5022,7 +5014,6 @@
     "node_modules/algoliasearch": {
       "version": "5.48.0",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@algolia/abtesting": "1.14.0",
         "@algolia/client-abtesting": "5.48.0",
@@ -5091,7 +5082,9 @@
       }
     },
     "node_modules/anymatch/node_modules/picomatch": {
-      "version": "2.3.1",
+      "version": "2.3.2",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.2.tgz",
+      "integrity": "sha512-V7+vQEJ06Z+c5tSye8S+nHUfI51xoXIXjHQ99cQtKUkQqqO1kO/KCJUfZXuB47h/YBlDhah2H3hdUGXn8ie0oA==",
       "license": "MIT",
       "engines": {
         "node": ">=8.6"
@@ -5467,7 +5460,9 @@
       "license": "ISC"
     },
     "node_modules/brace-expansion": {
-      "version": "1.1.12",
+      "version": "1.1.14",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.14.tgz",
+      "integrity": "sha512-MWPGfDxnyzKU7rNOW9SP/c50vi3xrmrua/+6hfPbCS2ABNWfx24vPidzvC7krjU/RTo235sV776ymlsMtGKj8g==",
       "license": "MIT",
       "dependencies": {
         "balanced-match": "^1.0.0",
@@ -5501,7 +5496,6 @@
         }
       ],
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "baseline-browser-mapping": "^2.9.0",
         "caniuse-lite": "^1.0.30001759",
@@ -5962,7 +5956,6 @@
       "version": "0.5.8",
       "hasInstallScript": true,
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@contentlayer2/cli": "0.5.8",
         "@contentlayer2/client": "0.5.8",
@@ -6773,7 +6766,6 @@
       "version": "0.25.1",
       "hasInstallScript": true,
       "license": "MIT",
-      "peer": true,
       "bin": {
         "esbuild": "bin/esbuild"
       },
@@ -6829,7 +6821,6 @@
       "version": "9.39.2",
       "dev": true,
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@eslint-community/eslint-utils": "^4.8.0",
         "@eslint-community/regexpp": "^4.12.1",
@@ -6888,7 +6879,6 @@
       "version": "10.1.8",
       "dev": true,
       "license": "MIT",
-      "peer": true,
       "bin": {
         "eslint-config-prettier": "bin/cli.js"
       },
@@ -7432,7 +7422,9 @@
       }
     },
     "node_modules/flatted": {
-      "version": "3.3.3",
+      "version": "3.4.2",
+      "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.4.2.tgz",
+      "integrity": "sha512-PjDse7RzhcPkIJwy5t7KPWQSZ9cAbzQXcafsetQoD7sOJRQlGikNbx7yZp2OotDnJyrDcbyRq3Ttb18iYOqkxA==",
       "dev": true,
       "license": "ISC"
     },
@@ -7703,7 +7695,9 @@
       }
     },
     "node_modules/glob/node_modules/brace-expansion": {
-      "version": "2.0.2",
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.1.0.tgz",
+      "integrity": "sha512-TN1kCZAgdgweJhWWpgKYrQaMNHcDULHkWwQIspdtjV4Y5aurRdZpjAqn6yX3FPqTA9ngHCc4hJxMAMgGfve85w==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -7711,11 +7705,13 @@
       }
     },
     "node_modules/glob/node_modules/minimatch": {
-      "version": "9.0.5",
+      "version": "9.0.9",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.9.tgz",
+      "integrity": "sha512-OBwBN9AL4dqmETlpS2zasx+vTeWclWzkblfZk7KTA5j3jeOONz/tRCnZomUyvNg83wL5Zv9Ss6HMJXAgL8R2Yg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
-        "brace-expansion": "^2.0.1"
+        "brace-expansion": "^2.0.2"
       },
       "engines": {
         "node": ">=16 || 14 >=14.17"
@@ -8921,7 +8917,6 @@
     "node_modules/jiti": {
       "version": "1.21.7",
       "license": "MIT",
-      "peer": true,
       "bin": {
         "jiti": "bin/jiti.js"
       }
@@ -10511,7 +10506,9 @@
       }
     },
     "node_modules/micromatch/node_modules/picomatch": {
-      "version": "2.3.1",
+      "version": "2.3.2",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.2.tgz",
+      "integrity": "sha512-V7+vQEJ06Z+c5tSye8S+nHUfI51xoXIXjHQ99cQtKUkQqqO1kO/KCJUfZXuB47h/YBlDhah2H3hdUGXn8ie0oA==",
       "license": "MIT",
       "engines": {
         "node": ">=8.6"
@@ -10566,7 +10563,9 @@
       }
     },
     "node_modules/minimatch": {
-      "version": "3.1.2",
+      "version": "3.1.5",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.5.tgz",
+      "integrity": "sha512-VgjWUsnnT6n+NUk6eZq77zeFdpW2LWDzP6zFGrCbHXiYNul5Dzqk2HHQ5uFH2DNW5Xbp8+jVzaeNt94ssEEl4w==",
       "license": "ISC",
       "dependencies": {
         "brace-expansion": "^1.1.7"
@@ -10680,11 +10679,12 @@
       }
     },
     "node_modules/next": {
-      "version": "15.5.10",
+      "version": "15.5.15",
+      "resolved": "https://registry.npmjs.org/next/-/next-15.5.15.tgz",
+      "integrity": "sha512-VSqCrJwtLVGwAVE0Sb/yikrQfkwkZW9p+lL/J4+xe+G3ZA+QnWPqgcfH1tDUEuk9y+pthzzVFp4L/U8JerMfMQ==",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
-        "@next/env": "15.5.10",
+        "@next/env": "15.5.15",
         "@swc/helpers": "0.5.15",
         "caniuse-lite": "^1.0.30001579",
         "postcss": "8.4.31",
@@ -10697,14 +10697,14 @@
         "node": "^18.18.0 || ^19.8.0 || >= 20.0.0"
       },
       "optionalDependencies": {
-        "@next/swc-darwin-arm64": "15.5.7",
-        "@next/swc-darwin-x64": "15.5.7",
-        "@next/swc-linux-arm64-gnu": "15.5.7",
-        "@next/swc-linux-arm64-musl": "15.5.7",
-        "@next/swc-linux-x64-gnu": "15.5.7",
-        "@next/swc-linux-x64-musl": "15.5.7",
-        "@next/swc-win32-arm64-msvc": "15.5.7",
-        "@next/swc-win32-x64-msvc": "15.5.7",
+        "@next/swc-darwin-arm64": "15.5.15",
+        "@next/swc-darwin-x64": "15.5.15",
+        "@next/swc-linux-arm64-gnu": "15.5.15",
+        "@next/swc-linux-arm64-musl": "15.5.15",
+        "@next/swc-linux-x64-gnu": "15.5.15",
+        "@next/swc-linux-x64-musl": "15.5.15",
+        "@next/swc-win32-arm64-msvc": "15.5.15",
+        "@next/swc-win32-x64-msvc": "15.5.15",
         "sharp": "^0.34.3"
       },
       "peerDependencies": {
@@ -11265,9 +11265,10 @@
       "license": "ISC"
     },
     "node_modules/picomatch": {
-      "version": "4.0.3",
+      "version": "4.0.4",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.4.tgz",
+      "integrity": "sha512-QP88BAKvMam/3NxH6vj2o21R6MjxZUAd6nlwAS/pnGvN9IVLocLHxGYIzFhg6fUQ+5th6P4dv4eW9jX3DSIj7A==",
       "license": "MIT",
-      "peer": true,
       "engines": {
         "node": ">=12"
       },
@@ -11358,7 +11359,6 @@
         }
       ],
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "nanoid": "^3.3.11",
         "picocolors": "^1.1.1",
@@ -11496,7 +11496,6 @@
       "version": "3.8.1",
       "dev": true,
       "license": "MIT",
-      "peer": true,
       "bin": {
         "prettier": "bin/prettier.cjs"
       },
@@ -11678,7 +11677,9 @@
       }
     },
     "node_modules/qs": {
-      "version": "6.14.1",
+      "version": "6.15.0",
+      "resolved": "https://registry.npmjs.org/qs/-/qs-6.15.0.tgz",
+      "integrity": "sha512-mAZTtNCeetKMH+pSjrb76NAM8V9a05I9aBZOHztWy/UqcJdQYNsf59vrRKWnojAT9Y+GbIvoTBC++CPHqpDBhQ==",
       "license": "BSD-3-Clause",
       "dependencies": {
         "side-channel": "^1.1.0"
@@ -11718,7 +11719,6 @@
     "node_modules/react": {
       "version": "18.2.0",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "loose-envify": "^1.1.0"
       },
@@ -11729,7 +11729,6 @@
     "node_modules/react-dom": {
       "version": "18.2.0",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "loose-envify": "^1.1.0",
         "scheduler": "^0.23.0"
@@ -11814,7 +11813,9 @@
       }
     },
     "node_modules/readdirp/node_modules/picomatch": {
-      "version": "2.3.1",
+      "version": "2.3.2",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.2.tgz",
+      "integrity": "sha512-V7+vQEJ06Z+c5tSye8S+nHUfI51xoXIXjHQ99cQtKUkQqqO1kO/KCJUfZXuB47h/YBlDhah2H3hdUGXn8ie0oA==",
       "license": "MIT",
       "engines": {
         "node": ">=8.6"
@@ -12771,7 +12772,9 @@
       "license": "MIT"
     },
     "node_modules/sax": {
-      "version": "1.4.4",
+      "version": "1.6.0",
+      "resolved": "https://registry.npmjs.org/sax/-/sax-1.6.0.tgz",
+      "integrity": "sha512-6R3J5M4AcbtLUdZmRv2SygeVaM7IhrLXu9BmnOGmmACak8fiUtOsYNWUS4uK7upbmHIBbLBeFeI//477BKLBzA==",
       "license": "BlueOak-1.0.0",
       "engines": {
         "node": ">=11.0.0"
@@ -13496,17 +13499,19 @@
       "license": "MIT"
     },
     "node_modules/svgo": {
-      "version": "3.3.2",
+      "version": "3.3.3",
+      "resolved": "https://registry.npmjs.org/svgo/-/svgo-3.3.3.tgz",
+      "integrity": "sha512-+wn7I4p7YgJhHs38k2TNjy1vCfPIfLIJWR5MnCStsN8WuuTcBnRKcMHQLMM2ijxGZmDoZwNv8ipl5aTTen62ng==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "@trysound/sax": "0.2.0",
         "commander": "^7.2.0",
         "css-select": "^5.1.0",
         "css-tree": "^2.3.1",
         "css-what": "^6.1.0",
         "csso": "^5.0.5",
-        "picocolors": "^1.0.0"
+        "picocolors": "^1.0.0",
+        "sax": "^1.5.0"
       },
       "bin": {
         "svgo": "bin/svgo"
@@ -13547,7 +13552,6 @@
     "node_modules/tailwindcss": {
       "version": "3.4.19",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@alloc/quick-lru": "^5.2.0",
         "arg": "^5.0.2",
@@ -13723,8 +13727,7 @@
     },
     "node_modules/tslib": {
       "version": "2.8.1",
-      "license": "0BSD",
-      "peer": true
+      "license": "0BSD"
     },
     "node_modules/typanion": {
       "version": "3.14.0",
@@ -13833,7 +13836,6 @@
       "version": "5.9.3",
       "dev": true,
       "license": "Apache-2.0",
-      "peer": true,
       "bin": {
         "tsc": "bin/tsc",
         "tsserver": "bin/tsserver"
@@ -14625,7 +14627,9 @@
       "license": "ISC"
     },
     "node_modules/yaml": {
-      "version": "2.8.2",
+      "version": "2.8.3",
+      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.3.tgz",
+      "integrity": "sha512-AvbaCLOO2Otw/lW5bmh9d/WEdcDFdQp2Z2ZUH3pX9U2ihyUY0nvLv7J6TrWowklRGPYbB/IuIMfYgxaCPg5Bpg==",
       "license": "ISC",
       "bin": {
         "yaml": "bin.mjs"
diff --git a/package.json b/package.json
index 1400193..233791a 100644
--- a/package.json
+++ b/package.json
@@ -22,7 +22,7 @@
     "github-slugger": "^2.0.0",
     "gray-matter": "^4.0.2",
     "image-size": "1.0.0",
-    "next": "15.5.10",
+    "next": "15.5.15",
     "next-contentlayer2": "0.5.8",
     "next-themes": "^0.3.0",
     "pliny": "0.4.1",
diff --git a/public/static/images/Logos/2026-Sitecore_MVP_Technology.png b/public/static/images/Logos/2026-Sitecore_MVP_Technology.png
new file mode 100644
index 0000000..a5e592f
Binary files /dev/null and b/public/static/images/Logos/2026-Sitecore_MVP_Technology.png differ