proper links

lukegalbraithrussell · lukegalbraithrussell · commit 68bd0f15a79d · 2025-08-04T10:56:01.000-07:00
diff --git a/docs/english/concepts/acknowledge.md b/docs/english/concepts/acknowledge.md
@@ -1,7 +1,7 @@
 ---
 title: Acknowledging requests
 lang: en
-slug: /concepts/acknowledge
+slug: /bolt-python/concepts/acknowledge
 ---
 
 Actions, commands, shortcuts, options requests, and view submissions must **always** be acknowledged using the `ack()` function. This lets Slack know that the request was received so that it may update the Slack user interface accordingly.
diff --git a/docs/english/concepts/actions.md b/docs/english/concepts/actions.md
@@ -1,7 +1,7 @@
 ---
 title: Listening & responding to actions
 lang: en
-slug: /concepts/actions
+slug: /bolt-python/concepts/actions
 ---
 
 Your app can listen and respond to user actions, like button clicks, and menu selects, using the `action` method.
diff --git a/docs/english/concepts/adapters.md b/docs/english/concepts/adapters.md
@@ -1,7 +1,7 @@
 ---
 title: Adapters
 lang: en
-slug: /concepts/adapters
+slug: /bolt-python/concepts/adapters
 ---
 
 Adapters are responsible for handling and parsing incoming requests from Slack to conform to [`BoltRequest`](https://github.com/slackapi/bolt-python/blob/main/slack_bolt/request/request.py), then dispatching those requests to your Bolt app.
diff --git a/docs/english/concepts/ai-apps.md b/docs/english/concepts/ai-apps.md
@@ -1,7 +1,7 @@
 ---
 title: Using AI in Apps
 lang: en
-slug: /concepts/ai-apps
+slug: /bolt-python/concepts/ai-apps
 ---
 
 :::info This feature requires a paid plan
diff --git a/docs/english/concepts/app-home.md b/docs/english/concepts/app-home.md
@@ -1,7 +1,7 @@
 ---
 title: Publishing views to App Home
 lang: en
-slug: /concepts/app-home
+slug: /bolt-python/concepts/app-home
 ---
 
 [Home tabs](/surfaces/app-home) are customizable surfaces accessible via the sidebar and search that allow apps to display views on a per-user basis. After enabling App Home within your app configuration, home tabs can be published and updated by passing a `user_id` and [view payload](/reference/interaction-payloads/view-interactions-payload/#view_submission) to the [`views.publish`](/reference/methods/views.publis) method.
diff --git a/docs/english/concepts/async.md b/docs/english/concepts/async.md
@@ -1,7 +1,7 @@
 ---
 title: Using async (asyncio)
 lang: en
-slug: /concepts/async
+slug: /bolt-python/concepts/async
 ---
 
 To use the async version of Bolt, you can import and initialize an `AsyncApp` instance (rather than `App`). `AsyncApp` relies on [AIOHTTP](https://docs.aiohttp.org) to make API requests, which means you'll need to install `aiohttp` (by adding to `requirements.txt` or running `pip install aiohttp`).
diff --git a/docs/english/concepts/authenticating-oauth.md b/docs/english/concepts/authenticating-oauth.md
@@ -1,7 +1,7 @@
 ---
 title: Authenticating with OAuth
 lang: en
-slug: /concepts/authenticating-oauth
+slug: /bolt-python/concepts/authenticating-oauth
 ---
 
 Slack apps installed on multiple workspaces will need to implement OAuth, then store installation information (like access tokens) securely. By providing `client_id`, `client_secret`, `scopes`, `installation_store`, and `state_store` when initializing App, Bolt for Python will handle the work of setting up OAuth routes and verifying state. If you're implementing a custom adapter, you can make use of our [OAuth library](/python-slack-sdk/oauth/), which is what Bolt for Python uses under the hood.
diff --git a/docs/english/concepts/authorization.md b/docs/english/concepts/authorization.md
@@ -1,7 +1,7 @@
 ---
 title: Authorization
 lang: en
-slug: /concepts/authorization
+slug: /bolt-python/concepts/authorization
 ---
 
 Authorization is the process of determining which Slack credentials should be available while processing an incoming Slack request.
diff --git a/docs/english/concepts/commands.md b/docs/english/concepts/commands.md
@@ -1,7 +1,7 @@
 ---
 title: Listening & responding to commands
 lang: en
-slug: /concepts/commands
+slug: /bolt-python/concepts/commands
 ---
 
 Your app can use the `command()` method to listen to incoming slash command requests. The method requires a `command_name` of type `str`.
diff --git a/docs/english/concepts/context.md b/docs/english/concepts/context.md
@@ -1,7 +1,7 @@
 ---
 title: Adding context
 lang: en
-slug: /concepts/context
+slug: /bolt-python/concepts/context
 ---
 
 All listeners have access to a `context` dictionary, which can be used to enrich requests with additional information. Bolt automatically attaches information that is included in the incoming request, like `user_id`, `team_id`, `channel_id`, and `enterprise_id`.
diff --git a/docs/english/concepts/custom-adapters.md b/docs/english/concepts/custom-adapters.md
@@ -1,7 +1,7 @@
 ---
 title: Custom adapters
 lang: en
-slug: /concepts/custom-adapters
+slug: /bolt-python/concepts/custom-adapters
 ---
 
 [Adapters](/bolt-python/concepts/adapters) are flexible and can be adjusted based on the framework you prefer. There are two necessary components of adapters:
diff --git a/docs/english/concepts/custom-steps.md b/docs/english/concepts/custom-steps.md
@@ -2,7 +2,7 @@
 title: Listening and responding to custom steps
 sidebar_label: Custom Steps
 lang: en
-slug: /concepts/custom-steps
+slug: /bolt-python/concepts/custom-steps
 ---
 
 Your app can use the `function()` method to listen to incoming [custom step requests](/workflows/workflow-steps). Custom steps are used in Workflow Builder to build workflows. The method requires a step `callback_id` of type `str`. This `callback_id` must also be defined in your [Function](/reference/app-manifest#functions) definition. Custom steps must be finalized using the `complete()` or `fail()` listener arguments to notify Slack that your app has processed the request.
diff --git a/docs/english/concepts/errors.md b/docs/english/concepts/errors.md
@@ -1,7 +1,7 @@
 ---
 title: Handling errors
 lang: en
-slug: /concepts/errors
+slug: /bolt-python/concepts/errors
 ---
 
 If an error occurs in a listener, you can handle it directly using a try/except block. Errors associated with your app will be of type `BoltError`. Errors associated with calling Slack APIs will be of type `SlackApiError`.
diff --git a/docs/english/concepts/event-listening.md b/docs/english/concepts/event-listening.md
@@ -1,7 +1,7 @@
 ---
 title: Listening to events
 lang: en
-slug: /concepts/event-listening
+slug: /bolt-python/concepts/event-listening
 ---
 
 You can listen to [any Events API event](/reference/events) using the `event()` method after subscribing to it in your app configuration. This allows your app to take action when something happens in a workspace where it's installed, like a user reacting to a message or joining a channel.
diff --git a/docs/english/concepts/global-middleware.md b/docs/english/concepts/global-middleware.md
@@ -1,7 +1,7 @@
 ---
 title: Global middleware
 lang: en
-slug: /concepts/global-middleware
+slug: /bolt-python/concepts/global-middleware
 ---
 
 Global middleware is run for all incoming requests, before any listener middleware. You can add any number of global middleware to your app by passing middleware functions to `app.use()`. Middleware functions are called with the same arguments as listeners, with an additional `next()` function.
diff --git a/docs/english/concepts/lazy-listeners.md b/docs/english/concepts/lazy-listeners.md
@@ -1,7 +1,7 @@
 ---
 title: Lazy listeners (FaaS)
 lang: en
-slug: /concepts/lazy-listeners
+slug: /bolt-python/concepts/lazy-listeners
 ---
 
 Lazy Listeners are a feature which make it easier to deploy Slack apps to FaaS (Function-as-a-Service) environments. Please note that this feature is only available in Bolt for Python, and we are not planning to add the same to other Bolt frameworks.
diff --git a/docs/english/concepts/listener-middleware.md b/docs/english/concepts/listener-middleware.md
@@ -1,7 +1,7 @@
 ---
 title: Listener middleware
 lang: en
-slug: /concepts/listener-middleware
+slug: /bolt-python/concepts/listener-middleware
 ---
 
 Listener middleware is only run for the listener in which it's passed. You can pass any number of middleware functions to the listener using the `middleware` parameter, which must be a list that contains one to many middleware functions.
diff --git a/docs/english/concepts/logging.md b/docs/english/concepts/logging.md
@@ -1,7 +1,7 @@
 ---
 title: Logging
 lang: en
-slug: /concepts/logging
+slug: /bolt-python/concepts/logging
 ---
 
 By default, Bolt will log information from your app to the output destination. After you've imported the `logging` module, you can customize the root log level by passing the `level` parameter to `basicConfig()`. The available log levels in order of least to most severe are `debug`, `info`, `warning`, `error`, and `critical`.
diff --git a/docs/english/concepts/message-listening.md b/docs/english/concepts/message-listening.md
@@ -1,7 +1,7 @@
 ---
 title: Listening to messages
 lang: en
-slug: /concepts/message-listening
+slug: /bolt-python/concepts/message-listening
 ---
 
 To listen to messages that [your app has access to receive](/messaging/retrieving-messages), you can use the `message()` method which filters out events that aren't of type `message`.
diff --git a/docs/english/concepts/message-sending.md b/docs/english/concepts/message-sending.md
@@ -1,7 +1,7 @@
 ---
 title: Sending messages
 lang: en
-slug: /concepts/message-sending
+slug: /bolt-python/concepts/message-sending
 ---
 
 Within your listener function, `say()` is available whenever there is an associated conversation (for example, a conversation where the event or action which triggered the listener occurred). `say()` accepts a string to post simple messages and JSON payloads to send more complex messages. The message payload you pass in will be sent to the associated conversation.
diff --git a/docs/english/concepts/opening-modals.md b/docs/english/concepts/opening-modals.md
@@ -1,7 +1,7 @@
 ---
 title: Opening modals
 lang: en
-slug: /concepts/opening-modals
+slug: /bolt-python/concepts/opening-modals
 ---
 
 [Modals](/surfaces/modals) are focused surfaces that allow you to collect user data and display dynamic information. You can open a modal by passing a valid `trigger_id` and a [view payload](/reference/interaction-payloads/view-interactions-payload/#view_submission) to the built-in client's [`views.open`](/reference/methods/views.open/) method. 
diff --git a/docs/english/concepts/select-menu-options.md b/docs/english/concepts/select-menu-options.md
@@ -1,7 +1,7 @@
 ---
 title: Listening & responding to select menu options
 lang: en
-slug: /concepts/options
+slug: /bolt-python/concepts/options
 ---
 
 The `options()` method listens for incoming option request payloads from Slack. [Similar to `action()`](/bolt-python/concepts/action-listening),
diff --git a/docs/english/concepts/shortcuts.md b/docs/english/concepts/shortcuts.md
@@ -1,7 +1,7 @@
 ---
 title: Listening & responding to shortcuts
 lang: en
-slug: /concepts/shortcuts
+slug: /bolt-python/concepts/shortcuts
 ---
 
 The `shortcut()` method supports both [global shortcuts](/interactivity/implementing-shortcuts#global) and [message shortcuts](/interactivity/implementing-shortcuts#messages).
diff --git a/docs/english/concepts/socket-mode.md b/docs/english/concepts/socket-mode.md
@@ -1,7 +1,7 @@
 ---
 title: Using Socket Mode
 lang: en
-slug: /concepts/socket-mode
+slug: /bolt-python/concepts/socket-mode
 ---
 
 With the introduction of [Socket Mode](/apis/events-api/using-socket-mode), Bolt for Python introduced support in version `1.2.0`. With Socket Mode, instead of creating a server with endpoints that Slack sends payloads too, the app will instead connect to Slack via a WebSocket connection and receive data from Slack over the socket connection. Make sure to enable Socket Mode in your app configuration settings. 
diff --git a/docs/english/concepts/token-rotation.md b/docs/english/concepts/token-rotation.md
@@ -1,7 +1,7 @@
 ---
 title: Token rotation
 lang: en
-slug: /concepts/token-rotation
+slug: /bolt-python/concepts/token-rotation
 ---
 
 Supported in Bolt for Python as of [v1.7.0](https://github.com/slackapi/bolt-python/releases/tag/v1.7.0), token rotation provides an extra layer of security for your access tokens and is defined by the [OAuth V2 RFC](https://datatracker.ietf.org/doc/html/rfc6749#section-10.4). 
diff --git a/docs/english/concepts/updating-pushing-views.md b/docs/english/concepts/updating-pushing-views.md
@@ -1,7 +1,7 @@
 ---
 title: Updating & pushing views
 lang: en
-slug: /concepts/updating-pushing-views
+slug: /bolt-python/concepts/updating-pushing-views
 ---
 
 Modals contain a stack of views. When you call [`views_open`](https://api./reference/methods/views.open/slack.com/methods/views.open), you add the root view to the modal. After the initial call, you can dynamically update a view by calling [`views_update`](/reference/methods/views.update/), or stack a new view on top of the root view by calling [`views_push`](/reference/methods/views.push/)
diff --git a/docs/english/concepts/view-submissions.md b/docs/english/concepts/view-submissions.md
@@ -1,7 +1,7 @@
 ---
 title: Listening to views
 lang: en
-slug: /concepts/view_submissions
+slug: /bolt-python/concepts/view_submissions
 ---
 
 If a [view payload](/reference/interaction-payloads/view-interactions-payload/#view_submission) contains any input blocks, you must listen to `view_submission` requests to receive their values. To listen to `view_submission` requests, you can use the built-in `view()` method. `view()` requires a `callback_id` of type `str` or `re.Pattern`.
diff --git a/docs/english/concepts/web-api.md b/docs/english/concepts/web-api.md
@@ -1,7 +1,7 @@
 ---
 title: Using the Web API
 lang: en
-slug: /concepts/web-api
+slug: /bolt-python/concepts/web-api
 ---
 
 You can call [any Web API method](/reference/methods) using the [`WebClient`](/python-slack-sdk/web) provided to your Bolt app as either `app.client` or `client` in middleware/listener arguments (given that your app has the appropriate scopes). When you call one the client's methods, it returns a `SlackResponse` which contains the response from Slack.
diff --git a/docs/english/legacy/steps-from-apps.md b/docs/english/legacy/steps-from-apps.md
@@ -1,7 +1,7 @@
 ---
 title: Steps from apps
 lang: en
-slug: /legacy/steps-from-apps
+slug: /bolt-python/legacy/steps-from-apps
 ---
 
 :::danger[Steps from Apps is a deprecated feature.]
diff --git a/docs/japanese/concepts/acknowledge.md b/docs/japanese/concepts/acknowledge.md
@@ -1,7 +1,7 @@
 ---
 title: リクエストの確認
 lang: ja-jp
-slug: /concepts/acknowledge
+slug: /bolt-python/concepts/acknowledge
 ---
 
 アクション（action）、コマンド（command）、ショートカット（shortcut）、オプション（options）、およびモーダルからのデータ送信（view_submission）の各リクエストは、**必ず** `ack()` 関数を使って確認を行う必要があります。これによってリクエストが受信されたことが Slack に認識され、Slack のユーザーインターフェイスが適切に更新されます。
diff --git a/docs/japanese/concepts/actions.md b/docs/japanese/concepts/actions.md
@@ -1,7 +1,7 @@
 ---
 title: アクション
 lang: ja-jp
-slug: /concepts/actions
+slug: /bolt-python/concepts/actions
 ---
 
 ## アクションのリスニング
diff --git a/docs/japanese/concepts/adapters.md b/docs/japanese/concepts/adapters.md
@@ -1,7 +1,7 @@
 ---
 title: アダプター
 lang: ja-jp
-slug: /concepts/adapters
+slug: /bolt-python/concepts/adapters
 ---
 
 アダプターは Slack から届く受信リクエストの受付とパーズを担当し、それらのリクエストを <a href="https://github.com/slackapi/bolt-python/blob/main/slack_bolt/request/request.py">`BoltRequest`</a> の形式に変換して Bolt アプリに引き渡します。
diff --git a/docs/japanese/concepts/app-home.md b/docs/japanese/concepts/app-home.md
@@ -1,7 +1,7 @@
 ---
 title: ホームタブの更新
 lang: ja-jp
-slug: /concepts/app-home
+slug: /bolt-python/concepts/app-home
 ---
 
 <a href="/surfaces/app-home">ホームタブ</a>は、サイドバーや検索画面からアクセス可能なサーフェスエリアです。アプリはこのエリアを使ってユーザーごとのビューを表示することができます。アプリ設定ページで App Home の機能を有効にすると、<a href="/reference/methods/views.publis">`views.publish`</a> API メソッドの呼び出しで `user_id` と[ビューのペイロード](/reference/interaction-payloads/view-interactions-payload/#view_submission)を指定して、ホームタブを公開・更新することができるようになります。
diff --git a/docs/japanese/concepts/assistant.md b/docs/japanese/concepts/assistant.md
@@ -1,7 +1,7 @@
 ---
 title: エージェント・アシスタント
 lang: en
-slug: /concepts/assistant
+slug: /bolt-python/concepts/assistant
 ---
 
 このページは、Bolt を使ってエージェント・アシスタントを実装するための方法を紹介します。この機能に関する一般的な情報については、[こちらのドキュメントページ（英語）](/ai/)を参照してください。
diff --git a/docs/japanese/concepts/async.md b/docs/japanese/concepts/async.md
@@ -1,7 +1,7 @@
 ---
 title: Async（asyncio）の使用
 lang: ja-jp
-slug: /concepts/async
+slug: /bolt-python/concepts/async
 ---
 
 非同期バージョンの Bolt を使用する場合は、`App` の代わりに `AsyncApp` インスタンスをインポートして初期化します。`AsyncApp` では <a href="https://docs.aiohttp.org/">AIOHTTP</a> を使って API リクエストを行うため、`aiohttp` をインストールする必要があります（`requirements.txt` に追記するか、`pip install aiohttp` を実行します）。
diff --git a/docs/japanese/concepts/authenticating-oauth.md b/docs/japanese/concepts/authenticating-oauth.md
@@ -1,7 +1,7 @@
 ---
 title: OAuth を使った認証
 lang: ja-jp
-slug: /concepts/authenticating-oauth
+slug: /bolt-python/concepts/authenticating-oauth
 ---
 
 Slack アプリを複数のワークスペースにインストールできるようにするためには、OAuth フローを実装した上で、アクセストークンなどのインストールに関する情報をセキュアな方法で保存する必要があります。アプリを初期化する際に `client_id`、`client_secret`、`scopes`、`installation_store`、`state_store` を指定することで、OAuth のエンドポイントのルート情報や stateパラメーターの検証をBolt for Python にハンドリングさせることができます。カスタムのアダプターを実装する場合は、SDK が提供する組み込みの[OAuth ライブラリ](/python-slack-sdk/oauth/)を利用するのが便利です。これは Slack が開発したモジュールで、Bolt for Python 内部でも利用しています。
diff --git a/docs/japanese/concepts/authorization.md b/docs/japanese/concepts/authorization.md
@@ -1,7 +1,7 @@
 ---
 title: 認可（Authorization）
 lang: ja-jp
-slug: /concepts/authorization
+slug: /bolt-python/concepts/authorization
 ---
 
 認可（Authorization）は、Slack からの受信リクエストを処理するにあたって、どのようなSlack
diff --git a/docs/japanese/concepts/commands.md b/docs/japanese/concepts/commands.md
@@ -1,7 +1,7 @@
 ---
 title: コマンドのリスニングと応答
 lang: ja-jp
-slug: /concepts/commands
+slug: /bolt-python/concepts/commands
 ---
 
 スラッシュコマンドが実行されたリクエストをリッスンするには、`command()` メソッドを使用します。このメソッドでは `str` 型の `command_name` の指定が必要です。
diff --git a/docs/japanese/concepts/context.md b/docs/japanese/concepts/context.md
@@ -1,7 +1,7 @@
 ---
 title: コンテキストの追加
 lang: ja-jp
-slug: /concepts/context
+slug: /bolt-python/concepts/context
 ---
 
 すべてのリスナーは `context` ディクショナリにアクセスできます。リスナーはこれを使ってリクエストの付加情報を得ることができます。受信リクエストに含まれる `user_id`、`team_id`、`channel_id`、`enterprise_id` などの情報は、Bolt によって自動的に設定されます。
diff --git a/docs/japanese/concepts/custom-adapters.md b/docs/japanese/concepts/custom-adapters.md
@@ -1,7 +1,7 @@
 ---
 title: カスタムのアダプター
 lang: ja-jp
-slug: /concepts/custom-adapters
+slug: /bolt-python/concepts/custom-adapters
 ---
 
 [アダプター](/bolt-python/concepts/adapters)はフレキシブルで、あなたが使用したいフレームワークに合わせた調整も可能です。アダプターでは、次の 2 つの要素が必須となっています。
diff --git a/docs/japanese/concepts/custom-steps.md b/docs/japanese/concepts/custom-steps.md
@@ -1,7 +1,7 @@
 ---
 title: Listening and responding to custom steps
 lang: ja-jp
-slug: /concepts/custom-steps
+slug: /bolt-python/concepts/custom-steps
 ---
 
 Your app can use the `function()` method to listen to incoming [custom step requests](/workflows/workflow-steps). Custom steps are used in Workflow Builder to build workflows. The method requires a step `callback_id` of type `str`. This `callback_id` must also be defined in your [Function](/reference/app-manifest#functions) definition. Custom steps must be finalized using the `complete()` or `fail()` listener arguments to notify Slack that your app has processed the request.
diff --git a/docs/japanese/concepts/errors.md b/docs/japanese/concepts/errors.md
@@ -1,7 +1,7 @@
 ---
 title: エラーの処理
 lang: ja-jp
-slug: /concepts/errors
+slug: /bolt-python/concepts/errors
 ---
 
 リスナー内でエラーが発生した場合に try/except ブロックを使用して直接エラーを処理することができます。アプリに関連するエラーは、`BoltError` 型です。Slack API の呼び出しに関連するエラーは、`SlackApiError` 型となります。
diff --git a/docs/japanese/concepts/event-listening.md b/docs/japanese/concepts/event-listening.md
@@ -1,7 +1,7 @@
 ---
 title: イベントのリスニング
 lang: ja-jp
-slug: /concepts/event-listening
+slug: /bolt-python/concepts/event-listening
 ---
 
 `event()` メソッドを使うと、[Events API](/reference/events) の任意のイベントをリッスンできます。リッスンするイベントは、アプリの設定であらかじめサブスクライブしておく必要があります。これを利用することで、アプリがインストールされたワークスペースで何らかのイベント（例：ユーザーがメッセージにリアクションをつけた、ユーザーがチャンネルに参加した）が発生したときに、アプリに何らかのアクションを実行させることができます。
diff --git a/docs/japanese/concepts/global-middleware.md b/docs/japanese/concepts/global-middleware.md
@@ -1,7 +1,7 @@
 ---
 title: グローバルミドルウェア
 lang: ja-jp
-slug: /concepts/global-middleware
+slug: /bolt-python/concepts/global-middleware
 order: 8
 ---
 
diff --git a/docs/japanese/concepts/lazy-listeners.md b/docs/japanese/concepts/lazy-listeners.md
diff --git a/docs/japanese/concepts/listener-middleware.md b/docs/japanese/concepts/listener-middleware.md
diff --git a/docs/japanese/concepts/logging.md b/docs/japanese/concepts/logging.md
diff --git a/docs/japanese/concepts/message-listening.md b/docs/japanese/concepts/message-listening.md
diff --git a/docs/japanese/concepts/message-sending.md b/docs/japanese/concepts/message-sending.md
diff --git a/docs/japanese/concepts/opening-modals.md b/docs/japanese/concepts/opening-modals.md
diff --git a/docs/japanese/concepts/select-menu-options.md b/docs/japanese/concepts/select-menu-options.md
diff --git a/docs/japanese/concepts/shortcuts.md b/docs/japanese/concepts/shortcuts.md
diff --git a/docs/japanese/concepts/socket-mode.md b/docs/japanese/concepts/socket-mode.md
diff --git a/docs/japanese/concepts/token-rotation.md b/docs/japanese/concepts/token-rotation.md
diff --git a/docs/japanese/concepts/updating-pushing-views.md b/docs/japanese/concepts/updating-pushing-views.md
diff --git a/docs/japanese/concepts/view-submissions.md b/docs/japanese/concepts/view-submissions.md
diff --git a/docs/japanese/concepts/web-api.md b/docs/japanese/concepts/web-api.md
diff --git a/docs/japanese/legacy/steps-from-apps.md b/docs/japanese/legacy/steps-from-apps.md
