Skip to content

Wavefront documentation to mintlify#170

Merged
vizsatiz merged 2 commits into
developfrom
wavefront
Nov 25, 2025
Merged

Wavefront documentation to mintlify#170
vizsatiz merged 2 commits into
developfrom
wavefront

Conversation

@vizsatiz
Copy link
Copy Markdown
Member

@vizsatiz vizsatiz commented Nov 25, 2025

Summary by CodeRabbit

  • Documentation
    • Renamed first navigation tab from "Guides" to "Wavefront" and reintroduced the index page under it
    • Added a new "FloAI" documentation tab with Getting Started, Core Features, and Advanced groups
    • Reworked main docs landing to a Wavefront AI Middleware overview with architecture, platform components, and release timeline
    • Updated footer GitHub link to the Wavefront repository
    • Minor formatting and whitespace cleanups

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Nov 25, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Navigation and landing documentation were reorganized: the first nav tab was renamed to "Wavefront", a new "FloAI" tab was added, the main landing page was replaced with a Wavefront overview, and a new Flo AI onboarding MDX page was introduced.

Changes

Cohort / File(s) Change Summary
Navigation changes
documentation/docs.json
Renamed first navigation tab from Guides to Wavefront; added a new FloAI tab with groups ("Getting started", "Core Features", "Advanced") and pages; adjusted contextual options array formatting; updated footer GitHub link from Flo AI to Wavefront.
New Flo AI page
documentation/flo-ai.mdx
Added a new MDX onboarding page for Flo AI with sections: Welcome (Quick Start), Key Features, Core Capabilities, and Get Started links to essentials and examples.
Landing page replacement
documentation/index.mdx
Replaced previous Flo AI landing content with a Wavefront AI Middleware "Project Overview" including capabilities list, architecture overview (with image), platform components, and a release timeline; updated community messaging and EOF formatting.

Sequence Diagram(s)

