Docs: update screenshots with new UI changes (#4579)

* remove-images

* logs-pane

* logs

* more-logs

* langsmith-langwatch

* guides-folder

* quickstart

* follow-image

* getting-started-folder

* share-store-change

* workspace-old-images

* component-folder

* deployment-folder

* configuration-folder

* delete-venv

* favicon-footer-header

* favicon-bw-and-replace-gif

* docs: Update prerequisites and terminology in Getting Started and Workspace documentation

* docs: Update terminology from "New Project" to "New Flow" in starter project documentation

* Apply suggestions from code review

Co-authored-by: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com>

* docs: Update terminology from "project" to "flow" in starter project documentation

* docs: Update terminology from "project" to "flow" in starter project documentation

---------

Co-authored-by: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com>
This commit is contained in:
Mendon Kissling 2024-11-13 19:58:01 -05:00 • committed by GitHub
commit c7f688ceda
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
232 changed files with 144 additions and 249 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 385 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 113 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 133 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 185 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 136 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 130 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 63 KiB

View file

@ -90,8 +90,6 @@ class CustomComponent(Component):
8. Click **Check & Save** to confirm your component works.
You now have an operational custom component.
![](./238089171.png)
## Add inputs and modify output methods
@ -161,8 +159,6 @@ Since the component outputs a `Message`, you can wire it into a chat and pass me
Your Custom Component accepts the Chat Input message through `MessageTextInput`, fills in the variables with the `process_inputs` method, and finally passes the message `User Username (Age: 49, Gender: Male) sent the following special message: Hello!` to Chat Output.
![](./custom-component-chat.png)
By defining inputs this way, Langflow can automatically handle the validation and display of these fields in the user interface, making it easier to create robust and user-friendly custom components.
All of the types detailed above derive from a general class that can also be accessed through the generic `Input` class.
@ -427,8 +423,6 @@ The component performs basic text analysis, including character count and senten
Since the component inputs and outputs a `Message`, you can wire the component into a chat and see how the basic custom component logic interacts with your input.
![](./custom-component-inputs-chat.png)
## Create a Custom Component with Multiple Outputs {#6f225be8a142450aa19ee8e46a3b3c8c}
---

View file

@ -10,7 +10,7 @@ A component is a single building block within a flow. It consists of inputs, o
During the flow creation process, you will notice handles (colored circles) attached to one or both sides of a component. These handles use distinct colors to indicate the types of inputs and outputs that can be interconnected. Hover over a handle to see connection details.
![](./565424296.png)
<img src="/img/prompt-component.png" alt="Prompt component" style={{display: 'block', margin: 'auto', width: 300}} />
On the top right corner of the component, you'll find the a play button to run a component. Once it runs, a status icon appears and you can hover over that to visualize success or error messages. Start interacting with your AI by clicking the **Playground** at the bottom right of the workspace.
@ -22,14 +22,14 @@ On the top right corner of the component, you'll find the a play button to run a
Each component is unique, but they all have a menu bar at the top that looks something like this.
![](./938852908.png)
<img src="/img/openai-model-component.png" alt="Prompt component" style={{display: 'block', margin: 'auto', width: 300}} />
It consists of options such as:
- **Code** — displays the component's Python code. You can modify the code and save it.
- **Advanced** — See and adjust all parameters of a component.
- **Freeze** — After a component runs, lock its previous output state to prevent it from re-running.
- **Code** — Modify the component's Python code and save it.
- **Controls** — Adjust all parameters of a component.
- **Freeze Path** — After a component runs, lock its previous output state to prevent it from re-running.
Click **All** (the "..." button) to see all options.
@ -40,9 +40,6 @@ Click **All** (the "..." button) to see all options.
Langflow includes an output visualizer for components that opens a pop-up screen. This allows you to easily inspect and monitor transmissions between components, providing instant feedback on your workflows.
![](./987204819.png)
## Advanced settings {#b6430d4903df44f0ba4618a558c83d7b}
@ -66,17 +63,9 @@ Multiple components can be grouped into a single component for reuse. This is us
4. Double-click the name and description to change them.
5. Save your grouped component to in the sidebar for later use!
[group video here]
## Component version {#887fd587589448dc8c27336d1c235b9b}
A component's state is stored in a database, while sidebar components are like starter templates. As soon as you drag a component from the sidebar to the workspace, the two components are no longer in parity.
The component will keep the version number it was initialized to the workspace with. Click the **Update Component** icon (exclamation mark) to bring the component up to the `latest` version. This will change the code of the component in place so you can validate that the component was updated by checking its Python code before and after updating it.
![](./263391508.png)

Binary file not shown.

Before

Width:  |  Height:  |  Size: 276 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 178 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 350 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 341 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 171 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 833 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 44 KiB

Some files were not shown because too many files have changed in this diff Show more