remove manual slugs

lukegalbraithrussell · lukegalbraithrussell · commit 7b1503ff3908 · 2025-08-06T10:26:07.000-07:00
diff --git a/docs/english/building-an-app.md b/docs/english/building-an-app.md
@@ -1,5 +1,4 @@
 ---
-title: Building an App with Bolt for Python
 sidebar_label: Building an App
 ---
 
diff --git a/docs/english/concepts/acknowledge.md b/docs/english/concepts/acknowledge.md
@@ -1,8 +1,4 @@
----
-title: Acknowledging requests
-lang: en
-slug: /bolt-python/concepts/acknowledge
----
+# Acknowledging requests
 
 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,8 +1,4 @@
----
-title: Listening & responding to actions
-lang: en
-slug: /bolt-python/concepts/actions
----
+# Listening & responding to 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,8 +1,4 @@
----
-title: Adapters
-lang: en
-slug: /bolt-python/concepts/adapters
----
+# 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,8 +1,4 @@
----
-title: Using AI in Apps
-lang: en
-slug: /bolt-python/concepts/ai-apps
----
+#: Using AI in Apps
 
 :::info This feature requires a paid plan
 If you don't have a paid workspace for development, you can join the [Developer Program](https://api.slack.com/developer-program) and provision a sandbox with access to all Slack features for free.
diff --git a/docs/english/concepts/app-home.md b/docs/english/concepts/app-home.md
@@ -1,8 +1,4 @@
----
-title: Publishing views to App Home
-lang: en
-slug: /bolt-python/concepts/app-home
----
+# Publishing views to 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,8 +1,4 @@
----
-title: Using async (asyncio)
-lang: en
-slug: /bolt-python/concepts/async
----
+# Using async (asyncio)
 
 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,8 +1,4 @@
