Merge branch 'dev' into generic_icon_component

.github/workflows/deploy_gh-pages.yml

@@ -0,0 +1,39 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+    # Review gh actions docs if you want to further define triggers, paths, etc
+    # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
+
+jobs:
+  deploy:
+    name: Deploy to GitHub Pages
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 18
+          cache: npm
+          cache-dependency-path: ./docs/package-lock.json
+
+      - name: Install dependencies
+        run: cd docs && npm install
+      - name: Build website
+        run: cd docs && npm run build
+
+      # Popular action to deploy to GitHub Pages:
+      # Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          # Build output to publish to the `gh-pages` branch:
+          publish_dir: ./docs/build
+          # The following lines assign commit authorship to the official
+          # GH-Actions bot for deploys to `gh-pages` branch:
+          # https://github.com/actions/checkout/issues/13#issuecomment-724415212
+          # The GH actions bot is used by default if you didn't specify the two fields.
+          # You can swap them out with your own user credentials.

.gitignore

@@ -244,5 +244,10 @@ dmypy.json
 # Poetry
 .testenv/*
 langflow.db
+
+
 .githooks/prepare-commit-msg
-langchain.db
+.langchain.db
+
+# docusaurus
+.docusaurus/

.readthedocs.yaml

@@ -0,0 +1,31 @@
+# Read the Docs configuration file for Sphinx projects
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the OS, Python version and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.11"
+    # You can also specify other tool versions:
+    # nodejs: "19"
+    # rust: "1.64"
+    # golang: "1.19"
+
+# Build documentation in the "docs/" directory with Sphinx
+sphinx:
+   configuration: docs/conf.py
+
+# Optionally build your docs in additional formats such as PDF and ePub
+# formats:
+#    - pdf
+#    - epub
+
+# Optional but recommended, declare the Python requirements required
+# to build your documentation
+# See https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
+# python:
+#    install:
+#    - requirements: docs/requirements.txt

docs/README.md

@@ -0,0 +1,41 @@
+# Website
+
+This website is built using [Docusaurus 2](https://docusaurus.io/), a modern static website generator.
+
+### Installation
+
+```
+$ yarn
+```
+
+### Local Development
+
+```
+$ yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+### Build
+
+```
+$ yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+### Deployment
+
+Using SSH:
+
+```
+$ USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```
+$ GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

docs/babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

docs/docs/components/agents.mdx

@@ -0,0 +1,2 @@
+# Agents 
+(coming soon)

docs/docs/components/chains.mdx

@@ -0,0 +1,2 @@
+# Chains
+(coming soon)

docs/docs/components/embeddings.mdx

@@ -0,0 +1,2 @@
+# Embeddings
+(coming soon)

docs/docs/components/llms.mdx

@@ -0,0 +1,2 @@
+# LLMs
+(coming soon)

docs/docs/components/loaders.mdx

@@ -0,0 +1,2 @@
+# Loaders
+(coming soon)

docs/docs/components/memories.mdx

@@ -0,0 +1,2 @@
+# Memories
+(coming soon)

docs/docs/components/prompts.mdx

@@ -0,0 +1,2 @@
+# Prompts
+(coming soon)

docs/docs/components/text-splitters.mdx

@@ -0,0 +1,2 @@
+# Text Splitters
+(coming soon)

docs/docs/components/toolkits.mdx

@@ -0,0 +1,2 @@
+# Toolkits
+(coming soon)

docs/docs/components/tools.mdx

@@ -0,0 +1,2 @@
+# Tools
+(coming soon)

docs/docs/components/utilities.mdx

@@ -0,0 +1,2 @@
+# Utilities
+(coming soon)

docs/docs/components/vector-stores.mdx

@@ -0,0 +1,2 @@
+# Vector Stores
+(coming soon)

docs/docs/components/wrappers.mdx

@@ -0,0 +1,2 @@
+# Wrappers
+(coming soon)

docs/docs/contributing/community.md

@@ -0,0 +1,38 @@
+# Community
+
+## 🤖 Join **Langflow** Discord server
+
+ Join us to ask questions and showcase your projects.
+
+ Let's bring together the building blocks of AI integration!
+
+ Langflow [Discord](https://discord.gg/EqksyE2EX9) server.
+
+---
+
+## 🐦 Stay tunned for **Langflow** on Twitter
+
+Follow [@logspace_ai](https://twitter.com/logspace_ai) on **Twitter** to get the latest news about **Langflow**.
+
+---
+## ⭐️ Star **Langflow** on GitHub
+
+You can "star" **Langflow** in [GitHub](https://github.com/logspace-ai/langflow).
+
+By adding a star, other users will be able to find it more easily and see that it has been already useful for others.
+
+---
+
+## 👀 Watch the GitHub repository for releases
+
+You can "watch" **Langflow** in [GitHub](https://github.com/logspace-ai/langflow).
+
+
+If you select "Watching" instead of "Releases only" you will receive notifications when someone creates a new issue or question. You can also specify that you only want to be notified about new issues, discussions, PRs, etc.
+
+
+Then you can try and help them solve those questions.
+
+---
+
+Thanks! 🚀

docs/docs/contributing/github-issues.md

@@ -0,0 +1,27 @@
+# GitHub Issues
+
+Our [issues](https://github.com/logspace-ai/langflow/issues) page is kept up to date
+with bugs, improvements, and feature requests. There is a taxonomy of labels to help
+with sorting and discovery of issues of interest.
+
+If you're looking for help with your code, consider posting a question on the
+[GitHub Discussions board](https://github.com/logspace-ai/langflow/discussions). Please
+understand that we won't be able to provide individual support via email. We
+also believe that help is much more valuable if it's **shared publicly**,
+so that more people can benefit from it.
+
+- **Describing your issue:** Try to provide as many details as possible. What
+  exactly goes wrong? _How_ is it failing? Is there an error?
+  "XY doesn't work" usually isn't that helpful for tracking down problems. Always
+  remember to include the code you ran and if possible, extract only the relevant
+  parts and don't just dump your entire script. This will make it easier for us to
+  reproduce the error.
+
+- **Sharing long blocks of code or logs:** If you need to include long code,
+  logs or tracebacks, you can wrap them in `<details>` and `</details>`. This
+  [collapses the content](https://developer.mozilla.org/en/docs/Web/HTML/Element/details) so it only becomes visible on click, making the issue easier to read and follow.
+
+
+## Issue labels
+
+[See this page](https://github.com/logspace-ai/langflow/labels) for an overview of the system we use to tag our issues and pull requests.