(Skipped — changes are documentation/navigation edits and do not modify runtime control flow.)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Pay attention to JSON structure and comma/brace placement in documentation/docs.json.
  • Review documentation/index.mdx for large content/formatting errors and correct image path alignment.
  • Verify internal links in documentation/flo-ai.mdx point to existing doc pages (essentials/*, telemetry, examples).

Poem

🐰 I nibbled through the doc-lined trail,
A Wavefront title set to sail,
FloAI tucked in a brand-new tab,
Pages polished, footers nabbed,
Hopping onward — docs prevail! 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main objective: migrating Wavefront documentation to Mintlify format, as evidenced by the reorganization of docs.json navigation structure and the creation of new MDX documentation files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 066b84f and 4e70739.

⛔ Files ignored due to path filters (3)
  • documentation/images/wavefront-arc.png is excluded by !**/*.png
  • documentation/logo/dark.png is excluded by !**/*.png
  • documentation/logo/light.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • documentation/docs.json (2 hunks)

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
documentation/flo-ai.mdx (1)

6-6: Consider clarifying the "(Wavefront coming soon)" note.

The heading "## Welcome to Flo AI (Wavefront coming soon) 🌊" signals a transition, but it may create confusion about the current state of the platform. Consider:

  • Removing the parenthetical if Wavefront is a separate product/tab
  • Updating the phrasing to clarify the relationship between Flo AI and Wavefront
documentation/index.mdx (1)

14-14: Remove duplicate Discord link.

The Discord link appears twice: once in the introductory section (line 14) and again at the end (line 88). Remove the duplicate to reduce redundancy.

Apply this diff to remove the duplicate:

-**Join our discord at https://discord.gg/BPXsNwfuRU** to get early access to the platform and to provide feedback
+Join our community to get early access and provide feedback.

Alternatively, keep the explicit link in one location (recommend the opening section) and use a softer closing at the end.

Also applies to: 88-88

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 108e0c0 and 066b84f.

📒 Files selected for processing (3)
  • documentation/docs.json (3 hunks)
  • documentation/flo-ai.mdx (1 hunks)
  • documentation/index.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
documentation/index.mdx

[style] ~7-~7: Try moving the adverb to make the sentence clearer.
Context: ...I is an open-source middleware platform designed to seamlessly integrate AI-driven agents, workflows, and data sources across ent...

(SPLIT_INFINITIVE)


[uncategorized] ~35-~35: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...nce and least-privilege access. - 🤖 Open Source & Proprietary Model Support Works...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🔇 Additional comments (9)
documentation/docs.json (3)

14-23: Verify that the Wavefront tab is complete with all intended pages.

The renamed "Wavefront" tab now contains only the "index" page. Confirm this is intentional—if other pages (e.g., architecture, roadmap, API reference) should appear under this tab, they should be added to the pages array.


92-99: Approve contextual options formatting adjustments.

The reformatting of the contextual options array (indentation and ordering) does not change the set of options available. The change is purely stylistic.


24-56: All FloAI tab page references are valid and exist in the documentation.

Verification confirms that all 14 pages referenced in the FloAI tab across the three groups (Getting started, Core Features, Advanced) have corresponding MDX/MD files in the documentation directory. No missing files detected.

documentation/flo-ai.mdx (3)

1-4: Verify page title alignment with navigation structure.

The page title is "Flo AI Documentation", but based on docs.json, this page is referenced as "flo-ai" under the FloAI tab. Consider renaming the title to "Flo AI" or "Introduction to Flo AI" to avoid confusion with the overall documentation. The current title may imply this is the entire Flo AI documentation rather than an onboarding/introduction page.


1-4: Approve content structure and Mintlify component usage.

The page structure is well-organized using Mintlify's Card and Columns components. Frontmatter is correct, and the layout clearly presents Flo AI's features and capabilities.


10-95: All internal href references in documentation/flo-ai.mdx have been verified and resolve to existing documentation pages. No missing pages were detected, and the duplicate reference to essentials/telemetry is expected (lines 32 and 81 both link to the telemetry page in different card contexts).

documentation/index.mdx (3)

55-55: Verify image path resolves correctly.

The image path ./images/wavefront-arc.png must exist relative to the documentation directory. Mintlify typically resolves paths from the documentation/ root, so confirm the file is located at documentation/images/wavefront-arc.png.


16-16: Approve cross-file navigation linking.

The note linking to /flo-ai correctly references the new Flo AI onboarding page, establishing proper navigation between the Wavefront overview and Flo AI documentation. This aligns well with the docs.json tab structure.


5-70: Approve comprehensive Wavefront overview structure.

The new content establishes a clear project identity with:

  • Clear status and licensing information
  • Comprehensive capabilities list
  • Well-organized architecture overview with visual support
  • Transparent release timeline

The restructuring from "Flo AI Documentation" to "Project Overview" effectively positions Wavefront as the primary platform while integrating Flo AI as a core component. The information hierarchy is logical and serves as an effective landing page.

Comment thread documentation/index.mdx
Comment on lines +2 to +14
title: "Project Overview"
---

<Note>Wavefront documentation will be updated soon, along with code release</Note>

## Welcome to Flo AI (Wavefront coming soon) 🌊

Flo AI is a Python framework that makes building production-ready AI agents and teams as easy as writing YAML. Think "Kubernetes for AI Agents" - compose complex AI architectures using pre-built components while maintaining the flexibility to create your own.

<Card
title="Quick Start"
icon="rocket"
href="/quickstart"
horizontal
>
Get started with Flo AI in minutes - from installation to your first agent.
</Card>

## Key Features

<Columns cols={2}>
<Card
title="🔌 Truly Composable"
icon="puzzle-piece"
href="/essentials/agents"
>
Build complex AI systems by combining smaller, reusable components.
</Card>
<Card
title="🏗️ Built-in observability"
icon="shield-check"
href="/essentials/telemetry"
>
Built-in observability for production deployments.
</Card>
<Card
title="📝 YAML-First"
icon="file-code"
href="/essentials/yaml-workflows"
>
Define your entire agent architecture in simple YAML configurations.
</Card>
<Card
title="🧠 LLM-Powered Routing"
icon="route"
href="/essentials/routing"
>
Intelligent routing decisions made by LLMs, no code required.
</Card>
</Columns>

## Core Capabilities

Everything you need to build sophisticated AI agents and workflows.

<Columns cols={2}>
<Card
title="Multi-LLM Support"
icon="brain"
href="/essentials/llm-providers"
>
Support for OpenAI, Anthropic, Google, Ollama, and more with consistent interfaces.
</Card>
<Card
title="Tool Integration"
icon="wrench"
href="/essentials/tools"
>
Easy tool creation with the @flo_tool decorator and LangChain compatibility.
</Card>
<Card
title="Visual Studio"
icon="palette"
href="/essentials/studio"
>
Design AI workflows visually with our React-based studio interface.
</Card>
<Card
title="OpenTelemetry"
icon="chart-line"
href="/essentials/telemetry"
>
Built-in observability with automatic instrumentation for production monitoring.
</Card>
</Columns>

## Get Started

<Card
title="View Examples"
icon="code"
href="https://github.com/rootflo/flo-ai/tree/main/flo_ai/examples"
>
Explore comprehensive examples and use cases in our GitHub repository.
</Card>
# 🚀 Wavefront AI Middleware

Wavefront AI is an open-source middleware platform designed to seamlessly integrate AI-driven agents, workflows, and data sources across enterprise environments. It acts as a connective layer that bridges modular frontend applications with complex backend data pipelines, ensuring secure access, observability, and compatibility with modern AI and data infrastructures.

**Status**: Pre-release (Under active development)
**Beta release**: Dec 2025
**Wavefront License**: GNU AFFERO GENERAL PUBLIC LICENSE 3.0
**FloAI License**: MIT LICENSE
**Contributing**: We welcome early feedback! See [CONTRIBUTING.md](CONTRIBUTING.md).
**Community**: Join our discord at https://discord.gg/BPXsNwfuRU
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify external links and fix grammar issues.

Three concerns here:

  1. Link verification: Confirm that CONTRIBUTING.md exists and the Discord link is correct.
  2. Grammar – Split infinitive (Line 7): "designed to seamlessly integrate" should be restructured. Consider: "designed to integrate seamlessly AI-driven agents..." or "designed for seamless integration of AI-driven agents...".
  3. Grammar – Compound adjective (Line 35): "Open Source & Proprietary Model Support" should use hyphens: "Open-Source & Proprietary-Model Support" or restructure as "Support for Open-Source and Proprietary Models".

🏁 Script executed:

#!/bin/bash
# Description: Verify file and link references in index.mdx

# Check if CONTRIBUTING.md exists
if [[ -f "CONTRIBUTING.md" ]]; then
  echo "✓ Found: CONTRIBUTING.md"
else
  echo "❌ Missing: CONTRIBUTING.md"
fi

# Check if image exists
if [[ -f "documentation/images/wavefront-arc.png" ]]; then
  echo "✓ Found: documentation/images/wavefront-arc.png"
else
  echo "❌ Missing: documentation/images/wavefront-arc.png"
fi

Length of output: 74


I need to verify the missing image file location and check the Discord link. Let me gather more information:


---

🏁 Script executed:

```shell
#!/bin/bash
# Find all PNG files in documentation directory
echo "=== Searching for PNG files in documentation/ ==="
fd -e png documentation/

# Check the actual content of index.mdx around the image reference
echo -e "\n=== Checking image reference in index.mdx ==="
rg -n "wavefront-arc" documentation/

# List all files in documentation/images if it exists
echo -e "\n=== Contents of documentation/images/ directory ==="
ls -la documentation/images/ 2>/dev/null || echo "Directory not found"

Length of output: 615


🏁 Script executed:

#!/bin/bash
# Verify Discord link returns valid response
echo "=== Checking Discord link ==="
curl -s -o /dev/null -w "HTTP Status: %{http_code}\n" "https://discord.gg/BPXsNwfuRU"

Length of output: 46


Critical issue: Missing image directory and incorrect alt text. Verify grammar and link references.

The verification found:

  • CONTRIBUTING.md exists
  • ✓ Discord link is valid (HTTP 301 redirect)
  • documentation/images/ directory does not exist — the image referenced at line 55 (./images/wavefront-arc.png) cannot be found. Create the directory and add the image file, or update the image path if it's stored elsewhere.
  • Incorrect alt text (line 55): alt="Rootflo" should reflect Wavefront content, e.g., alt="Wavefront Architecture".

Also fix the grammar issues:

  1. Split infinitive (Line 7): Restructure "designed to seamlessly integrate AI-driven agents..." to "designed for seamless integration of AI-driven agents..." or "designed to integrate seamlessly across..."
  2. Compound adjective (Line 35): Use hyphens or restructure "Open-Source & Proprietary-Model Support" or "Support for Open-Source and Proprietary Models".
🧰 Tools
🪛 LanguageTool

[style] ~7-~7: Try moving the adverb to make the sentence clearer.
Context: ...I is an open-source middleware platform designed to seamlessly integrate AI-driven agents, workflows, and data sources across ent...

(SPLIT_INFINITIVE)

🤖 Prompt for AI Agents
In documentation/index.mdx around lines 2–14 (and referencing line 55), the
referenced image path ./images/wavefront-arc.png is missing because
documentation/images/ does not exist and the alt text is incorrect; create the
documentation/images/ directory and add the wavefront-arc.png file (or update
the image path to the correct existing location), change alt="Rootflo" to
alt="Wavefront Architecture", reword line 7 from "designed to seamlessly
integrate AI-driven agents..." to "designed for seamless integration of
AI-driven agents..." (or "designed to integrate seamlessly across..."), and
change the compound adjective on line 35 to "Support for Open-Source and
Proprietary Models" or use hyphens like "Open-Source & Proprietary-Model
Support" to correct grammar.

Comment thread documentation/index.mdx
Built-in telemetry with Grafana and Prometheus support. Track agent performance, audit trails, and guardrail enforcement in real-time.

- **🤖 No Code Agent & Workflow Builder**
Built-in capabilities to build and customer AI agents, and AI Workflows, connecting Data Sources, Knowledge Bases, in minutes
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix apparent typo: "customer" → "custom".

Line 42 reads: "...build and customer AI agents...". This appears to be a typo; should be "custom AI agents".

Apply this diff to fix the typo:

-  Built-in capabilities to build and customer AI agents, and AI Workflows, connecting Data Sources, Knowledge Bases, in minutes
+  Built-in capabilities to build and customize AI agents, and AI Workflows, connecting Data Sources, Knowledge Bases, in minutes
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Built-in capabilities to build and customer AI agents, and AI Workflows, connecting Data Sources, Knowledge Bases, in minutes
Built-in capabilities to build and customize AI agents, and AI Workflows, connecting Data Sources, Knowledge Bases, in minutes
🤖 Prompt for AI Agents
documentation/index.mdx around line 42: the phrase "build and customer AI
agents" contains a typo—replace "customer" with "custom" so the sentence reads
"build and custom AI agents"; update that single word at line 42 to correct the
typo.

@vizsatiz vizsatiz merged commit 84c4eb3 into develop Nov 25, 2025
4 of 5 checks passed
@vizsatiz vizsatiz deleted the wavefront branch November 25, 2025 06:06
@vizsatiz vizsatiz restored the wavefront branch December 4, 2025 08:17
@vizsatiz vizsatiz deleted the wavefront branch December 4, 2025 08:19
thomastomy5 pushed a commit that referenced this pull request Apr 27, 2026
* Wavefront documentation to mintify

* Adding png files
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