----
-title: Authenticating with OAuth
-lang: en
-slug: /bolt-python/concepts/authenticating-oauth
----
+# Authenticating with 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](/tools/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,8 +1,4 @@
----
-title: Authorization
-lang: en
-slug: /bolt-python/concepts/authorization
----
+# 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,8 +1,4 @@
----
-title: Listening & responding to commands
-lang: en
-slug: /bolt-python/concepts/commands
----
+# Listening & responding to 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,8 +1,4 @@
----
-title: Adding context
-lang: en
-slug: /bolt-python/concepts/context
----
+# Adding 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,8 +1,4 @@
----
-title: Custom adapters
-lang: en
-slug: /bolt-python/concepts/custom-adapters
----
+# Custom adapters
 
 [Adapters](/tools/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
@@ -1,10 +1,9 @@
 ---
-title: Listening and responding to custom steps
-sidebar_label: Custom Steps
-lang: en
-slug: /bolt-python/concepts/custom-steps
+sidebar_label: Custom steps
 ---
 
+# Listening and responding to 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.
 
 * `complete()` requires **one** argument: `outputs` of type `dict`. It ends your custom step **successfully** and provides a dictionary containing the outputs of your custom step as per its definition.
diff --git a/docs/english/concepts/errors.md b/docs/english/concepts/errors.md
@@ -1,8 +1,4 @@
----
-title: Handling errors
-lang: en
-slug: /bolt-python/concepts/errors
----
+#  Handling 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,8 +1,4 @@
----
-title: Listening to events
-lang: en
-slug: /bolt-python/concepts/event-listening
----
+# Listening to events
 
 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,8 +1,4 @@
----
-title: Global middleware
-lang: en
-slug: /bolt-python/concepts/global-middleware
----
+# 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,8 +1,4 @@
----
-title: Lazy listeners (FaaS)
-lang: en
-slug: /bolt-python/concepts/lazy-listeners
----
+# Lazy listeners (FaaS)
 
 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,8 +1,4 @@
----
-title: Listener middleware
-lang: en
-slug: /bolt-python/concepts/listener-middleware
----
+# 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,8 +1,4 @@
----
-title: Logging
-lang: en
-slug: /bolt-python/concepts/logging
----
+# 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,9 +1,4 @@
----
-title: Listening to messages
-lang: en
-slug: /bolt-python/concepts/message-listening
----
-
+# Listening to messages
 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`.
 
 `message()` accepts an argument of type `str` or `re.Pattern` object that filters out any messages that don't match the pattern.
diff --git a/docs/english/concepts/message-sending.md b/docs/english/concepts/message-sending.md
@@ -1,8 +1,4 @@
----
-title: Sending messages
-lang: en
-slug: /bolt-python/concepts/message-sending
----
+# Sending messages
 
 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,8 +1,4 @@
----
-title: Opening modals
-lang: en
-slug: /bolt-python/concepts/opening-modals
----
+# 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,8 +1,4 @@
----
-title: Listening & responding to select menu options
-lang: en
-slug: /bolt-python/concepts/options
----
+# Listening & responding to select menu options
 
 The `options()` method listens for incoming option request payloads from Slack. [Similar to `action()`](/tools/bolt-python/concepts/actions),
 an `action_id` or constraints object is required. In order to load external data into your select menus, you must provide an options load URL in your app configuration, appended with `/slack/events`.
diff --git a/docs/english/concepts/shortcuts.md b/docs/english/concepts/shortcuts.md
@@ -1,8 +1,4 @@
----
-title: Listening & responding to shortcuts
-lang: en
-slug: /bolt-python/concepts/shortcuts
----
+# Listening & responding to 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,8 +1,4 @@
----
-title: Using Socket Mode
-lang: en
-slug: /bolt-python/concepts/socket-mode
----
+# Using 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,8 +1,4 @@
----
-title: Token rotation
-lang: en
-slug: /bolt-python/concepts/token-rotation
----
+# 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,8 +1,4 @@
----
-title: Updating & pushing views
-lang: en
-slug: /bolt-python/concepts/updating-pushing-views
----
+# 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,8 +1,4 @@
----
-title: Listening to views
-lang: en
-slug: /bolt-python/concepts/view_submissions
----
+# Listening to views
 
 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,8 +1,4 @@
----
-title: Using the Web API
-lang: en
-slug: /bolt-python/concepts/web-api
----
+# Using the Web API
 
 You can call [any Web API method](/reference/methods) using the `WebClient` 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/getting-started.md b/docs/english/getting-started.md
@@ -1,9 +1,8 @@
 ---
-title: Quickstart guide with Bolt for Python
 sidebar_label: Quickstart
 ---
 
-# Getting started with Bolt for Python
+# Quickstart guide with Bolt for Python
 
 This quickstart guide aims to help you get a Slack app using Bolt for Python up and running as soon as possible!
 
diff --git a/docs/english/legacy/steps-from-apps.md b/docs/english/legacy/steps-from-apps.md
@@ -1,8 +1,4 @@
----
-title: Steps from apps
-lang: en
-slug: /bolt-python/legacy/steps-from-apps
----
+# Steps from apps
 
 :::danger[Steps from Apps is a deprecated feature.]
 
diff --git a/docs/english/tutorial/custom-steps-workflow-builder-existing/custom-steps-workflow-builder-existing.md b/docs/english/tutorial/custom-steps-workflow-builder-existing/custom-steps-workflow-builder-existing.md
@@ -1,6 +1,4 @@
----
-title: Custom Steps for Workflow Builder (existing app)
----
+# Custom Steps for Workflow Builder (existing app)
 
 :::info[This feature requires a paid plan]
 If you don't have a paid workspace for development, you can join the [Developer Program](https://api.slack.com/developer-program) and provision a sandbox with access to all Slack features for free.
diff --git a/docs/english/tutorial/custom-steps-workflow-builder-new/custom-steps-workflow-builder-new.md b/docs/english/tutorial/custom-steps-workflow-builder-new/custom-steps-workflow-builder-new.md
@@ -1,6 +1,4 @@
----
-title: Custom Steps for Workflow Builder (new app)
----
+# Custom Steps for Workflow Builder (new app)
 
 :::info[This feature requires a paid plan]
 If you don't have a paid workspace for development, you can join the [Developer Program](https://api.slack.com/developer-program) and provision a sandbox with access to all Slack features for free.
diff --git a/docs/english/tutorial/modals/modals.md b/docs/english/tutorial/modals/modals.md
@@ -1,4 +1,3 @@
-
 # Modals
 
 If you're learning about Slack apps, modals, or slash commands for the first time, you've come to the right place! In this tutorial, we'll take a look at setting up your very own server using GitHub Codespaces, then using that server to run your Slack app built with the [**Bolt for Python framework**](https://github.com/SlackAPI/bolt-python).

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,4 @@`
`1`	`1`	`---`
`2`		`-title: Building an App with Bolt for Python`
`3`	`2`	`sidebar_label: Building an App`
`4`	`3`	`---`
`5`	`4`