fixed links

CHANGELOG.mdx

@@ -1827,10 +1827,10 @@ Upgrade dependent libraries with security vulnerabilities (Pillow, TensorFlow, u
 
 ### Bugfixes
 
-- [#8364](https://github.com/rasahq/rasa/issues/8364): Fixed a bug where [`ListSlot`](./concepts/domain.mdx#list-slot)s were filled with single items
+- [#8364](https://github.com/rasahq/rasa/issues/8364): Fixed a bug where [`ListSlot`](./building-classic-assistants/domain.mdx#list-slot)s were filled with single items
   in case only one matching entity was extracted for this slot.
 
-  Values applied to [`ListSlot`](./concepts/domain.mdx#list-slot)s will be converted to a `List`
+  Values applied to [`ListSlot`](./building-classic-assistants/domain.mdx#list-slot)s will be converted to a `List`
   in case they aren't one.
 
 - [#8581](https://github.com/rasahq/rasa/issues/8581): Fix bug with false rule conflicts

docs/docs/action-server/validation-action.mdx

@@ -23,7 +23,7 @@ can be set or updated outside of a form context.
 :::note
 `ValidationAction` is intended for extracting slots **outside** the context of a form.
 It will ignore extraction and validation methods for any slots that have a form specified under the
-[slot mapping's `conditions`](../concepts/domain.mdx#mapping-conditions).
+[slot mapping's `conditions`](../building-classic-assistants/domain.mdx#mapping-conditions).
 It will not run these methods when the specified form is active nor when no form is active.
 Please extend the [`FormValidationAction`](./validation-action.mdx#formvalidationaction-class) class to apply
 custom slot mappings only within the context of a form.

docs/docs/building-classic-assistants/business-logic.mdx

@@ -35,7 +35,7 @@ The examples on this page come from the [formbot example bot](https://github.com
 ## Step-by-step Guide on Using Forms to Handle Business Logic
 
 [Forms](./forms.mdx) work by prompting the user for information until it has gathered all required information.
-The information is stored in [slots](../concepts/domain.mdx#slots). Once all the required slots are filled,
+The information is stored in [slots](./domain.mdx#slots). Once all the required slots are filled,
 the bot fulfills the user's original request.
 
 ### 1. Defining the form
@@ -65,7 +65,7 @@ forms:
         - outdoor_seating
 ```
 
-These slots need to be added to your domain's `slots` section, along with [slot mappings](../concepts/domain.mdx#slot-mappings) which define how the slots can be filled. For any slot filled `from_entity`, the entity also needs to be added
+These slots need to be added to your domain's `slots` section, along with [slot mappings](./domain.mdx#slot-mappings) which define how the slots can be filled. For any slot filled `from_entity`, the entity also needs to be added
 to the domain. Slots filled by forms should usually not influence
 the conversation, so set `influence_conversation` to `false:
 
@@ -122,7 +122,7 @@ filled based on the user's intent: If it is `affirm`, it'll be `true`, if it is
 However, the slot should only be set to `true` or `false` if the user was responding to the question, `Do you want to sit outside?`.
 To enforce this condition, the `conditions` for the `outdoor_seating` slot requires that `restaurant_form` is active and that the requested slot is `outdoor_seating`.
 If there were no conditions and the user had sent a message with the `affirm` or `deny` intent earlier in the conversation,
-the `outdoor_seating` slot would already be filled when the form was activated. Therefore the form would not prompt the user for their outdoor seating preference. See [mapping conditions](../concepts/domain.mdx#mapping-conditions) for more information.
+the `outdoor_seating` slot would already be filled when the form was activated. Therefore the form would not prompt the user for their outdoor seating preference. See [mapping conditions](./domain.mdx#mapping-conditions) for more information.
 
 #### Validating Slots
 
@@ -135,7 +135,7 @@ about validation actions.
 #### Requesting Slots
 
 To specify how the bot should ask for the required information,
-you define [`responses`](../concepts/domain.mdx#responses) called `utter_ask_{slotname}` in your domain:
+you define [`responses`](./domain.mdx#responses) called `utter_ask_{slotname}` in your domain:
 
 ```yaml-rasa title="domain.yml"
 responses:
@@ -149,7 +149,7 @@ responses:
 
 ### 2. Updating the configuration
 
-A form's [happy path](../concepts/glossary.mdx#happy--unhappy-paths) should be defined as a [rule](rules.mdx) which means you'll need to add the [RulePolicy](./policies.mdx#rule-policy)
+A form's [happy path](./glossary.mdx#happy--unhappy-paths) should be defined as a [rule](rules.mdx) which means you'll need to add the [RulePolicy](./policies.mdx#rule-policy)
 to your policies:
 
 ```yaml-rasa title="config.yml"

docs/docs/building-classic-assistants/chitchat-faqs.mdx

@@ -5,7 +5,7 @@ title: Chitchat and FAQs
 abstract: FAQ assistants are the simplest assistants to build and typically the first kind of assistant anyone builds. This page is a guide to the concepts and training data you need to handle non-contextual questions like FAQs and chitchat.
 ---
 
-[FAQs](../concepts/glossary.mdx#faqs) and [chitchat](../concepts/glossary.mdx#chitchat) are two cases where the conversational assistant responds with a fixed set of messages, and the assistant should always answer the same way,
+[FAQs](./glossary.mdx#faqs) and [chitchat](./glossary.mdx#chitchat) are two cases where the conversational assistant responds with a fixed set of messages, and the assistant should always answer the same way,
 no matter what has happened previously in the conversation.
 For example, in the following conversation, every question can be asked at any point in the conversation,
 with the answer being independent of anything the user has said previously.
@@ -82,7 +82,7 @@ pipeline:
 
 Consider an example where you have 20 different FAQs. Although each question is represented as an individual intent, all FAQ intents are handled the same way in the dialogue. For each FAQ intent, the assistant **retrieves** the proper response depending on which question has been asked.
 
-Instead of writing 20 rules, you can use a single action, e.g. `utter_faq` to handle all FAQs with a single rule by grouping them together under a single [retrieval intent](../concepts/glossary.mdx#retrieval-intent)
+Instead of writing 20 rules, you can use a single action, e.g. `utter_faq` to handle all FAQs with a single rule by grouping them together under a single [retrieval intent](./glossary.mdx#retrieval-intent)
 called e.g. `faq`.
 
 The single action uses the output of the
@@ -144,7 +144,7 @@ intents:
 
 Responses for the ResponseSelector follow the same naming convention as
 retrieval intents. Besides this, they can have all the characteristics of
-normal bot [response](../concepts/domain.mdx#responses). For the chitchat intents
+normal bot [response](./domain.mdx#responses). For the chitchat intents
 listed above, our responses could look like:
 
 ```yaml-rasa title="domain.yml"

docs/docs/building-classic-assistants/components.mdx

@@ -568,7 +568,7 @@ Note: The `feature-dimension` for sequence and sentence features does not have t
   **Configuring for incremental training**
 
   To ensure that `sparse_features` are of fixed size during
-  [incremental training](../concepts/command-line-interface.mdx#incremental-training), the
+  [incremental training](../command-line-interface.mdx#incremental-training), the
   component should be configured to account for additional patterns that may be
   added to the training data in future. To do so, configure the `number_additional_patterns`
   parameter while training the base model from scratch:
@@ -703,7 +703,7 @@ Note: The `feature-dimension` for sequence and sentence features does not have t
   **Configuring for incremental training**
 
   To ensure that `sparse_features` are of fixed size during
-  [incremental training](../concepts/command-line-interface.mdx#incremental-training), the
+  [incremental training](../command-line-interface.mdx#incremental-training), the
   component should be configured to account for additional vocabulary tokens
   that may be added as part of new training examples in the future.
   To do so, configure the `additional_vocabulary_size` parameter while training the base model from scratch:
@@ -2435,7 +2435,7 @@ Selectors predict a bot response from a set of candidate responses.
   It embeds user inputs and response labels into the same space and follows the exact same
   neural network architecture and optimization as the [DIETClassifier](./components.mdx#dietclassifier).
 
-  To use this component, your training data should contain [retrieval intents](../concepts/glossary.mdx#retrieval-intent). To define these,
+  To use this component, your training data should contain [retrieval intents](./glossary.mdx#retrieval-intent). To define these,
   checkout [documentation on NLU training examples](./training-data-format.mdx#training-examples) and
   [documentation on defining response utterances for retrieval intents](../concepts/responses.mdx#defining-responses).
 
@@ -2706,5 +2706,5 @@ pipeline:
 - name: "sentiment.SentimentAnalyzer"
 ```
 
-See the [guide on custom graph components](../concepts/custom-graph-components.mdx) for a complete guide on custom components.
+See the [guide on custom graph components](../concepts/components/custom-graph-components.mdx) for a complete guide on custom components.
 Also be sure to read the section on the [Component Lifecycle](./tuning-your-model.mdx#component-lifecycle).

docs/docs/building-classic-assistants/domain.mdx

@@ -17,7 +17,7 @@ Here is a full example of a domain, taken from the
 The domain can be defined as a single YAML file or split across multiple files in a directory.
 When split across multiple files, the domain contents will be read and automatically merged together.
 
-Using the [command line interface](./command-line-interface.mdx#rasa-train),
+Using the [command line interface](../command-line-interface.mdx#rasa-train),
 you can train a model with split domain files by running:
 
 ```bash
@@ -733,7 +733,7 @@ if it is empty when the form is activated.
 
 ### Custom Slot Mappings
 
-You can define custom slot mappings using [slot validation actions](./concepts/slot-validation-actions.mdx) when none of the
+You can define custom slot mappings using [slot validation actions](../concepts/slot-validation-actions.mdx) when none of the
 predefined mappings fit your use case. You must define this slot mapping to be of type `custom`, for example:
 
 ```yaml
@@ -776,7 +776,7 @@ slots:
 Responses are actions that send a message to a user without running any custom code or
 returning events. These responses can be defined directly in the domain file under the `responses` key
 and can include rich content such as buttons and attachments. For more information on responses and how to define them,
-see [Responses](./concepts/responses.mdx).
+see [Responses](../concepts/responses.mdx).
 
 ## Forms
 
@@ -786,7 +786,7 @@ For more information on form and how to define them, see [Forms](../building-cla
 
 ## Actions
 
-[Actions](./concepts/actions.mdx) are the things your bot can actually do.
+[Actions](../concepts/actions.mdx) are the things your bot can actually do.
 For example, an action could:
 
 - respond to a user,
@@ -797,7 +797,7 @@ For example, an action could:
 
 - just about anything!
 
-All [custom actions](./concepts/custom-actions.mdx) should be listed in your domain, except responses which need not be listed
+All [custom actions](../concepts/custom-actions.mdx) should be listed in your domain, except responses which need not be listed
 under `actions:` as they are already listed under `responses:`.
 
 ### Select which actions should receive domain
@@ -872,7 +872,7 @@ implementation moves all existing slots into the new session. Note that all
 conversations begin with an `action_session_start`. Overriding this action could
 for instance be used to initialize the tracker with slots from an external API
 call, or to start the conversation with a bot message. The docs on
-[Customizing the session start action](./concepts/default-actions.mdx#customization) shows you how to do that.
+[Customizing the session start action](../concepts/default-actions.mdx#customization) shows you how to do that.
 
 :::
 

docs/docs/building-classic-assistants/forms.mdx

@@ -19,7 +19,7 @@ policies:
 
 ### Defining a Form
 
-Define a form by adding it to the `forms` section in your [domain](../concepts/domain.mdx).
+Define a form by adding it to the `forms` section in your [domain](./domain.mdx).
 The name of the form is also the name of the action which you can use in
 [stories](./stories.mdx) or [rules](./rules.mdx) to handle form executions.
 You will need to specify a list of slot names to the mandatory `required_slots` key.
@@ -141,12 +141,12 @@ write stories or rules for this case.
 ### Slot Mappings
 
 :::caution Changed in 3.0
-As of 3.0, [slot mappings](../concepts/domain.mdx#slot-mappings) are defined in the `slots` section of the domain.
+As of 3.0, [slot mappings](./domain.mdx#slot-mappings) are defined in the `slots` section of the domain.
 This change allows the same slot mapping to be reused across multiple forms, removing any unnecessary duplication.
 Please follow the [migration guide](../migration-guide.mdx#slot-mappings) to update your assistant.
 
-Note specifically the role of [Mapping Conditions](../concepts/domain.mdx#mapping-conditions) and the
-[unique entity mapping](../concepts/domain.mdx#unique-from_entity-mapping-matching) constraint.
+Note specifically the role of [Mapping Conditions](./domain.mdx#mapping-conditions) and the
+[unique entity mapping](./domain.mdx#unique-from_entity-mapping-matching) constraint.
 :::
 
 ### Writing Stories / Rules for Unhappy Form Paths
@@ -291,7 +291,7 @@ The `slots_mapped_in_domain` argument provided to the `required_slots` method of
 has been replaced by the `domain_slots` argument, please update your custom actions to the new argument name.
 :::
 
-If none of the predefined [Slot Mappings](../concepts/domain.mdx#slot-mappings) fit your use
+If none of the predefined [Slot Mappings](./domain.mdx#slot-mappings) fit your use
 case, you can use the
 [Custom Action](../concepts/actions.mdx#custom-actions) `validate_<form_name>` to write your own
 extraction code. Rasa will trigger this action when the form is run.
@@ -421,7 +421,7 @@ class ValidateBookingForm(FormValidationAction):
 ### The requested_slot slot
 
 The slot `requested_slot` is automatically added to the domain as a
-slot of type [`text`](../concepts/domain.mdx#text-slot). The value of the `requested_slot` will be
+slot of type [`text`](./domain.mdx#text-slot). The value of the `requested_slot` will be
 ignored during conversations. If you want to change this behavior, you need to add
 the `requested_slot` to your domain file as a categorical slot with
 `influence_conversation` set to `true`.

docs/docs/building-classic-assistants/glossary.mdx

@@ -5,7 +5,7 @@ title: Rasa Glossary
 description: Glossary for all Rasa-related terms
 ---
 
-## [Action](./actions.mdx)
+## [Action](../concepts/custom-actions.mdx)
 
 A single step that a bot takes in a conversation (e.g. calling an API or sending a response back to the user).
 
@@ -50,15 +50,15 @@ An element in the an assistant's [NLU pipeline](../building-classic-assistants/t
 
 Incoming messages are processed by a sequence of components called a pipeline. A component can perform tasks ranging from entity extraction to intent classification to pre-processing.
 
-## [Conditional Response Variation](./responses.mdx#conditional-response-variations)
+## [Conditional Response Variation](../concepts/responses.mdx#conditional-response-variations)
 
 Response variation that can only be used when the current dialogue state satisfies some constraints as defined in the domain or responses files. If there's a match between the constraints and the dialogue state, Rasa can use this variation.
 
-## [Custom Action](./actions.mdx#custom-actions)
+## [Custom Action](../concepts/custom-actions.mdx)
 
 An action written by a bot developer that can run arbitrary code, mainly to interact with external systems and APIs.
 
-## [Default Action](./actions.mdx#default-actions)
+## [Default Action](../concepts/default-actions.mdx)
 
 A built-in action that comes with predefined functionality.
 
@@ -166,7 +166,7 @@ A special type of intent that can be divided into smaller sub-intents. For examp
 
 A messaging channel used to build custom connectors. Includes an input channel, where user messages can be posted to Rasa, and the ability to specify a callback URL, where the bot’s response actions will be sent.
 
-## [Response / Template / Utterance](./responses.mdx)
+## [Response / Template / Utterance](../concepts/responses.mdx)
 
 A message that an assistant sends to a user. This can include text, buttons, images, and other content.
 
@@ -188,7 +188,7 @@ Training data format for the dialogue model, consisting of a conversation betwee
 
 Transformer Embedding Dialogue Policy. TED is the default machine learning-based dialogue policy used by Rasa. TED complements rule-based policies by handling previously unseen situations, where no rule exists to determine the next action.
 
-## [Template / Response / Utterance](./responses.mdx)
+## [Template / Response / Utterance](../concepts/responses.mdx)
 
 A message template used to respond to a user. Can include text, buttons, images, and other attachments.