A small, shared home for the Merchandising & Search team. It answers three everyday questions:
- A search looks wrong — what do I do?
- Where do I write it down so it doesn't get lost?
- How do I get real evidence about what shoppers are doing?
That's the whole first release. We'll add more only when a real question asks for it.
| Page | For |
|---|---|
| Start Here | The 2-minute orientation. Read this first. |
| Who you're serving | The big idea: Insight is configuration-driven, not persona-driven. Short and forwardable — read this. |
| Working a logged-in account | The seven Experience Profiles and the configs that masquerade as search bugs. |
| When a search looks wrong | A step-by-step walkthrough when results look off. |
| Log a search problem | How to record a problem so someone can pick it up. |
| Ask the Discovery agent | Get search evidence in plain English from the team's AI agent. |
This is the source of truth for the hub's content. The pages here are written to be published into Microsoft Teams / SharePoint, where the team actually reads them. This repo is where we draft and keep the master copy; SharePoint is where people go.
- To stand up the Teams + SharePoint side, follow SETUP-M365.md.
- When you edit a page here, re-publish it in SharePoint (the setup guide explains how).
This hub is deliberately non-technical. The heavy lifting lives elsewhere and we just point to it:
- The Discovery Intelligence agent (search evidence from Adobe Analytics + LogRocket) lives in the Analyst Workbench repo — see Ask the Discovery agent.
- The Analyst Workbench and fusion-mcp server are the analytics engine behind the scenes. We link to them; we don't duplicate or move them.
Resist the urge to build a big wiki. Add a page only when someone actually asks the same question twice. Keep every new page in plain language a merchandiser would use.