Skip to content

docs: rename component categories for 1.7#10645

Closed
mendonk wants to merge 6 commits into
docs-1.7-releasefrom
docs-rename-component-categories
Closed

docs: rename component categories for 1.7#10645
mendonk wants to merge 6 commits into
docs-1.7-releasefrom
docs-rename-component-categories

Conversation

@mendonk
Copy link
Copy Markdown
Collaborator

@mendonk mendonk commented Nov 18, 2025

Preview
Change component categories and pages for 1.7, see #10180
This is a lazy version that creates minimal new pages, renames existing pages, and moves the components around, with the left nav reshuffled.

Links are updated.

Further component changes in 1.7 will be based on this PR.

@mendonk mendonk requested a review from aimurphy November 18, 2025 16:30
@mendonk mendonk self-assigned this Nov 18, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Nov 18, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs-rename-component-categories

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

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

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Nov 18, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Nov 18, 2025

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

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Nov 18, 2025
Copy link
Copy Markdown
Collaborator

@aimurphy aimurphy left a comment

Choose a reason for hiding this comment

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

Please see my comments. Some things are unclear.

Comment on lines +17 to +23
* **Load files**: Import data from a file or directory with the [**Read File** component](/components-files#read-file) and [**Directory** component](components-files#directory).

* **Search the web**: Fetch data from the web with components like the [**News Search** component](#news-search), [**RSS Reader** component](#rss-reader), [**Web Search** component](#web-search), and [**URL** component](#url).
* **Search the web**: Fetch data from the web with components like the [**News Search** component](/components-data#news-search), [**RSS Reader** component](/components-data#rss-reader), [**Web Search** component](/components-data#web-search), and [**URL** component](/components-data#url).

* **Make API calls**: Use APIs to trigger flows or perform actions with the [**API Request** component](#api-request) and [**Webhook** component](#webhook).
* **Make API calls**: Use APIs to trigger flows or perform actions with the [**API Request** component](#api-request) and [**Webhook** component](/components-io#webhook).

* **Run SQL queries**: Query an SQL database with the [**SQL Database** component](#sql-database).
* **Run SQL queries**: Query an SQL database with the [**SQL Database** component](/components-helpers#sql-database).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

These are just some examples for flavor; however most of these aren't on this page anymore.
The intro needs to be changed because this will create confusion.
The simplest solution is to just delete lines 15-28 (or 15-34 if the tip no longer makes sense).

@@ -0,0 +1,264 @@
---
title: Files and knowledge
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is this the name of the category in the UI?


For videos, see the **Twelve Labs** and **YouTube** <Icon name="Blocks" aria-hidden="true" /> [**Bundles**](/components-bundle-components).

### File parameters
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
### File parameters
### Read File parameters

For additional Docling features, including other components and OCR parsers, use the [**Docling** bundle](/bundles-docling).
:::

### File output
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
### File output
### Read File output

import TabItem from '@theme/TabItem';

Helper components provide utility functions to help manage data and perform simple tasks in your flow.
In Langflow version 1.7.0, the **Helpers** category was renamed **Utilities**.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Please make a ticket (or add to your Slack list) to remove these version-specific sentences in a future release when they are stale.


## Webhook

The **Webhook** component defines a webhook trigger that runs a flow when it receives an HTTP POST request.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
The **Webhook** component defines a webhook trigger that runs a flow when it receives an HTTP POST request.
The **Webhook** component creates a webhook trigger that runs a flow when it receives an HTTP POST request.
The **Webhook** component is for starting flows only.
It cannot be used as a flow's output component.

optional suggestion

import PartialParams from '@site/docs/_partial-hidden-params.mdx';
import PartialDevModeWindows from '@site/docs/_partial-dev-mode-windows.mdx';

LLM operations components use attached [**Language model** components](/components-models) to make decisions.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Could you check if "Language model component" is bold or not on other pages? I think I stopped bolding it because we have the core component and bundled components. The bundles don't consistently use the words "language model" in the component names, so it's not really accurate to bold it. (Same for embedding model components).

@@ -1,5 +1,5 @@
---
title: Processing components
title: Processing
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I put "components" in the name here because Prompt template is on its own page in this section. I didn't want to misrepresented "processing" as a single component.

TBH, I think all the components should just have their own pages, and then structure the nav by the categories. It would make these reorgs much less painful because we could just shuffle the nav instead of moving the content around piecemeal. You don't need to do that in this PR, but just and idea to keep in mind.

* Transform data into a different data type with the [**Type Convert** component](#type-convert) to pass it between incompatible components.
* **Transform data structures**: Convert data between different types with the [**Type Convert** component](#type-convert), or perform operations on structured data with the [**Data Operations** component](#data-operations) and [**DataFrame Operations** component](#dataframe-operations).

## Prompt Template
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is Prompt Template still in this category? If not, remove this section.

Comment thread docs/sidebars.js
"Components/components-agents",
"Components/components-embedding-models",
{
type: "link",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I'm not clear what's happening here. Why are these anchored links in here? Are these components in two categories?

@mendonk
Copy link
Copy Markdown
Collaborator Author

mendonk commented Nov 18, 2025

Screenshot 2025-11-18 at 12 05 54 PM

@mendonk
Copy link
Copy Markdown
Collaborator Author

mendonk commented Nov 18, 2025

Closing to just make each component its own page.

@mendonk mendonk closed this Nov 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants