docs: update support documentation to reflect support rebranding

[mendonk]

This pull request updates documentation to reflect a change in branding from "Luna for Langflow" by DataStax to "IBM Elite Support for Langflow."

Summary by CodeRabbit

• Documentation
  • Rebranded “Luna for Langflow” to “IBM Elite Support for Langflow” throughout the support page.
  • Updated provider references from DataStax to IBM, including subscriber terminology and contact details.
  • Revised coverage statement to August 2025 and updated supported Langflow versions to 1.5.x.
  • Replaced the subscription link with the new IBM Elite Support URL.
  • Updated the Support sidebar label to “IBM Elite Support for Langflow.”

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Rebrands the Langflow support documentation from “Luna”/DataStax to “IBM Elite Support,” updates coverage/version text and subscription link, and changes the sidebar label for the doc entry. No code or logic changes.

Changes

Cohort / File(s)	Summary
Documentation content rebrand docs/docs/Support/luna-for-langflow.mdx	Replaced “Luna for Langflow”/DataStax references with “IBM Elite Support for Langflow”/IBM, updated coverage to “As of August 2025… supports Langflow 1.5.x,” updated subscription link; slug and Python versions unchanged.
Documentation navigation label docs/sidebars.js	Sidebar label for Support/luna-for-langflow changed from “Enterprise support” to “IBM Elite Support for Langflow”; structure and id unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• docs: Build out Troubleshooting and Support documentation #8662 — Also modifies the same support doc and its sidebar label; earlier rebranded it to “Enterprise support,” aligning with this doc’s evolution.

Suggested labels

documentation, size:XS, lgtm

Suggested reviewers

• carlosrcoelho

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs-update-support-page

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (4)

docs/docs/Support/luna-for-langflow.mdx (4)

6-13: Shift to second-person, active voice and tighten copy.

Style guide calls for second person and present tense. Also simplify “If an issue is encountered…” to active voice.

Apply this diff:

-With **IBM Elite Support for Langflow** support, you can develop and deploy Langflow applications with confidence.
+With **IBM Elite Support for Langflow**, you develop and deploy Langflow applications with confidence.

-IBM Elite Support for Langflow is a subscription to the Langflow expertise at IBM.
-It's meant for Langflow users who want all the benefits of running their own open-source deployments, as well as the peace of mind that comes with having direct access to the team that has authored the majority of the Langflow code.
+IBM Elite Support for Langflow is a subscription to IBM’s Langflow expertise.
+Use it when you want the benefits of running your own open-source deployment and the peace of mind that comes from direct access to the team that authored most of the Langflow code.

-IBM Elite Support subscribers can get help with general-purpose and technical questions for their open-source Langflow deployments.
-If an issue is encountered, IBM is there to help.
+IBM Elite Support subscribers get help with general and technical questions for their open-source Langflow deployments.
+If you encounter an issue, IBM will help.

---

15-15: Remove redundant wording in info note.

“Support … support covers” is repetitive. Streamline.

Apply this diff:

-As of August 2025, IBM Elite Support for Langflow support covers Langflow versions 1.5.x.
+As of August 2025, IBM Elite Support for Langflow covers Langflow versions 1.5.x.

---

18-18: Fix pluralization and tighten wording.

Grammar: “all version” → “all versions.” Also optional: drop the parenthetical since the range already conveys it.

Apply this diff:

-Supported versions are `>=3.10, <3.14`, which includes all version from 3.10 through 3.13.x, but not 3.14.
+Supported versions are `>=3.10, <3.14`, which includes all versions from 3.10 through 3.13.x, but not 3.14.

---

1-21: Optional: Add sidebar_label here to keep the source of truth in the doc.

You updated the label in sidebars.js. Alternatively, set sidebar_label in frontmatter so the doc controls its own label and sidebars can remain lean.

Apply this diff:

 ---
 title: IBM Elite Support for Langflow
+sidebar_label: IBM Elite Support for Langflow
 description: Get enterprise-grade help for your open-source Langflow deployments with direct access to experts.
 slug: /luna-for-langflow
 ---

If you adopt this, you can remove the explicit label override for this entry in docs/sidebars.js.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 933198d and 35fd461.

📒 Files selected for processing (2)

• docs/docs/Support/luna-for-langflow.mdx (1 hunks)
• docs/sidebars.js (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

docs/docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)

docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.

Files:

• docs/docs/Support/luna-for-langflow.mdx

docs/sidebars.js

📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)

Sidebar navigation must be updated in docs/sidebars.js to reflect new or reorganized documentation content.

Files:

• docs/sidebars.js

🧠 Learnings (1)

📚 Learning: 2025-07-18T18:26:42.027Z

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be updated in docs/sidebars.js to reflect new or reorganized documentation content.

Applied to files:

• docs/sidebars.js

🪛 LanguageTool

docs/docs/Support/luna-for-langflow.mdx

[grammar] ~14-~14: There might be a mistake here.
Context: ...ountered, IBM is there to help. :::info As of August 2025, IBM Elite Support for...

(QB_NEW_EN)

---

[grammar] ~18-~18: There might be a mistake here.
Context: ... from 3.10 through 3.13.x, but not 3.14. ::: To subscribe or learn more, see [IB...

(QB_NEW_EN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build-and-deploy

🔇 Additional comments (2)

docs/sidebars.js (1)

472-475: Approve sidebar label update; slug unchanged ensures link stability

• Verified that the id: "Support/luna-for-langflow" and slug: /luna-for-langflow remain unchanged, so all existing routes will continue to work without redirects.
• No other Markdown or MDX files link to this slug outside of docs/docs/Support/luna-for-langflow.mdx, so there are no inbound links to update.

docs/docs/Support/luna-for-langflow.mdx (1)

21-21: External Link & Naming Verified Internally – Manual Confirmation Needed

• The link text “IBM Elite Support for Langflow” appears consistently in:
  • docs/docs/Support/luna-for-langflow.mdx
    • Title metadata (line 2)
    • Intro paragraph (line 6)
    • Info note (line 15)
    • Subscription link (line 21)
  • docs/sidebars.js
    • Sidebar label at line 474
• The URL https://ibm.com/docs/esfl?topic=elite-support-langflow-specification is present at docs/docs/Support/luna-for-langflow.mdx:21.

Please manually confirm that the external IBM documentation page at the above URL displays the exact product name “IBM Elite Support for Langflow” (e.g., in its header or title) to ensure full naming consistency.

[coderabbitai]

⚠️ Potential issue

Frontmatter missing required description field.

Docs must include at least title and description. Add a concise, second-person description.

Apply this diff:

 ---
-title: IBM Elite Support for Langflow
+title: IBM Elite Support for Langflow
+description: Get enterprise-grade help for your open-source Langflow deployments with direct access to experts.
 slug: /luna-for-langflow
 ---

📝 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

	---
	title: Enterprise support for Langflow
	title: IBM Elite Support for Langflow
	slug: /luna-for-langflow
	---
	---
	title: IBM Elite Support for Langflow
	description: Get enterprise-grade help for your open-source Langflow deployments with direct access to experts.
	slug: /luna-for-langflow
	---

🤖 Prompt for AI Agents

In docs/docs/Support/luna-for-langflow.mdx around lines 1 to 4 the frontmatter
is missing the required description field; add a concise, second-person
description key to the YAML frontmatter (e.g., description: "Explain how Luna
supports you when using Langflow") directly under the title line so the file
includes both title and description fields for docs validation.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Guard against leftover “Luna” references and broken internal links.

Given the rebrand, ensure no stale references remain and all internal links resolve.

Run:

---

🏁 Script executed:

#!/bin/bash
# 1) Find any lingering "Luna" references in docs
rg -nP '\bLuna\b' docs --type=md --type=mdx -C2

# 2) List docs missing the required frontmatter description
#    (assumes description should appear in the first 15 lines)
fd -t f -e md -e mdx docs/docs | xargs -I{} awk 'NR<=15{if($0~ /^---/){inFM=1} if(inFM && $0~ /^---/ && NR>1){inFM=0} if(inFM && $0~ /^description:/) found=1} END{if(!found) print FILENAME}' {}

# 3) Check internal links for the legacy slug and ensure they still point to a valid page
rg -nP '\]\(/luna-for-langflow\)' docs --type=md --type=mdx -C2

Length of output: 713

---

I’ll rerun the checks with globs to correctly include .mdx files and fix the fd usage:

---

🏁 Script executed:

#!/bin/bash
set -e

echo "1) Searching for any leftover “Luna” references in .md/.mdx:"
rg -nP '\bLuna\b' --glob '*.md' --glob '*.mdx' docs/ -C2 || echo "→ No lingering “Luna” references found."

echo
echo "2) Listing docs missing a frontmatter ‘description:’ (within first 15 lines):"
find docs/docs -type f \( -name '*.md' -o -name '*.mdx' \) -print | while read -r file; do
  if ! head -n 15 "$file" | awk '
    BEGIN { inFM = 0; found = 0 }
    /^---/ { if (inFM == 0) { inFM = 1 } else { inFM = 0 } }
    inFM && /^description:/ { found = 1 }
    END { exit !found }
  '; then
    echo "→ Missing description in frontmatter: $file"
  fi
done

echo
echo "3) Checking internal links still pointing at the old /luna-for-langflow slug:"
rg -nP '\]\(/luna-for-langflow\)' --glob '*.md' --glob '*.mdx' docs/ -C2 || echo "→ No broken internal links found."

Length of output: 57000

---

Add missing frontmatter description to Support/luna-for-langflow.mdx

No leftover “Luna” references or broken internal links were detected. However, the page’s frontmatter needs a description: field to comply with our docs standards.

• docs/docs/Support/luna-for-langflow.mdx
– Currently only has title and slug in its YAML block.
– Please add a description: entry within the first ---…--- section.

Suggested diff:

---
 title: IBM Elite Support for Langflow
-slug: /luna-for-langflow
+slug: /luna-for-langflow
+description: >
+  Subscription plan for IBM Elite Support tailored to Langflow 1.5.x deployments
+  (requires Python ≥3.10,<3.14).
---

📝 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

	---
	title: Enterprise support for Langflow
	title: IBM Elite Support for Langflow
	slug: /luna-for-langflow
	---
	With **Luna for Langflow** support, you can develop and deploy Langflow applications with confidence.
	With **IBM Elite Support for Langflow** support, you can develop and deploy Langflow applications with confidence.
	Luna is a subscription to the Langflow expertise at DataStax. It's meant for Langflow users who want all the benefits of running their own open-source deployments, as well as the peace of mind that comes with having direct access to the team that has authored the majority of the Langflow code.
	IBM Elite Support for Langflow is a subscription to the Langflow expertise at IBM.
	It's meant for Langflow users who want all the benefits of running their own open-source deployments, as well as the peace of mind that comes with having direct access to the team that has authored the majority of the Langflow code.
	Luna subscribers can get help with general-purpose and technical questions for their open-source Langflow deployments.
	If an issue is encountered, DataStax is there to help.
	IBM Elite Support subscribers can get help with general-purpose and technical questions for their open-source Langflow deployments.
	If an issue is encountered, IBM is there to help.
	:::info
	As of May 2025, Luna for Langflow support covers Langflow versions 1.4.x.
	As of August 2025, IBM Elite Support for Langflow support covers Langflow versions 1.5.x.
	Subscribers must run a supported Python version to receive support.
	Supported versions are `>=3.10, <3.14`, which includes all version from 3.10 through 3.13.x, but not 3.14.
	:::
	To subscribe or learn more, see [Luna for Langflow](https://www.datastax.com/products/luna-langflow).
	\ No newline at end of file
	To subscribe or learn more, see [IBM Elite Support for Langflow](https://ibm.com/docs/esfl?topic=elite-support-langflow-specification).
	---
	title: IBM Elite Support for Langflow
	slug: /luna-for-langflow
	description: >
	Subscription plan for IBM Elite Support tailored to Langflow 1.5.x deployments
	(requires Python ≥3.10,<3.14).
	---

🧰 Tools

🪛 LanguageTool

[grammar] ~14-~14: There might be a mistake here.
Context: ...ountered, IBM is there to help. :::info As of August 2025, IBM Elite Support for...

(QB_NEW_EN)

---

[grammar] ~18-~18: There might be a mistake here.
Context: ... from 3.10 through 3.13.x, but not 3.14. ::: To subscribe or learn more, see [IB...

(QB_NEW_EN)

🤖 Prompt for AI Agents

In docs/docs/Support/luna-for-langflow.mdx lines 1-21, the frontmatter block
only contains title and slug; add a description: field inside the initial ---
... --- YAML frontmatter (immediately after title or slug) with a short summary
of the page (one-line sentence describing IBM Elite Support for Langflow) so the
file complies with docs standards and metadata consumers can display a
description.

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarQube Cloud

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft