From 86724df7f1abcd01b39d8473a3118c359b29c547 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Mon, 25 Sep 2023 17:21:56 +0200 Subject: [PATCH 01/14] move advanced graph topics to reference docs --- docs/sidebars.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sidebars.js b/docs/sidebars.js index 6fb0ad6746a2..fd63d377c8c9 100644 --- a/docs/sidebars.js +++ b/docs/sidebars.js @@ -64,8 +64,6 @@ module.exports = { "concepts/components/overview", "concepts/components/llm-configuration", "concepts/components/llm-custom", - "concepts/components/custom-graph-components", - "concepts/components/graph-recipe", ], }, "concepts/policies", // TODO: ENG-538 @@ -260,6 +258,8 @@ module.exports = { "nlu-based-assistants/glossary", "telemetry/telemetry", "telemetry/reference", + "concepts/components/custom-graph-components", + "concepts/components/graph-recipe", require("./docs/reference/sidebar.json"), ], }, From c4ad2b8b8826a82ee5d6c4cde713af2dc808fd78 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Mon, 25 Sep 2023 17:22:41 +0200 Subject: [PATCH 02/14] wip refactor config/components section of calm docs --- .../concepts/components/llm-configuration.mdx | 82 +++++-------- docs/docs/concepts/components/overview.mdx | 108 ++++++++++++------ docs/docs/concepts/dialogue-understanding.mdx | 1 + 3 files changed, 106 insertions(+), 85 deletions(-) diff --git a/docs/docs/concepts/components/llm-configuration.mdx b/docs/docs/concepts/components/llm-configuration.mdx index f196969ea19b..a825e5ace6db 100644 --- a/docs/docs/concepts/components/llm-configuration.mdx +++ b/docs/docs/concepts/components/llm-configuration.mdx @@ -1,7 +1,7 @@ --- id: llm-configuration -sidebar_label: Configuration -title: Configuration +sidebar_label: LLM Providers +title: LLM Providers abstract: | Instructions on how to setup and configure Large Language Models from OpenAI, Cohere, and other providers. @@ -11,41 +11,22 @@ abstract: | ## Overview -This guide will walk you through the process of configuring Rasa to connect to an -LLM, including deployments that rely on Azure OpenAI service. Instructions for -other LLM providers are further down the page. +All Rasa components which make use of an LLM can be configured. +This includes: +* Which LLM provider to use +* The model you want to use +* The sampling temperature +* The prompt template -## Assitant Configration +and other settings. +This page applies to the following components which use LLMs: -To use LLMs in your assistant, you need to configure the following components: +* [LLMCommandGenerator](../dialogue-understanding.mdx) +* DocsearchPolicy +* IntentlessPolicy +* ContextualResponseRephraser +* LLMIntentClassifier -```yaml title="config.yml" -recipe: default.v1 -language: en -pipeline: - - name: LLMCommandGenerator - -policies: - - name: rasa.core.policies.flow_policy.FlowPolicy - - name: rasa_plus.ml.DocsearchPolicy - - name: RulePolicy -``` - -To use the rephrasing capability, you'll also need to add the following to your -endpoint configuration: - -```yaml title="endpoints.yml" -nlg: - type: rasa_plus.ml.ContextualResponseRephraser -``` - -Additional configuration parameters are explained in detail in the documentation -pages for each of these components: - -- [LLMCommandGenerator](../dialogue-understanding.mdx) -- [FlowPolicy](../policies.mdx#flow-policy) -- Docseacrh -- [ContextualResponseRephraser](../contextual-response-rephraser.mdx) ## OpenAI Configuration @@ -55,18 +36,10 @@ can be configured with different LLMs, but OpenAI is the default. If you want to configure your assistant with a different LLM, you can find instructions for other LLM providers further down the page. -### Prerequisites - -Before beginning, make sure that you have: - -- Access to OpenAI's services -- Ability to generate API keys for OpenAI ### API Token -The API token is a key element that allows your Rasa instance to connect and -communicate with OpenAI. This needs to be configured correctly to ensure seamless -interaction between the two. +The API token authenticates your requests to the OpenAI API. To configure the API token, follow these steps: @@ -102,16 +75,23 @@ To configure the API token, follow these steps: ### Model Configuration -Rasa allow you to use different models for different components. For example, -you might use one model for intent classification and another for rephrasing. +Many LLM providers offer multiple models through their API. +The model is specified individually for each component, so that if you want to you can use +a combination of various models. -To configure models per component, follow these steps described on the -pages for each component: +```yaml title="config.yml" +recipe: default.v1 +language: en +pipeline: + - name: LLMCommandGenerator + model: "gpt-4" + +policies: + - name: rasa.core.policies.flow_policy.FlowPolicy + - name: rasa_plus.ml.DocsearchPolicy + model: "gpt-3.5-turbo" +``` -1. [intent classification instructions](../../nlu-based-assistants/components.mdx#llmintentclassifier) -2. [rephrasing instructions](../contextual-response-rephraser.mdx#llm-configuration) -3. [intentless policy instructions](../policies.mdx#flow-policy) -4. docsearch instructions ### Additional Configuration for Azure OpenAI Service diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index b7024ff09986..cae9b2f47020 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -6,57 +6,97 @@ description: Learn about model configuration for Rasa. abstract: The configuration file defines the components and policies that your model will use to make predictions based on user input. --- -The recipe key allows for different types of config and model architecture. -Currently, "default.v1" and the experimental "graph.v1" recipes are supported. +import RasaProLabel from '@theme/RasaProLabel'; -:::info New in 3.5 +You can customise many aspects of how Rasa works by modifying the `config.yml` file. -The config file now includes a new mandatory key `assistant_id` which represents the unique assistant identifier. +A minimal configuration for a [CALM](../calm.mdx) assistant looks like this: + +```yaml-rasa title="config.yml" +recipe: default.v1 +language: en +assistant_id: 20230405-114328-tranquil-mustard + +pipeline: + - name: LLMCommandGenerator + +policies: + - name: rasa.core.policies.flow_policy.FlowPolicy +``` + +:::tip Default Configuration +For backwards compatibility, running `rasa init` will create an NLU-based assistant. +To create a CALM assistant with the right `config.yml`, add the +additional `--template` argument: + +```bash +rasa init --template calm +``` ::: -The `assistant_id` key must specify a unique value to distinguish multiple assistants in deployment. -The assistant identifier will be propagated to each event's metadata, alongside the model id. -Note that if the config file does not include this required key or the placeholder default value is not replaced, a random -assistant name will be generated and added to the configuration everytime when running `rasa train`. +### The recipe, language, and assistant_id keys -The language and pipeline keys specify the components used by the model to make NLU predictions. -The policies key defines the policies used by the model to predict the next action. +The `recipe` key only needs to be modified if you want to build a [custom graph recipe](./graph-recipe.mdx). +The vast majority of projects should use the default value `"default.v1"`. +The `language` key is a 2-letter ISO code for the language your assistant supports. -## Suggested Config +The `assistant_id` key should be a unique value and allows you to distinguish multiple +deployed assistants. +This id is added to each event's metadata, together with the model id. +See [event brokers](../production/event-brokers.mdx) for more information. +Note that if the config file does not include this required key or the placeholder default value +is not replaced, a random assistant name will be generated and added to the configuration +every time you run `rasa train`. -TODO: update -You can leave the pipeline and/or policies key out of your configuration file. -When you run `rasa train`, the Suggested Config feature will select a default configuration -for the missing key(s) to train the model. -Make sure to specify the language key in your `config.yml` file with the -2-letter ISO language code. +## Pipeline -Example `config.yml` file: +The `pipeline` key lists the components which will be used to process and understand the messages +that end users send to your assistant. +In a CALM assistant, the output of your pipeline components is a list of [commands](../dialogue-understanding.mdx). -```yaml-rasa (docs/sources/data/configs_for_docs/example_for_suggested_config.yml) +The main component in your pipeline is the `LLMCommandGenerator`. +Here is what an example configuration looks like: + +```yaml-rasa title="config.yml" +pipeline: + - name: LLMCommandGenerator + llm: + model_name: "gpt-4" + request_timeout: 7 + temperature: 0.0 ``` -The selected configuration will also be written as comments into the `config.yml` file, -so you can see which configuration was used. For the example above, the resulting file -might look e.g. like this: +The full set of configurable parameters is listed [here](../dialogue-understanding.mdx). + +All components which make use of LLMs have common configuration parameters which are listed [here](../llm-configuration.mdx) -```yaml-rasa (docs/sources/data/configs_for_docs/example_for_suggested_config_after_train.yml) + +### Combining CALM and NLU-based components + + + +Rasa Pro allows you to combine both NLU-based and CALM components in your pipeline. +See a full list of NLU-based components [here](../buil-based-assistants/components.mdx). + +## Policies + +The `policies` key lists the [dialogue policies](../policies.mdx) your assistant will use +to progress the conversation. + +```yaml-rasa title="config.yml" +policies: + - name: rasa.core.policies.flow_policy.FlowPolicy ``` -If you like, you can then un-comment the suggested configuration for one or both of the -keys and make modifications. Note that this will disable automatic suggestions for this -key when training again. -As long as you leave the configuration commented out and don't specify any configuration -for a key yourself, a default configuration will be suggested whenever you train a new -model. +The `FlowPolicy` currently doesn't have an additional configuration parameters. -:::note nlu- or dialogue- only models +### Combining CALM and NLU-based dialogue policies -Only the default configuration for `pipeline` will be automatically selected -if you run `rasa train nlu`, and only the default configuration for `policies` -will be selected if you run `rasa train core`. -::: + + +Rasa Pro allows you to use both NLU-based and CALM dialogue policies in your assistant. +See a full list of NLU-based policies [here](../buil-based-assistants/policies.mdx). diff --git a/docs/docs/concepts/dialogue-understanding.mdx b/docs/docs/concepts/dialogue-understanding.mdx index cb6e3b7957db..5b55c21b336a 100644 --- a/docs/docs/concepts/dialogue-understanding.mdx +++ b/docs/docs/concepts/dialogue-understanding.mdx @@ -25,6 +25,7 @@ There is currently only one command generator available: the `LLMCommandGenerato To use this component in your bot, you need to add the `LLMCommandGenerator` to your NLU pipeline in the `config.yml` file. +Read more about the `config.yml` file [here](./components/overview.mdx). ```yaml-rasa title="config.yml" pipeline: From 9601417a4167f6b579e765030eb70d03727e6dc2 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Tue, 26 Sep 2023 13:47:56 +0200 Subject: [PATCH 03/14] tutle --- docs/docs/concepts/components/overview.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index cae9b2f47020..36c12d1f3f90 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -1,8 +1,8 @@ --- id: overview -sidebar_label: Overview -title: Model Configuration -description: Learn about model configuration for Rasa. +sidebar_label: Configuration +title: Configuration +description: Configure your Rasa Assistant. abstract: The configuration file defines the components and policies that your model will use to make predictions based on user input. --- From 88201e22c9b58859f2b65bd95a6ee3e92b7e968f Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 10:03:14 +0200 Subject: [PATCH 04/14] moved custom llm components page to reference --- docs/docs/concepts/components/llm-custom.mdx | 2 +- docs/sidebars.js | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docs/concepts/components/llm-custom.mdx b/docs/docs/concepts/components/llm-custom.mdx index 895eb55b342c..9a3660f409d5 100644 --- a/docs/docs/concepts/components/llm-custom.mdx +++ b/docs/docs/concepts/components/llm-custom.mdx @@ -1,6 +1,6 @@ --- id: llm-custom -sidebar_label: Customization +sidebar_label: Customizing LLM Components title: Customizing LLM based Components abstract: --- diff --git a/docs/sidebars.js b/docs/sidebars.js index fd63d377c8c9..5786ecd50747 100644 --- a/docs/sidebars.js +++ b/docs/sidebars.js @@ -63,7 +63,6 @@ module.exports = { items: [ "concepts/components/overview", "concepts/components/llm-configuration", - "concepts/components/llm-custom", ], }, "concepts/policies", // TODO: ENG-538 @@ -256,10 +255,11 @@ module.exports = { collapsed: true, items: [ "nlu-based-assistants/glossary", - "telemetry/telemetry", - "telemetry/reference", "concepts/components/custom-graph-components", + "concepts/components/llm-custom", "concepts/components/graph-recipe", + "telemetry/telemetry", + "telemetry/reference", require("./docs/reference/sidebar.json"), ], }, From 57828f19695c1b3f9bea2059b07af9445a717b2b Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 11:02:42 +0200 Subject: [PATCH 05/14] fix typo --- docs/docs/concepts/components/overview.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index 36c12d1f3f90..12dcf358ae56 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -80,7 +80,7 @@ All components which make use of LLMs have common configuration parameters which Rasa Pro allows you to combine both NLU-based and CALM components in your pipeline. -See a full list of NLU-based components [here](../buil-based-assistants/components.mdx). +See a full list of NLU-based components [here](../nlu-based-assistants/components.mdx). ## Policies @@ -99,4 +99,4 @@ The `FlowPolicy` currently doesn't have an additional configuration parameters. Rasa Pro allows you to use both NLU-based and CALM dialogue policies in your assistant. -See a full list of NLU-based policies [here](../buil-based-assistants/policies.mdx). +See a full list of NLU-based policies [here](../nlu-based-assistants/policies.mdx). From bb944ccbbf885b68e910f5a0452d3aa869a12e31 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:19:19 +0200 Subject: [PATCH 06/14] Update docs/docs/concepts/components/overview.mdx Co-authored-by: Maxime Vdb --- docs/docs/concepts/components/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index 12dcf358ae56..ac2995042790 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -56,7 +56,7 @@ every time you run `rasa train`. The `pipeline` key lists the components which will be used to process and understand the messages that end users send to your assistant. -In a CALM assistant, the output of your pipeline components is a list of [commands](../dialogue-understanding.mdx). +In a CALM assistant, the output of your components pipeline is a list of [commands](../dialogue-understanding.mdx). The main component in your pipeline is the `LLMCommandGenerator`. Here is what an example configuration looks like: From 21f0db20b76406834804cec891090158f8453247 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:19:44 +0200 Subject: [PATCH 07/14] Update docs/sidebars.js Co-authored-by: Maxime Vdb --- docs/sidebars.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sidebars.js b/docs/sidebars.js index 5786ecd50747..ed198b974248 100644 --- a/docs/sidebars.js +++ b/docs/sidebars.js @@ -259,7 +259,7 @@ module.exports = { "concepts/components/llm-custom", "concepts/components/graph-recipe", "telemetry/telemetry", - "telemetry/reference", + "telemetry/reference", require("./docs/reference/sidebar.json"), ], }, From e479e9cc5010c95fbab58f7cafcfb8c17d6f993e Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:19:54 +0200 Subject: [PATCH 08/14] Update docs/docs/concepts/components/llm-configuration.mdx Co-authored-by: Maxime Vdb --- docs/docs/concepts/components/llm-configuration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/concepts/components/llm-configuration.mdx b/docs/docs/concepts/components/llm-configuration.mdx index a825e5ace6db..e63bf70c3270 100644 --- a/docs/docs/concepts/components/llm-configuration.mdx +++ b/docs/docs/concepts/components/llm-configuration.mdx @@ -13,8 +13,8 @@ abstract: | All Rasa components which make use of an LLM can be configured. This includes: -* Which LLM provider to use -* The model you want to use +* The LLM provider +* The model * The sampling temperature * The prompt template From 74d845e48983997cbd82045a27bbad9ca05c7c2b Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:20:07 +0200 Subject: [PATCH 09/14] Update docs/docs/concepts/components/llm-configuration.mdx Co-authored-by: Maxime Vdb --- docs/docs/concepts/components/llm-configuration.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docs/concepts/components/llm-configuration.mdx b/docs/docs/concepts/components/llm-configuration.mdx index e63bf70c3270..58f3a68dcf3c 100644 --- a/docs/docs/concepts/components/llm-configuration.mdx +++ b/docs/docs/concepts/components/llm-configuration.mdx @@ -77,7 +77,8 @@ To configure the API token, follow these steps: Many LLM providers offer multiple models through their API. The model is specified individually for each component, so that if you want to you can use -a combination of various models. +a combination of various models. For instance here is how you could configure a different model +for the `LLMCommandGenerator` and the `DocsearchPolicy`: ```yaml title="config.yml" recipe: default.v1 From 9f84a0ce000b592878d635890c92cc7a8ac81782 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:20:21 +0200 Subject: [PATCH 10/14] Update docs/docs/concepts/components/overview.mdx Co-authored-by: Maxime Vdb --- docs/docs/concepts/components/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index ac2995042790..1fc206ae71bc 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -37,7 +37,7 @@ rasa init --template calm ### The recipe, language, and assistant_id keys -The `recipe` key only needs to be modified if you want to build a [custom graph recipe](./graph-recipe.mdx). +The `recipe` key only needs to be modified if you want to use a [custom graph recipe](./graph-recipe.mdx). The vast majority of projects should use the default value `"default.v1"`. The `language` key is a 2-letter ISO code for the language your assistant supports. From 4098485cf77aab0995cac05cd4ed64293f34b05b Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:25:07 +0200 Subject: [PATCH 11/14] review comments --- docs/docs/concepts/components/overview.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index 1fc206ae71bc..4c1328ffa5b7 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -7,6 +7,7 @@ abstract: The configuration file defines the components and policies that your m --- import RasaProLabel from '@theme/RasaProLabel'; +import RasaProBanner from "@theme/RasaProBanner"; You can customise many aspects of how Rasa works by modifying the `config.yml` file. @@ -79,6 +80,8 @@ All components which make use of LLMs have common configuration parameters which + + Rasa Pro allows you to combine both NLU-based and CALM components in your pipeline. See a full list of NLU-based components [here](../nlu-based-assistants/components.mdx). @@ -92,11 +95,13 @@ policies: - name: rasa.core.policies.flow_policy.FlowPolicy ``` -The `FlowPolicy` currently doesn't have an additional configuration parameters. +The [FlowPolicy](../policies.mdx#flow-policy) currently doesn't have an additional configuration parameters. ### Combining CALM and NLU-based dialogue policies + + Rasa Pro allows you to use both NLU-based and CALM dialogue policies in your assistant. See a full list of NLU-based policies [here](../nlu-based-assistants/policies.mdx). From 1c7fcea6285bcc90f0a2d883e0331f5dd9c5aea1 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:36:04 +0200 Subject: [PATCH 12/14] fix links --- docs/docs/concepts/components/overview.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index 4c1328ffa5b7..955fad25989b 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -11,7 +11,7 @@ import RasaProBanner from "@theme/RasaProBanner"; You can customise many aspects of how Rasa works by modifying the `config.yml` file. -A minimal configuration for a [CALM](../calm.mdx) assistant looks like this: +A minimal configuration for a [CALM](../../calm.mdx) assistant looks like this: ```yaml-rasa title="config.yml" recipe: default.v1 @@ -46,7 +46,7 @@ The `language` key is a 2-letter ISO code for the language your assistant suppor The `assistant_id` key should be a unique value and allows you to distinguish multiple deployed assistants. This id is added to each event's metadata, together with the model id. -See [event brokers](../production/event-brokers.mdx) for more information. +See [event brokers](../../production/event-brokers.mdx) for more information. Note that if the config file does not include this required key or the placeholder default value is not replaced, a random assistant name will be generated and added to the configuration every time you run `rasa train`. @@ -73,7 +73,7 @@ pipeline: The full set of configurable parameters is listed [here](../dialogue-understanding.mdx). -All components which make use of LLMs have common configuration parameters which are listed [here](../llm-configuration.mdx) +All components which make use of LLMs have common configuration parameters which are listed [here](./llm-configuration.mdx) ### Combining CALM and NLU-based components @@ -83,7 +83,7 @@ All components which make use of LLMs have common configuration parameters which Rasa Pro allows you to combine both NLU-based and CALM components in your pipeline. -See a full list of NLU-based components [here](../nlu-based-assistants/components.mdx). +See a full list of NLU-based components [here](../../nlu-based-assistants/components.mdx). ## Policies @@ -104,4 +104,4 @@ The [FlowPolicy](../policies.mdx#flow-policy) currently doesn't have an addition Rasa Pro allows you to use both NLU-based and CALM dialogue policies in your assistant. -See a full list of NLU-based policies [here](../nlu-based-assistants/policies.mdx). +See a full list of NLU-based policies [here](../../nlu-based-assistants/policies.mdx). From 23da906c3155250699675cbe0d2e3a2b1d3a66b3 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Thu, 28 Sep 2023 13:49:28 +0200 Subject: [PATCH 13/14] fix hierarchy test --- docs/docs/concepts/components/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/concepts/components/overview.mdx b/docs/docs/concepts/components/overview.mdx index 955fad25989b..3f7dca576c3c 100644 --- a/docs/docs/concepts/components/overview.mdx +++ b/docs/docs/concepts/components/overview.mdx @@ -36,7 +36,7 @@ rasa init --template calm ::: -### The recipe, language, and assistant_id keys +## The recipe, language, and assistant_id keys The `recipe` key only needs to be modified if you want to use a [custom graph recipe](./graph-recipe.mdx). The vast majority of projects should use the default value `"default.v1"`. From 5052c54aaa77c816854f228a1cd44cb81568b873 Mon Sep 17 00:00:00 2001 From: Alan Nichol Date: Tue, 17 Oct 2023 14:57:08 +0200 Subject: [PATCH 14/14] put custom components info back in components section --- docs/sidebars.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sidebars.js b/docs/sidebars.js index ed198b974248..865e1b7fa7b2 100644 --- a/docs/sidebars.js +++ b/docs/sidebars.js @@ -63,6 +63,9 @@ module.exports = { items: [ "concepts/components/overview", "concepts/components/llm-configuration", + "concepts/components/custom-graph-components", + "concepts/components/llm-custom", + "concepts/components/graph-recipe", ], }, "concepts/policies", // TODO: ENG-538 @@ -255,9 +258,6 @@ module.exports = { collapsed: true, items: [ "nlu-based-assistants/glossary", - "concepts/components/custom-graph-components", - "concepts/components/llm-custom", - "concepts/components/graph-recipe", "telemetry/telemetry", "telemetry/reference", require("./docs/reference/sidebar.json"),