Skip to content

content: Legal IQ positioning on Semantic Search walkthrough landing#54

Merged
spaarke-dev merged 1 commit into
mainfrom
content/legal-iq-positioning
May 18, 2026
Merged

content: Legal IQ positioning on Semantic Search walkthrough landing#54
spaarke-dev merged 1 commit into
mainfrom
content/legal-iq-positioning

Conversation

@spaarke-dev

Copy link
Copy Markdown
Owner

Summary

Replaces tech-stack name-drop with category positioning on the walkthrough landing page lede.

Before:

…powered by SharePoint Embedded and Azure AI Search.

After:

…one module of the Spaarke Legal IQ stack.

Why

  • Positions Spaarke as a category (Legal IQ), not a feature on top of named Microsoft components.
  • Builds the "Legal IQ stack" term Spaarke has been investing in across content (the-iq-stack article, the walkthrough's own intro card, etc.).
  • The intro card on the tour already carries the M365 framing ("lives in your Microsoft 365 tenant — your data, your governance, your existing permissions"), so dropping M365 from the landing copy avoids duplication.

Test plan

  • After deploy, /semantic-search-walkthrough shows the updated lede.
  • Walkthrough itself (/tour/semantic-search-walkthrough) unchanged.

🤖 Generated with Claude Code

…lkthrough landing

The landing-page lede mentioned 'SharePoint Embedded and Azure AI
Search' as the underlying tech. Replacing with 'one module of the
Spaarke Legal IQ stack' to:

- Position Spaarke as a category, not a feature stack
- Build the 'Legal IQ' term Spaarke has been investing in across
  recent content (the-iq-stack article, intro card on this same
  walkthrough, etc.)
- Avoid double-mentioning Microsoft 365 (the intro card on the tour
  itself already says 'lives in your Microsoft 365 tenant — your
  data, your governance, your existing permissions')

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@spaarke-dev spaarke-dev merged commit 3382988 into main May 18, 2026
@spaarke-dev spaarke-dev deleted the content/legal-iq-positioning branch May 18, 2026 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant