Add Mixpanel to Snowplow migration guide

[johnmicahreid]

Summary

• Adds new migration guide at /docs/resources/migration-guides/mixpanel/ to help technical implementers migrate from Mixpanel to Snowplow
• Follows the structure and style of existing Segment and Google Analytics migration guides
• Includes Mixpanel-specific content covering unique features:
  • User profiles vs. events architecture and migration strategy
  • Super properties pattern conversion to global context entities
  • Group analytics mapping to Snowplow group entities
  • Identity management (identify(), alias(), reset())
  • Profile manipulation methods (.people.set(), .people.increment()) and warehouse alternatives
• Contains comprehensive tracking comparison table mapping all Mixpanel API calls to Snowplow equivalents
• Includes 3-phase migration approach (Assess/plan, Implement/validate, Cutover/finalize)
• All links follow documentation standards (end with /index.md)
• 222 lines, professional technical tone consistent with other guides

Test plan

• Run yarn start and verify the page renders at /resources/migration-guides/mixpanel/
• Verify all internal links work correctly (especially fundamentals links)
• Check tables are properly formatted
• Verify code blocks have correct syntax highlighting
• Confirm frontmatter displays properly (title, description, keywords)
• Check sidebar position (should appear between Segment and Google Analytics guides)
• Verify heading hierarchy (only H2 and H3 used)
• Run yarn build to ensure no build errors

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for snowplow-docs ready!

Name	Link
🔨 Latest commit	a2e8084
🔍 Latest deploy log	https://app.netlify.com/projects/snowplow-docs/deploys/69613263f4d08d000819da05
😎 Deploy Preview	https://deploy-preview-1573--snowplow-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 18 (no change from production) Accessibility: 91 (no change from production) Best Practices: 92 (no change from production) SEO: 95 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Missing SEO metadata

The following markdown files are missing required metadata fields:

• docs/resources/migration-guides/mixpanel/index.md: missing fields: sidebar_label

Required fields

The file metadata is important for SEO and marketing. All markdown files, except for those with filenames starting with _, should include:

• title: Full, descriptive page title
• sidebar_label: Short title for navigation sidebar (can be the same as the main title)
• description: One to two sentences summarizing the page contents
• keywords: Array of marketing/SEO keywords

Please add the missing metadata.

[claude]

Writing Quality Review

Thank you for this comprehensive migration guide! The content is well-structured and follows most of the style guide. Here are some suggestions to align it fully with the documentation standards:

Style Guide Issues

Filler words to remove (line references approximate):

• Line 13: "it's important to understand" → "Understanding"
• Line 13: "how Snowplow structures events differently from Mixpanel" could be "how Snowplow structures events" ("differently from Mixpanel" is implied by context)
• Line 40: "This event would be loaded" → "This event loads" (active voice, present tense)
• Line 41: "The exact table structure depends" → Consider "The table structure depends" (remove "exact" as filler)
• Line 88: "In Mixpanel's warehouse export" → "In Mixpanel warehouse exports" (more general)
• Line 151: "Using a Tracking Plan is optional" → "Tracking Plans are optional"

Tone and word choice:

• Line 17, 30: "Mixpanel's core method" → "Mixpanel tracks user behavior with" (more direct)
• Line 125: "Schematic event specification isn't optional" → "Event specification is required" (positive framing is clearer)
• Line 145: "We recommend using" → "Use" (avoid "we", be more direct per style guide)
• Line 153: "Your existing Mixpanel Tracking Plans will serve as the foundation" → "Use your existing Mixpanel Tracking Plans as the foundation" (imperative voice)
• Line 155: "Before migration, we advise auditing" → "Before migration, audit" (remove "we advise")

Contractions consistency:
The style guide says "contractions are fine" but this guide uses very few. Consider whether "you'll", "it's" should be expanded to "you will", "it is" for consistency with the more formal sections, or add more contractions for a conversational tone. Current usage is inconsistent (line 13 has "you'll", line 155 has "we advise").

List punctuation:

• Lines 189-197: Check if items should have periods since some contain multiple clauses

Verb tense:

• Line 196: "You'll need to translate" → Consider "Translate" (imperative, present tense)
• Generally good on staying present tense

Structural Suggestions

Preceding prose before headings:
All sections properly introduced ✅

Admonition usage:
The info admonitions at lines 137-139 and 171-173 should have custom headings per style guide. They currently have headings, but verify the format matches Docusaurus admonition syntax.

Content Accuracy

Terminology check:

• "entity" vs "context" - ✅ correctly uses "entity" throughout
• "self-describing event" - ✅ used correctly
• Capitalization of products/features - ✅ appears correct throughout

Link validation needed:
Verify these links resolve (they appear correct but should be tested):

• Line 18: /docs/fundamentals/events/index.md
• Line 19: /docs/fundamentals/entities/index.md
• Line 44: /docs/sources/web-trackers/tracking-events/ecommerce/index.md
• Others throughout

Minor Polish

• Line 146: "three phases" ✅ correctly spells out single-digit number
• Line 182: "three main tasks" ✅ correct
• Consider whether the dual repetition of the MCP server info box (lines 137-139 and 171-173) is necessary or if one reference would suffice

Overall Assessment

This is high-quality documentation that follows most style conventions. The main areas for improvement are:

1. Removing filler/marketing language ("important to understand", "we recommend", "we advise")
2. Making voice more consistently imperative
3. Verifying admonition syntax
4. Checking contraction consistency

The technical content is accurate and comprehensive. Nice work on the detailed tracking comparison table and the clear three-phase migration approach!