docs: replace evaluation loop image with LoopDiagram component

[Lotte-Verheyden]

Replaces the static continuous-evaluation-loop image on the evaluation core concepts page with the interactive <LoopDiagram /> component used in the academy. This gives the docs page the same loop graph, with Online/Offline labels, per-stage meta tags, cycling activity indicator, and links into the academy stages.

Greptile Summary

Replaces the static continuous-evaluation-loop.png image (wrapped in a <Frame>) with the interactive <LoopDiagram /> component on the evaluation core-concepts page.

• LoopDiagram is already registered globally in mdx-components.tsx, so no import is needed in the MDX file — the component will resolve correctly.
• The component renders an animated, responsive loop diagram with Online/Offline labels, per-stage meta tags, a cycling activity indicator, and links to the corresponding academy stages.

Confidence Score: 5/5

Safe to merge — single-line docs change swapping a static image for an already-registered interactive component.

The only change is removing 4 lines (a <Frame> wrapping a PNG) and adding <LoopDiagram />. The component is globally registered in mdx-components.tsx so it resolves without an explicit import, it is already live on overview.mdx and multiple academy pages, and no logic or configuration is affected.

No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    subgraph Online["Online Evaluation"]
        T["Trace\n(traces · sessions · agents · prompts)"]
        M["Monitor\n(dashboards · LLM-as-judge · feedback)"]
    end
    subgraph Offline["Offline Evaluation"]
        D["Build Datasets\n(datasets · features-as-tests)"]
        E["Experiment\n(prompts · models · code variants)"]
        EV["Evaluate\n(judges · custom evals · annotation)"]
    end
    T --> M --> D --> E --> EV
    EV -- Deploy --> T

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart LR
    subgraph Online["Online Evaluation"]
        T["Trace\n(traces · sessions · agents · prompts)"]
        M["Monitor\n(dashboards · LLM-as-judge · feedback)"]
    end
    subgraph Offline["Offline Evaluation"]
        D["Build Datasets\n(datasets · features-as-tests)"]
        E["Experiment\n(prompts · models · code variants)"]
        EV["Evaluate\n(judges · custom evals · annotation)"]
    end
    T --> M --> D --> E --> EV
    EV -- Deploy --> T

Loading

_{Reviews (1): Last reviewed commit: "docs: replace evaluation loop image with..." | Re-trigger Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-docs	Ready	Preview, Comment	Jul 4, 2026 2:19pm

[github-actions]

@claude review

[claude]

LGTM — swaps a static image for the already-registered LoopDiagram MDX component used across the academy.

Extended reasoning...

Overview

Single-file docs change to content/docs/evaluation/core-concepts.mdx: removes a <Frame>-wrapped static PNG and replaces it with <LoopDiagram />, an existing component globally registered in mdx-components.tsx and already rendered on ~20 other MDX pages (academy and blog).

Security risks

None. Pure MDX content swap; no auth, data flow, or executable code paths touched.

Level of scrutiny

Minimal — this is a size:XS documentation-only edit labeled auto-merge. The component already exists and is battle-tested elsewhere in the same site.

Other factors

Bug hunting system found no issues. Vercel preview build is running. The only observation worth mentioning is that the PR description contains an empty backticks pair (``) where the component name was presumably intended — cosmetic only, doesn't affect the code.