From bd27309a48f0ca0c035f37bd0ab93ab7c125c87c Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 10:32:46 -0500 Subject: [PATCH 001/153] Create benchmarks.mdx benchmarks test --- .../guides/guides-by-use-case/benchmarks.mdx | 267 ++++++++++++++++++ 1 file changed, 267 insertions(+) create mode 100644 pages/guides/guides-by-use-case/benchmarks.mdx diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx new file mode 100644 index 0000000000..de36fbbbba --- /dev/null +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -0,0 +1,267 @@ +'use client'; + +import React from "react"; +import { ExternalLink, LibraryBig, LineChart, Layers, Sparkles } from "lucide-react"; +import { Tabs, TabsList, TabsTrigger, TabsContent } from "@/components/ui/tabs"; +import { Card, CardContent } from "@/components/ui/card"; +import { Button } from "@/components/ui/button"; + +/** + * MDX-compatible version (no TypeScript prop types, client-ready) + * Drop this into a .mdx file in your docs app. If your UI kit + * components are Client Components, the 'use client' pragma above + * ensures interactivity (Tabs, Buttons, etc.). + */ + +// --- Helper components --- +const SectionHeader = ({ id, eyebrow, title, blurb }) => ( +
+
{eyebrow}
+

{title}

+

{blurb}

+
+); + +const Pill = ({ children }) => ( + {children} +); + +const LinkButton = ({ href, children }) => ( + + {children} + +); + +const GuideCard = ({ icon, title, caption, href, tag }) => ( + + +
+
{icon}
+
+
+

{title}

+ {tag ? {tag} : null} +
+

{caption}

+
+ Open +
+
+
+ + +); + +const ListItem = ({ title, href, caption }) => ( +
  • +
    +
    + + {title} + +

    {caption}

    +
    + +
    +
    • +); + +const TOC = () => ( + +); + +// --- Data --- +const DATA = { + benchmarks: [ + { + title: "Product Analytics Benchmarks", + caption: + "Explore conversion, retention, and engagement baselines across products to set realistic targets and spot outliers.", + href: "https://mixpanel.com/benchmarks/", + tag: "Live", + icon: , + }, + ], + industry: [ + { + title: "2025 Fintech Benchmarks Report", + caption: "Industry-specific performance norms and insights tailored for fintech teams.", + href: "https://mixpanel.com/m/benchmarks-report-2025-fintech/", + tag: "Report", + icon: , + }, + { + title: "2025 Media & Entertainment Benchmarks", + caption: "Benchmarks for audience growth, engagement, and retention across media & entertainment.", + href: "https://mixpanel.com/m/benchmarks-report-2025-media-entertainment/", + tag: "Report", + icon: , + }, + ], + maturity: [ + { + title: "Get Started: Product Analytics Strategy", + caption: "Assess where you are on the analytics maturity curve and what to do to level up next.", + href: "https://mixpanel.com/content/product-analytics-strategy/get-started/", + tag: "Guide", + icon: , + }, + ], +}; + +export default function GuidesBenchmarksMock() { + return ( +
    + {/* Page header */} +
    +
    Guides Mockup
    +

    Benchmarks & Analytics Maturity

    +

    + A visual, link-first explainer page for Mixpanel Guides that pulls together our benchmarks and maturity resources. Use this mockup to test layout, tone, and information density before we ship. +

    +
    + + {/* Top controls */} +
    + + +
    + {/* Layout switcher */} + +
    +
    Choose a layout for the cards:
    + + Cards + List + Compact + +
    + + {/* --- Benchmarks --- */} +
    + + + +
    + {DATA.benchmarks.map((c) => ( + + ))} +
    +     + +
      + {DATA.benchmarks.map((c) => ( + + ))} +
    +     + +
    + {DATA.benchmarks.map((c) => ( + + {c.title} + + ))} +
    +     +
    + + {/* --- Benchmarks by Industry --- */} +
    + + + +
    + {DATA.industry.map((c) => ( + + ))} +
    +     + +
      + {DATA.industry.map((c) => ( + + ))} +
    +     + +
    + {DATA.industry.map((c) => ( + + {c.title} + + ))} +
    +     +
    + + {/* --- Analytics Maturity --- */} +
    + + + +
    + {DATA.maturity.map((c) => ( + + ))} +
    +     + +
      + {DATA.maturity.map((c) => ( + + ))} +
    +     + +
    + {DATA.maturity.map((c) => ( + + {c.title} + + ))} +
    +     +
    +     + + {/* Footer CTA to test engagement */} +
    +
    +
    Prototype
    +

    Does this layout work for your team? Share feedback and we’ll iterate.

    +
    + +
    +
    +
    +
    + ); +} From d472adb2ace8064ba70c25d4b5e289d40e276859 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 10:42:32 -0500 Subject: [PATCH 002/153] Update benchmarks.mdx button test --- .../guides/guides-by-use-case/benchmarks.mdx | 277 ++---------------- 1 file changed, 18 insertions(+), 259 deletions(-) diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx index de36fbbbba..c7557930f1 100644 --- a/pages/guides/guides-by-use-case/benchmarks.mdx +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -1,267 +1,26 @@ -'use client'; +# Benchmarks & Analytics Maturity +Description -import React from "react"; -import { ExternalLink, LibraryBig, LineChart, Layers, Sparkles } from "lucide-react"; -import { Tabs, TabsList, TabsTrigger, TabsContent } from "@/components/ui/tabs"; -import { Card, CardContent } from "@/components/ui/card"; -import { Button } from "@/components/ui/button"; +## Benchmarks +See product performance baselines across conversion, retention, and engagement. Use these as north stars to calibrate goals and identify outliers. -/** - * MDX-compatible version (no TypeScript prop types, client-ready) - * Drop this into a .mdx file in your docs app. If your UI kit - * components are Client Components, the 'use client' pragma above - * ensures interactivity (Tabs, Buttons, etc.). - */ -// --- Helper components --- -const SectionHeader = ({ id, eyebrow, title, blurb }) => ( -
    -
    {eyebrow}
    -

    {title}

    -

    {blurb}

    -
    -); -const Pill = ({ children }) => ( - {children} -); +
    -const LinkButton = ({ href, children }) => ( - - {children} - -); +
    + +

    -const GuideCard = ({ icon, title, caption, href, tag }) => ( - - -

    -
    {icon}
    -
    -
    -

    {title}

    - {tag ? {tag} : null} -
    -

    {caption}

    -
    - Open -
    -
    -
    - - -); -const ListItem = ({ title, href, caption }) => ( -
  • -
    -
    - - {title} - -

    {caption}

    -
    - -
    -
    • -); +

    +

    + +
    -const TOC = () => ( - -); - -// --- Data --- -const DATA = { - benchmarks: [ - { - title: "Product Analytics Benchmarks", - caption: - "Explore conversion, retention, and engagement baselines across products to set realistic targets and spot outliers.", - href: "https://mixpanel.com/benchmarks/", - tag: "Live", - icon: , - }, - ], - industry: [ - { - title: "2025 Fintech Benchmarks Report", - caption: "Industry-specific performance norms and insights tailored for fintech teams.", - href: "https://mixpanel.com/m/benchmarks-report-2025-fintech/", - tag: "Report", - icon: , - }, - { - title: "2025 Media & Entertainment Benchmarks", - caption: "Benchmarks for audience growth, engagement, and retention across media & entertainment.", - href: "https://mixpanel.com/m/benchmarks-report-2025-media-entertainment/", - tag: "Report", - icon: , - }, - ], - maturity: [ - { - title: "Get Started: Product Analytics Strategy", - caption: "Assess where you are on the analytics maturity curve and what to do to level up next.", - href: "https://mixpanel.com/content/product-analytics-strategy/get-started/", - tag: "Guide", - icon: , - }, - ], -}; - -export default function GuidesBenchmarksMock() { - return ( -
    - {/* Page header */} -
    -
    Guides Mockup
    -

    Benchmarks & Analytics Maturity

    -

    - A visual, link-first explainer page for Mixpanel Guides that pulls together our benchmarks and maturity resources. Use this mockup to test layout, tone, and information density before we ship. -

    -
    - - {/* Top controls */} -
    - - -
    - {/* Layout switcher */} - -
    -
    Choose a layout for the cards:
    - - Cards - List - Compact - -
    - - {/* --- Benchmarks --- */} -
    - - - -
    - {DATA.benchmarks.map((c) => ( - - ))} -
    -     - -
      - {DATA.benchmarks.map((c) => ( - - ))} -
    -     - -
    - {DATA.benchmarks.map((c) => ( - - {c.title} - - ))} -
    -     -
    - - {/* --- Benchmarks by Industry --- */} -
    - - - -
    - {DATA.industry.map((c) => ( - - ))} -
    -     - -
      - {DATA.industry.map((c) => ( - - ))} -
    -     - -
    - {DATA.industry.map((c) => ( - - {c.title} - - ))} -
    -     -
    - - {/* --- Analytics Maturity --- */} -
    - - - -
    - {DATA.maturity.map((c) => ( - - ))} -
    -     - -
      - {DATA.maturity.map((c) => ( - - ))} -
    -     - -
    - {DATA.maturity.map((c) => ( - - {c.title} - - ))} -
    -     -
    -     - - {/* Footer CTA to test engagement */} -
    -
    -
    Prototype
    -

    Does this layout work for your team? Share feedback and we’ll iterate.

    -
    - -
    -
    -
    -
    - ); -} +
    +

    +

    From f9dd912150830345868c7ae807025be4b93ec0ea Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 10:50:42 -0500 Subject: [PATCH 003/153] Update benchmarks.mdx --- .../guides/guides-by-use-case/benchmarks.mdx | 42 ++++++++++++++----- 1 file changed, 32 insertions(+), 10 deletions(-) diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx index c7557930f1..4bb5aec6bd 100644 --- a/pages/guides/guides-by-use-case/benchmarks.mdx +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -1,26 +1,48 @@ -# Benchmarks & Analytics Maturity -Description +# Identify Users -## Benchmarks -See product performance baselines across conversion, retention, and engagement. Use these as north stars to calibrate goals and identify outliers. +import { Tabs } from "nextra/components"; +import ExtendedButton from "/components/ExtendedButton/ExtendedButton"; +import ExtendedTabs from "/components/ExtendedTabs/ExtendedTabs"; +import { dataItems } from "/utils/constants"; + +## Overview + +This step introduces the `identify` method, which allows you to see which users triggered each event in Mixpanel. + +It also introduces the `people.set` method, which allows you to define the attributes of each user. + + + +{/* Next Section */} + + + +
    +

    - +

    + Next: Track Events +

    - - -

    + Once you've implemented `identify`, it's time to track what your users are + doing in your product. +







    + + + + From 75736833a94e0cc5b831278d44703c67662e7a7c Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 10:53:33 -0500 Subject: [PATCH 004/153] Update benchmarks.mdx --- .../guides/guides-by-use-case/benchmarks.mdx | 49 +------------------ 1 file changed, 1 insertion(+), 48 deletions(-) diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx index 4bb5aec6bd..83c831f0b0 100644 --- a/pages/guides/guides-by-use-case/benchmarks.mdx +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -1,48 +1 @@ -# Identify Users - -import { Tabs } from "nextra/components"; - -import ExtendedButton from "/components/ExtendedButton/ExtendedButton"; -import ExtendedTabs from "/components/ExtendedTabs/ExtendedTabs"; - -import { dataItems } from "/utils/constants"; - -## Overview - -This step introduces the `identify` method, which allows you to see which users triggered each event in Mixpanel. - -It also introduces the `people.set` method, which allows you to define the attributes of each user. - - - -{/* Next Section */} - - - -
    -

    - -
    - -
    -

    - Next: Track Events -

    -

    - Once you've implemented `identify`, it's time to track what your users are - doing in your product. -

    -

    - -
    - -
    -

    -

    - - - - +# test From a7bb2eaec79db42b9e6b57f776950eb3a8e3f280 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 11:03:07 -0500 Subject: [PATCH 005/153] Update benchmarks.mdx --- .../guides/guides-by-use-case/benchmarks.mdx | 26 ++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx index 83c831f0b0..6345cf1871 100644 --- a/pages/guides/guides-by-use-case/benchmarks.mdx +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -1 +1,25 @@ -# test +import { Cards } from 'nextra/components' + +# Benchmarks & Analytics Maturity + +## Benchmarks +See product performance baselines across conversion, retention, and engagement. Use these as north stars to calibrate goals and identify outliers. + + + + + +## Benchmarks by Industry +Drill into industry-specific norms to set context-rich targets. Start with our latest Fintech and Media & Entertainment reports. + + + + + + +## Analytics Maturity +Assess where your org sits on the analytics maturity curve and chart the next moves to unlock impact. + + + + From 1c6852122d8f6b4408f38e0c07dd42685f3a2eea Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 11:12:59 -0500 Subject: [PATCH 006/153] Update benchmarks.mdx add description after heading --- pages/guides/guides-by-use-case/benchmarks.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx index 6345cf1871..97bdc5ef70 100644 --- a/pages/guides/guides-by-use-case/benchmarks.mdx +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -1,6 +1,7 @@ import { Cards } from 'nextra/components' # Benchmarks & Analytics Maturity +Understand performance benchmarks and assess your organization’s analytics maturity. Whether you’re setting goals, comparing performance against peers, or looking for ways to advance your analytics practice, these resources will help guide your next steps. ## Benchmarks See product performance baselines across conversion, retention, and engagement. Use these as north stars to calibrate goals and identify outliers. @@ -13,13 +14,13 @@ See product performance baselines across conversion, retention, and engagement. Drill into industry-specific norms to set context-rich targets. Start with our latest Fintech and Media & Entertainment reports. - - + + ## Analytics Maturity Assess where your org sits on the analytics maturity curve and chart the next moves to unlock impact. - + From 3d1a10631d8788a58d16f4ebf7b5d73076555550 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Fri, 3 Oct 2025 11:21:21 -0500 Subject: [PATCH 007/153] Update benchmarks.mdx open links in new tab --- pages/guides/guides-by-use-case/benchmarks.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/guides/guides-by-use-case/benchmarks.mdx b/pages/guides/guides-by-use-case/benchmarks.mdx index 97bdc5ef70..f373a6e18b 100644 --- a/pages/guides/guides-by-use-case/benchmarks.mdx +++ b/pages/guides/guides-by-use-case/benchmarks.mdx @@ -7,20 +7,20 @@ Understand performance benchmarks and assess your organization’s analytics mat See product performance baselines across conversion, retention, and engagement. Use these as north stars to calibrate goals and identify outliers. - + ## Benchmarks by Industry Drill into industry-specific norms to set context-rich targets. Start with our latest Fintech and Media & Entertainment reports. - - + + ## Analytics Maturity Assess where your org sits on the analytics maturity curve and chart the next moves to unlock impact. - + From bc4d7ef8b252ab1138bdaa0053228b35df34cf8e Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Mon, 6 Oct 2025 16:41:33 -0500 Subject: [PATCH 008/153] Create oada.mdx video test --- pages/guides/guides-by-use-case/oada.mdx | 48 ++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 pages/guides/guides-by-use-case/oada.mdx diff --git a/pages/guides/guides-by-use-case/oada.mdx b/pages/guides/guides-by-use-case/oada.mdx new file mode 100644 index 0000000000..0085e6a9ef --- /dev/null +++ b/pages/guides/guides-by-use-case/oada.mdx @@ -0,0 +1,48 @@ +# Mixpanel Overview +Mixpanel helps product teams see what’s happening, understand why, decide what to do next, and measure impact—fast. This continuous cycle is the **OADA loop**: Observe → Analyze → Decide → Act. + +
    +
    + {/* Left: video with a min width so it wraps when narrow */} +
    +
    + +

    +
    From 2d59c0222032eb01c1dd1c79f870a740728b7753 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Mon, 6 Oct 2025 16:50:29 -0500 Subject: [PATCH 010/153] Update oada.mdx --- pages/guides/guides-by-use-case/oada.mdx | 74 +++++++++++++++--------- 1 file changed, 48 insertions(+), 26 deletions(-) diff --git a/pages/guides/guides-by-use-case/oada.mdx b/pages/guides/guides-by-use-case/oada.mdx index 5b68ec112b..8557f45d60 100644 --- a/pages/guides/guides-by-use-case/oada.mdx +++ b/pages/guides/guides-by-use-case/oada.mdx @@ -1,29 +1,51 @@ # Mixpanel Overview -Mixpanel helps product teams see what’s happening, understand why, decide what to do next, and measure impact—fast. This continuous cycle is the **OADA loop**: Observe → Analyze → Decide → Act. +Mixpanel helps product teams **see what’s happening**, **understand why**, **decide what to do next**, and **measure impact**—fast. This continuous cycle is the **OADA loop**: Observe → Analyze → Decide → Act.

    -
    -

    - -

    -
    +
    +
    + {/* Left: video with a min width so it wraps when narrow */} +
    +
    + +
    + +--- + +## The Continuous Innovation Loop (OADA) + +The OADA loop is the foundation of how Mixpanel supports better, faster product decisions. +Each phase represents a step teams take to close the feedback loop between data and action. + +| 👀 **Observe** | 📊 **Analyze** | 💡 **Decide** | 🚀 **Act** | +|---|---|---|---| +| Track the right events and understand user behavior. | Explore funnels, retention, and trends to find what drives engagement. | Align on opportunities using dashboards and metrics. | Launch experiments and measure impact to close the loop. | + +**Learn more:** [Go deeper on the OADA Loop →](/guides/mixpanel-oada-loop) + +--- + +## Mixpanel Features That Power the Loop + +- **Analysis:** Funnels, Flows, Insights, Retention +- **Experimentation:** Feature Flags, A/B Testing +- **Session Replay:** Combine quantitative and qualitative insights +- **Metric Trees:** Connect your metrics to understand cause and effect + +--- + +## Event Data Model + +Mixpanel’s **event-based data model** captures every user interaction—allowing you to measure, segment, and iterate quickly. + +- 📖 [How Mixpanel structures event data →](https://docs.mixpanel.com/docs/) + +--- + +## Keep Learning + +Keep building your Mixpanel expertise with these resources designed to help you learn, connect, and put insights into action. + +| Resource | Description | Link | +|-----------|--------------|------| +| **Community** | Connect with other Mixpanel users, share ideas, and learn how peers are tackling similar challenges. | [Open →](https://community.mixpanel.com/) | +| **Developer Docs** | Build and extend Mixpanel with SDKs, APIs, and advanced implementation guides. | [Open →](https://developer.mixpanel.com/reference/overview) | +| **Docs** | Explore product capabilities, setup guides, and detailed feature references. | [Open →](https://docs.mixpanel.com/) | +| **Events** | Join live sessions and webinars to explore new features, use cases, and expert-led best practices. | [Open →](https://mixpanel.com/events) | +| **Guides** | Apply Mixpanel best practices to real-world workflows and use cases. | 📍 You are here | +| **Mixpanel University** | Follow guided learning paths to validate your skills and earn certifications. | [Open →](https://mixpanel.com/university/) | + +**Closing thought:** Wherever you are in your Mixpanel journey, these resources will help you keep learning, stay connected, and keep improving. From 017ccca508d629ca791b18a340fbb251696057ab Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Wed, 8 Oct 2025 14:47:28 -0500 Subject: [PATCH 038/153] Update oada-loop.mdx --- pages/guides/guides-by-use-case/oada-loop.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/guides/guides-by-use-case/oada-loop.mdx b/pages/guides/guides-by-use-case/oada-loop.mdx index e9fb39dac5..4a8c07da10 100644 --- a/pages/guides/guides-by-use-case/oada-loop.mdx +++ b/pages/guides/guides-by-use-case/oada-loop.mdx @@ -2,7 +2,7 @@ The **Observe → Analyze → Decide → Act (OADA)** loop is the framework behind how great teams use Mixpanel to continuously innovate. Each phase represents a key moment in the product decision cycle—and Mixpanel provides the tools to complete that loop faster with every iteration. -**Why it matters:** Teams that move through the loop quickly learn what’s working, align faster, and deliver more impactful product improvements. +> **Why it matters:** Teams that move through the loop quickly learn what’s working, align faster, and deliver more impactful product improvements. --- From 961e46b727d78e81e22ff29ee052a3999ce15bba Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Wed, 8 Oct 2025 14:51:11 -0500 Subject: [PATCH 039/153] Update oada-loop.mdx From 0f18166f34844720d25b37c1e4501fcc156cf382 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Wed, 8 Oct 2025 14:54:43 -0500 Subject: [PATCH 040/153] Update mixpanel-lp.mdx --- .../guides/guides-by-use-case/mixpanel-lp.mdx | 63 ++++++++++++++----- 1 file changed, 49 insertions(+), 14 deletions(-) diff --git a/pages/guides/guides-by-use-case/mixpanel-lp.mdx b/pages/guides/guides-by-use-case/mixpanel-lp.mdx index a52feac731..7a5693d652 100644 --- a/pages/guides/guides-by-use-case/mixpanel-lp.mdx +++ b/pages/guides/guides-by-use-case/mixpanel-lp.mdx @@ -9,24 +9,59 @@ At its core, Mixpanel supports a **continuous innovation loop**—helping you ob ## See Mixpanel in Action - -
    - -
    +

    +
    +
    + {/* Left: video with a min width so it wraps when narrow */} +
    +
    + + +Full Page + + + + +Popup + + + + + From 759d678793d273c460db930ff0298e91a1e27589 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Thu, 9 Oct 2025 13:27:17 -0500 Subject: [PATCH 058/153] Update navattic.mdx --- pages/guides/guides-by-use-case/navattic.mdx | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/pages/guides/guides-by-use-case/navattic.mdx b/pages/guides/guides-by-use-case/navattic.mdx index 66e20f9c36..c25af6c4fd 100644 --- a/pages/guides/guides-by-use-case/navattic.mdx +++ b/pages/guides/guides-by-use-case/navattic.mdx @@ -5,13 +5,3 @@ Inline code Full Page - - -Popup - - - - - From 559fa184193005d85fca3a03d17aaf6cfee93ce6 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Thu, 9 Oct 2025 13:32:47 -0500 Subject: [PATCH 059/153] Update navattic.mdx --- pages/guides/guides-by-use-case/navattic.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/pages/guides/guides-by-use-case/navattic.mdx b/pages/guides/guides-by-use-case/navattic.mdx index c25af6c4fd..a77bc2f345 100644 --- a/pages/guides/guides-by-use-case/navattic.mdx +++ b/pages/guides/guides-by-use-case/navattic.mdx @@ -1,7 +1,3 @@ Inline code - -Full Page - - From eb2cce824bf611043db239c49c1b11c492dd6dc0 Mon Sep 17 00:00:00 2001 From: amymadden-bit Date: Thu, 9 Oct 2025 13:52:16 -0500 Subject: [PATCH 060/153] Update navattic.mdx --- pages/guides/guides-by-use-case/navattic.mdx | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/pages/guides/guides-by-use-case/navattic.mdx b/pages/guides/guides-by-use-case/navattic.mdx index a77bc2f345..58fca99e91 100644 --- a/pages/guides/guides-by-use-case/navattic.mdx +++ b/pages/guides/guides-by-use-case/navattic.mdx @@ -1,3 +1,11 @@ Inline code - +
    +