From 945a75270db10f0d7875f98959ced68919a1a1f4 Mon Sep 17 00:00:00 2001
From: Gabriele Todaro <109546049+Gabriele73@users.noreply.github.com>
Date: Sat, 18 May 2024 14:37:42 +0200
Subject: [PATCH 1/6] Create Getting_Started.mdx
---
docs/it/Getting_Started.mdx | 486 ++++++++++++++++++++++++++++++++++++
1 file changed, 486 insertions(+)
create mode 100644 docs/it/Getting_Started.mdx
diff --git a/docs/it/Getting_Started.mdx b/docs/it/Getting_Started.mdx
new file mode 100644
index 0000000000..49c13979c0
--- /dev/null
+++ b/docs/it/Getting_Started.mdx
@@ -0,0 +1,486 @@
+
+
+# Building your first Discord app
+
+Discord apps let you customize and extend Discord using a collection of APIs and interactive features. This guide will walk you through building your first Discord app using JavaScript, and by the end you'll have an app that uses slash commands, sends messages, and responds to component interactions.
+
+We'll be building a Discord app that lets server members play rock-paper-scissors (with 7 choices instead of the usual 3). This guide is beginner-focused, but it assumes a basic understanding of [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/JavaScript_basics).
+
+
+Here's what the finished app will look like:
+
+
+
+To make the user flow a bit more explicit:
+
+1. User 1 initiates a new game and picks their object using the app's `/challenge` slash command
+2. A message is sent to channel with a button inviting others to accept the challenge
+3. User 2 presses the **Accept** button
+4. User 2 is sent an ephemeral message where they select their object of choice
+5. The result of the game is posted back into the original channel for all to see
+
+
+
+- **[GitHub repository](https://github.com/discord/discord-example-app)** where the code from this guide lives along with some additional feature-specific code examples.
+- **[discord-interactions](https://github.com/discord/discord-interactions-js)**, a library that provides types and helper functions for Discord apps.
+- **[Express](https://expressjs.com)**, a popular JavaScript web framework we'll use to create a server where Discord can send us requests.
+- **[Glitch](https://glitch.com/)**, an online environment that simplifies building and hosting apps during early prototyping and development. You can also develop locally with a tool like **[ngrok](https://ngrok.com/)**.
+
+
+---
+
+## Step 1: Creating an app
+
+First, you'll need to create an app in the developer portal if you don't have one already:
+
+
+
+Enter a name for your app, then press **Create**.
+
+After you create your app, you'll land on the **General Overview** page of the app's settings where you can update basic information about your app like its description and icon. You'll also see an **Application ID** and **Interactions Endpoint URL**, which we'll use a bit later in the guide.
+
+### Configuring your bot
+
+Next we'll configure the [bot user](#DOCS_TOPICS_OAUTH2/bot-vs-user-accounts) for your app, which allows it to appear and behave similarly to other server members.
+
+On the left hand sidebar click **Bot**. On this page, you can configure settings like its [privileged intents](#DOCS_TOPICS_GATEWAY/privileged-intents) or whether it can be installed by other users.
+
+
+Intents determine which events Discord will send your app when you're creating a [Gateway API connection](#DOCS_TOPICS_GATEWAY). For example, if you want your app to do something when users add a reaction to a message, you can pass the `GUILD_MESSAGE_REACTIONS` (`1 << 10`) intent.
+
+Some intents are [privileged](#DOCS_TOPICS_GATEWAY/privileged-intents), meaning they allow your app to access data that may be considered sensitive (like the contents of messages). Privileged intents appear and can be toggled on the **Bot** page in your app's settings. Standard, non-privileged intents don't require any additional permissions or configurations.
+
+More information about intents and a full list of available intents, along with their associated events, is in the [Gateway documentation](#DOCS_TOPICS_GATEWAY/gateway-intents).
+
+
+
+
+There's also a **Token** section on the **Bot** page, which allows you to copy and reset your bot's token.
+
+Bot tokens are used to authorize API requests and carry your bot user's permissions, making them *highly sensitive*. Make sure to *never* share your token or check it into any kind of version control.
+
+Go ahead and copy the token, and store the token somewhere safe (like in a password manager).
+
+> warn
+> You won't be able to view your token again unless you regenerate it, so make sure to keep it somewhere safe.
+
+### Adding scopes and bot permissions
+
+Apps need approval from installing users to perform actions in Discord (like creating a slash command or fetching a list of server members). Let's select a few scopes and permissions to request before installing the app.
+
+
+When creating an app, scopes and permissions determine what your app can do and access in Discord servers.
+
+- [OAuth2 Scopes](#DOCS_TOPICS_OAUTH2/shared-resources-oauth2-scopes) determine what data access and actions your app can take, granted on behalf of an installing or authenticating user.
+- [Permissions](#DOCS_TOPICS_PERMISSIONS/permission-overwrites) are the granular permissions for your bot user, the same as other users in Discord have. They can be approved by the installing user or later updated within server settings or with [permission overwrites](#DOCS_TOPICS_PERMISSIONS/permission-overwrites).
+
+
+Click on **OAuth2** in the left sidebar, then select **URL generator**.
+
+> info
+> The URL generator creates an installation link based on the scopes and permissions you select for your app. You can use the link to install the app onto your own server, or share it with others so they can install it.
+
+For now, just add the **`bot` scope**, which adds your bot user.
+
+After you select `bot`, you can also select different permissions for your bot. For now, just check **Send Messages**.
+
+See a list of all [OAuth2 scopes](#DOCS_TOPICS_OAUTH2/shared-resources-oauth2-scopes), or read more on [permissions](#DOCS_TOPICS_PERMISSIONS) in the documentation.
+
+### Installing your app
+
+Once you add scopes, you should see a URL that you can copy to install your app.
+
+
+
+> info
+> When developing apps, you should build and test in a server that isn't actively used by others. If you don't have your own server already, you can [create one for free](https://support.discord.com/hc/en-us/articles/204849977-How-do-I-create-a-server-).
+
+Copy the URL from above, and paste it into your browser. You'll be guided through the installation flow, where you should make sure you're installing your app on a server where you can develop and test it.
+
+After installing your app, you can head over to your server and see that it has joined ✨
+
+With your app configured and installed, let's start developing it.
+
+---
+
+## Step 2: Running your app
+
+All of the code used in the example app can be found in [the GitHub repository](https://github.com/discord/discord-example-app).
+
+To make development a bit simpler, the app uses [discord-interactions](https://github.com/discord/discord-interactions-js), which provides types and helper functions. If you prefer to use other languages or libraries, check out the [Community Resources](#DOCS_TOPICS_COMMUNITY_RESOURCES) documentation.
+
+### Remixing the project
+
+This guide uses Glitch, which lets you clone and develop within your browser. If you'd prefer to develop your app locally, there's instructions on using ngrok [in the README](https://github.com/discord/discord-example-app#running-app-locally).
+
+> info
+> While Glitch is great for development and testing, [it has technical restrictions](https://help.glitch.com/kb/article/17-technical-restrictions/) so other hosting providers should be considered for production apps.
+
+To start, **[remix (or clone) the Glitch project 🎏](https://glitch.com/edit/#!/import/git?url=https://github.com/discord/discord-example-app.git)**.
+
+Once you remix the project, you'll land on a new Glitch project.
+
+
+
+
+- Your **project name** is a unique name for your project, found in the upper-left corner
+- **`.env`** is the file where all of your credentials for your app will be stored
+- **Logs** are where your project's output is found—this is helpful to see if the app is running or information about any errors your app encounters
+- The **Share** button in the top-right corner is where you'll find the live project URL, which you'll need to set up interactivity later in this guide
+
+
+#### Project structure
+
+All of the files for the project are on the left-hand side of your Glitch project. Below is an overview of the main folders and files:
+
+```
+├── examples -> short, feature-specific sample apps
+│ ├── app.js -> finished app.js code
+│ ├── button.js
+│ ├── command.js
+│ ├── modal.js
+│ ├── selectMenu.js
+├── .env -> your credentials and IDs
+├── app.js -> main entrypoint for app
+├── commands.js -> slash command payloads + helpers
+├── game.js -> logic specific to RPS
+├── utils.js -> utility functions and enums
+├── package.json
+├── README.md
+└── .gitignore
+```
+
+### Adding credentials
+
+There's already some code in your `app.js` file, but you'll need your app's token and ID to make requests. All of your credentials can be stored directly in the `.env` file.
+
+First, copy your bot user's token from earlier and paste it in the **`DISCORD_TOKEN`** variable in your `.env` file.
+
+Next, navigate to your app's **General Overview** page, then copy the **App ID** and **Public Key**. Paste the values in your `.env` file as **`APP_ID`** and **`PUBLIC_KEY`**.
+
+With your credentials configured, let's install and handle slash commands.
+
+### Installing slash commands
+
+> info
+> To install slash commands, the app is using [`node-fetch`](https://github.com/node-fetch/node-fetch). You can see the implementation for the installation in `utils.js` within the `DiscordRequest()` function.
+
+The project contains a `register` script you can use to install the commands in `ALL_COMMANDS`, which is defined at the bottom of `commands.js`. It installs the commands as global commands by calling the HTTP API's [`PUT /applications//commands`](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/bulk-overwrite-global-application-commands) endpoint.
+
+If you want to customize your commands or add additional ones, you can reference the command structure in the [commands documentation](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/application-command-object-application-command-structure).
+
+Run the `register` script by clicking **Terminal** at the bottom of your Glitch project and pasting the following command:
+
+```
+npm run register
+```
+
+Hit enter to run the command.
+
+If you navigate back to your server, you should see the slash commands appear. But if you try to run them, nothing will happen since your app isn't receiving or handling any requests from Discord.
+
+
+Discord has two APIs that you can mix-and-match to build apps:
+
+- **[HTTP API](#DOCS_REFERENCE/http-api)** is a REST-like API for general operations like sending and updating data in Discord, or fetching data about a resource.
+- **[Gateway API](#DOCS_REFERENCE/gateway-websocket-api)** is a WebSocket-based API that is helpful for maintaining state or listening to events happening in a Discord server. We won't be using it in this guide, but more information about how to create a Gateway connection and the different events you can listen to are in the [Gateway documentation](#DOCS_TOPICS_GATEWAY).
+
+
+---
+
+## Step 3: Handling interactivity
+
+To enable your app to receive slash command requests (and other interactions), Discord needs a public URL to send them. This URL can be configured in your app's settings as **Interaction Endpoint URL**.
+
+### Adding an interaction endpoint URL
+
+Glitch projects have a public URL exposed by default. Copy your project's URL by clicking the **Share** button in the top right corner, then copy the "Live site" project link near the bottom of the modal.
+
+> info
+> If you're developing locally, there are instructions for tunneling requests to your local environment [on the GitHub README](https://github.com/discord/discord-example-app#running-app-locally).
+
+With the link copied, go to your app's settings from [the developer portal](https://discord.com/developers/applications).
+
+On your app's **General Information** page, there's an **Interactive Endpoint URL** option, where you can paste your app's URL and append `/interactions` to it, which is where the Express app is configured to listen for requests.
+
+
+
+Click **Save Changes** and ensure your endpoint is successfully verified.
+
+The sample app handles verification in two ways:
+- It uses the `PUBLIC_KEY` and [discord-interactions package](https://github.com/discord/discord-interactions-js#usage) with a wrapper function (imported from `utils.js`) that makes it conform to [Express's `verify` interface](http://expressjs.com/en/5x/api.html#express.json). This is run on every incoming request to your app.
+- It responds to incoming `PING` requests.
+
+You can learn more about preparing your app to receive interactions in [the interactions documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/receiving-an-interaction).
+
+### Handling slash command requests
+
+With the endpoint verified, navigate to your project's `app.js` file and find the code block that handles the `/test` command:
+
+```javascript
+// "test" command
+if (name === 'test') {
+ // Send a message into the channel where command was triggered from
+ return res.send({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: {
+ // Fetches a random emoji to send from a helper function
+ content: 'hello world ' + getRandomEmoji(),
+ },
+ });
+}
+```
+
+The code above is responding to the interaction with a message in the channel it originated from. You can see all available response types, like responding with a modal, [in the documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-response-object-interaction-callback-type).
+
+> info
+> `InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE` is a constant [exported from `discord-interactions`](https://github.com/discord/discord-interactions-js/blob/main/src/index.ts#L33)
+
+Go to your server and make sure your app's `/test` slash command works. When you trigger it, your app should send a message that contains “hello world” followed by a random emoji.
+
+In the following section, we'll add an additional command that uses slash command options, buttons, and select menus to build the rock-paper-scissors game.
+
+---
+
+## Step 4: Adding message components
+
+The `/challenge` command will be how our rock-paper-scissors-style game is initiated. When the command is triggered, the app will send message components to the channel, which will guide the users to complete the game.
+
+### Adding a command with options
+
+The `/challenge` command, called `CHALLENGE_COMMAND` in `commands.js`, has an array of `options`. In our app, the options are objects representing different things that a user can select while playing rock-paper-scissors, generated using keys of `RPSChoices` in `game.js`.
+
+You can read more about command options and their structure [in the documentation](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/application-command-object-application-command-option-structure).
+
+> info
+> While this guide won't touch much on the `game.js` file, feel free to poke around and change commands or the options in the commands.
+
+
+
+To handle the `/challenge` command, add the following code after the `if name === “test”` if block:
+
+```javascript
+// "challenge" command
+if (name === 'challenge' && id) {
+ const userId = req.body.member.user.id;
+ // User's object choice
+ const objectName = req.body.data.options[0].value;
+
+ // Create active game using message ID as the game ID
+ activeGames[id] = {
+ id: userId,
+ objectName,
+ };
+
+ return res.send({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: {
+ content: `Rock papers scissors challenge from <@${userId}>`,
+ components: [
+ {
+ type: MessageComponentTypes.ACTION_ROW,
+ components: [
+ {
+ type: MessageComponentTypes.BUTTON,
+ // Append the game ID to use later on
+ custom_id: `accept_button_${req.body.id}`,
+ label: 'Accept',
+ style: ButtonStyleTypes.PRIMARY,
+ },
+ ],
+ },
+ ],
+ },
+ });
+}
+```
+
+
+> info
+> If you aren't sure where to paste the code, you can see the full code in `examples/app.js` in the Glitch project or the root `app.js` [on GitHub](https://github.com/discord/discord-example-app/blob/main/app.js).
+
+The above code is doing a few things:
+1. Parses the request body to get the ID of the user who triggered the slash command (`userId`), and the option (object choice) they selected (`objectName`).
+2. Adds a new game to the `activeGames` object using the interaction ID. The active game records the `userId` and `objectName`.
+3. Sends a message back to the channel with a button with a `custom_id` of `accept_button_`.
+
+> warn
+> The sample code uses an object as in-memory storage, but for production apps you should use a database.
+
+When sending a message with [message components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/what-is-a-component), the individual payloads are appended to a `components` array. Actionable components (like buttons) need to be inside of an [action row](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/action-rows), which you can see in the code sample.
+
+Note the unique `custom_id` sent with message components, in this case `accept_button_` with the active game's ID appended to it. A `custom_id` can be used to handle requests that Discord sends you when someone interacts with the component, which you'll see in a moment.
+
+Now when you run the `/challenge` command and pick an option, your app will send a message with an **Accept** button. Let's add code to handle the button press.
+
+
+
+
+
+When users interact with a message component, Discord will send a request with an [interaction type](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-object-interaction-type) of `3` (or the `MESSAGE_COMPONENT` value when using `discord-interactions`).
+
+To set up a handler for the button, we'll check the `type` of interaction, followed by matching the `custom_id`.
+
+Paste the following code under the type handler for `APPLICATION_COMMAND`s:
+
+```javascript
+if (type === InteractionType.MESSAGE_COMPONENT) {
+// custom_id set in payload when sending message component
+const componentId = data.custom_id;
+
+ if (componentId.startsWith('accept_button_')) {
+ // get the associated game ID
+ const gameId = componentId.replace('accept_button_', '');
+ // Delete message with token in request body
+ const endpoint = `webhooks/${process.env.APP_ID}/${req.body.token}/messages/${req.body.message.id}`;
+ try {
+ await res.send({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: {
+ // Fetches a random emoji to send from a helper function
+ content: 'What is your object of choice?',
+ // Indicates it'll be an ephemeral message
+ flags: InteractionResponseFlags.EPHEMERAL,
+ components: [
+ {
+ type: MessageComponentTypes.ACTION_ROW,
+ components: [
+ {
+ type: MessageComponentTypes.STRING_SELECT,
+ // Append game ID
+ custom_id: `select_choice_${gameId}`,
+ options: getShuffledOptions(),
+ },
+ ],
+ },
+ ],
+ },
+ });
+ // Delete previous message
+ await DiscordRequest(endpoint, { method: 'DELETE' });
+ } catch (err) {
+ console.error('Error sending message:', err);
+ }
+ }
+}
+```
+
+The above code:
+1. Checks for a `custom_id` that matches what we originally sent (in this case, it starts with `accept_button_`). The custom ID also has the active game ID appended, so we store that in `gameID`.
+2. [Deletes the original message](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/delete-original-interaction-response) calling a webhook using `node-fetch` and passing the unique interaction `token` in the request body. This is done to clean up the channel, and so other users can't click the button.
+3. Responds to the request by sending a message that contains a select menu with the object choices for the game. The payload should look fairly similar to the previous one, with the exception of the `options` array and `flags: 64`, [which indicates that the message is ephemeral](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/create-followup-message).
+
+The `options` array is populated using the `getShuffledOptions()` method in `game.js`, which manipulates the `RPSChoices` values to conform to the shape of [message component options](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/select-menu-object-select-option-structure).
+
+
+
+
+
+The last thing to add is code to handle select menu interactions, and to send the result of the game to channel.
+
+Since select menus are just another message component, the code to handle their interactions will be almost identical to buttons.
+
+Modify the code above to handle the select menu:
+
+```javascript
+if (type === InteractionType.MESSAGE_COMPONENT) {
+// custom_id set in payload when sending message component
+const componentId = data.custom_id;
+
+ if (componentId.startsWith('accept_button_')) {
+ // get the associated game ID
+ const gameId = componentId.replace('accept_button_', '');
+ // Delete message with token in request body
+ const endpoint = `webhooks/${process.env.APP_ID}/${req.body.token}/messages/${req.body.message.id}`;
+ try {
+ await res.send({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: {
+ content: 'What is your object of choice?',
+ // Indicates it'll be an ephemeral message
+ flags: InteractionResponseFlags.EPHEMERAL,
+ components: [
+ {
+ type: MessageComponentTypes.ACTION_ROW,
+ components: [
+ {
+ type: MessageComponentTypes.STRING_SELECT,
+ // Append game ID
+ custom_id: `select_choice_${gameId}`,
+ options: getShuffledOptions(),
+ },
+ ],
+ },
+ ],
+ },
+ });
+ // Delete previous message
+ await DiscordRequest(endpoint, { method: 'DELETE' });
+ } catch (err) {
+ console.error('Error sending message:', err);
+ }
+ } else if (componentId.startsWith('select_choice_')) {
+ // get the associated game ID
+ const gameId = componentId.replace('select_choice_', '');
+
+ if (activeGames[gameId]) {
+ // Get user ID and object choice for responding user
+ const userId = req.body.member.user.id;
+ const objectName = data.values[0];
+ // Calculate result from helper function
+ const resultStr = getResult(activeGames[gameId], {
+ id: userId,
+ objectName,
+ });
+
+ // Remove game from storage
+ delete activeGames[gameId];
+ // Update message with token in request body
+ const endpoint = `webhooks/${process.env.APP_ID}/${req.body.token}/messages/${req.body.message.id}`;
+
+ try {
+ // Send results
+ await res.send({
+ type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
+ data: { content: resultStr },
+ });
+ // Update ephemeral message
+ await DiscordRequest(endpoint, {
+ method: 'PATCH',
+ body: {
+ content: 'Nice choice ' + getRandomEmoji(),
+ components: []
+ }
+ });
+ } catch (err) {
+ console.error('Error sending message:', err);
+ }
+ }
+ }
+}
+```
+
+Similar to earlier code, the code above is getting the user ID and their object selection from the interaction request.
+
+That information, along with the original user's ID and selection from the `activeGames` object, are passed to the `getResult()` function. `getResult()` determines the winner, then builds a readable string to send back to the channel.
+
+We're also calling another webhook, this time to [update the follow-up ephemeral message](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/edit-followup-message) since it can't be deleted.
+
+Finally, the results are sent in the channel using the `CHANNEL_MESSAGE_WITH_SOURCE` interaction response type.
+
+
+
+....and that's it 🎊 Go ahead and test your app and make sure everything works.
+
+---
+
+## Next steps
+
+Congrats on building your first Discord app! 🤖
+
+Hopefully you learned a bit about Discord apps, how to configure them, and how to make them interactive. From here, you can continue building out your app or explore what else is possible:
+- Read **[the documentation](#DOCS_INTRO)** for in-depth information about API features
+- Browse the `examples/` folder in this project for smaller, feature-specific code examples
+- Check out **[community resources](#DOCS_TOPICS_COMMUNITY_RESOURCES)** for language-specific tools maintained by community members
+- Read our tutorial on [hosting Discord apps on Cloudflare Workers](#DOCS_TUTORIALS_HOSTING_ON_CLOUDFLARE_WORKERS)
+- Join the **[Discord Developers server](https://discord.gg/discord-developers)** to ask questions about the API, attend events hosted by the Discord API team, and interact with other devs
From 006aad43ab5e76634477b41d5549128d3b32899f Mon Sep 17 00:00:00 2001
From: Gabriele Todaro <109546049+Gabriele73@users.noreply.github.com>
Date: Sat, 18 May 2024 14:47:56 +0200
Subject: [PATCH 2/6] Update Getting_Started.mdx
---
docs/it/Getting_Started.mdx | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/docs/it/Getting_Started.mdx b/docs/it/Getting_Started.mdx
index 49c13979c0..d45420778d 100644
--- a/docs/it/Getting_Started.mdx
+++ b/docs/it/Getting_Started.mdx
@@ -1,27 +1,27 @@
-# Building your first Discord app
+# Sviluppare la tua prima app su Discord
-Discord apps let you customize and extend Discord using a collection of APIs and interactive features. This guide will walk you through building your first Discord app using JavaScript, and by the end you'll have an app that uses slash commands, sends messages, and responds to component interactions.
+Le app Discord ti permettono di personalizzare ed estendere le funzionalità di Discord utilizzando una collezione di APIs e funzionalità interattive. Questa guida ti servirà per sviluppare la tua prima app Discord utilizzando JavaScript, e alla fine avrai un'app che utilizza gli slash commmands, invia messaggi, e risponde alle component interactions.
-We'll be building a Discord app that lets server members play rock-paper-scissors (with 7 choices instead of the usual 3). This guide is beginner-focused, but it assumes a basic understanding of [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/JavaScript_basics).
+Svilupperemo un'app Discord che permette ai membri del server di giocare a sasso-carta-forbice (con 7 scelte invece delle usuali 3). Questa guida è beginner-focused, ma presume che tu abbia una conoscenza base di [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/JavaScript_basics).
-
-Here's what the finished app will look like:
+
+Ecco l'aspetto dell'app finalizzata:
-
+
-To make the user flow a bit more explicit:
+Per esplicitare l'user flow:
-1. User 1 initiates a new game and picks their object using the app's `/challenge` slash command
-2. A message is sent to channel with a button inviting others to accept the challenge
-3. User 2 presses the **Accept** button
-4. User 2 is sent an ephemeral message where they select their object of choice
-5. The result of the game is posted back into the original channel for all to see
+1. Utente 1 inizia un nuovo gioco e sceglie il proprio oggetto usando lo slash command `/challenge` fornito dall'app
+2. Un messaggio viene inviato nel canale con un bottone invitando altri a partecipare
+3. Utente 2 clicca il pulsante **Accept**
+4. Utente 2 riceve un messaggio effimero dove selezionano il proprio oggetto
+5. Il risultato del gioco viene inviato nel canale originale mostrando a tutti il risultato
-
-- **[GitHub repository](https://github.com/discord/discord-example-app)** where the code from this guide lives along with some additional feature-specific code examples.
+
+- **[Repository GitHub](https://github.com/discord/discord-example-app)** where the code from this guide lives along with some additional feature-specific code examples.
- **[discord-interactions](https://github.com/discord/discord-interactions-js)**, a library that provides types and helper functions for Discord apps.
- **[Express](https://expressjs.com)**, a popular JavaScript web framework we'll use to create a server where Discord can send us requests.
- **[Glitch](https://glitch.com/)**, an online environment that simplifies building and hosting apps during early prototyping and development. You can also develop locally with a tool like **[ngrok](https://ngrok.com/)**.
From 3933a99850858b4d7fbfdf56cc2fe860ab544a36 Mon Sep 17 00:00:00 2001
From: Gabriele Todaro <109546049+Gabriele73@users.noreply.github.com>
Date: Sat, 18 May 2024 14:49:46 +0200
Subject: [PATCH 3/6] Delete docs/it/Getting_Started.mdx
---
docs/it/Getting_Started.mdx | 486 ------------------------------------
1 file changed, 486 deletions(-)
delete mode 100644 docs/it/Getting_Started.mdx
diff --git a/docs/it/Getting_Started.mdx b/docs/it/Getting_Started.mdx
deleted file mode 100644
index d45420778d..0000000000
--- a/docs/it/Getting_Started.mdx
+++ /dev/null
@@ -1,486 +0,0 @@
-
-
-# Sviluppare la tua prima app su Discord
-
-Le app Discord ti permettono di personalizzare ed estendere le funzionalità di Discord utilizzando una collezione di APIs e funzionalità interattive. Questa guida ti servirà per sviluppare la tua prima app Discord utilizzando JavaScript, e alla fine avrai un'app che utilizza gli slash commmands, invia messaggi, e risponde alle component interactions.
-
-Svilupperemo un'app Discord che permette ai membri del server di giocare a sasso-carta-forbice (con 7 scelte invece delle usuali 3). Questa guida è beginner-focused, ma presume che tu abbia una conoscenza base di [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/JavaScript_basics).
-
-
-Ecco l'aspetto dell'app finalizzata:
-
-
-
-Per esplicitare l'user flow:
-
-1. Utente 1 inizia un nuovo gioco e sceglie il proprio oggetto usando lo slash command `/challenge` fornito dall'app
-2. Un messaggio viene inviato nel canale con un bottone invitando altri a partecipare
-3. Utente 2 clicca il pulsante **Accept**
-4. Utente 2 riceve un messaggio effimero dove selezionano il proprio oggetto
-5. Il risultato del gioco viene inviato nel canale originale mostrando a tutti il risultato
-
-
-
-- **[Repository GitHub](https://github.com/discord/discord-example-app)** where the code from this guide lives along with some additional feature-specific code examples.
-- **[discord-interactions](https://github.com/discord/discord-interactions-js)**, a library that provides types and helper functions for Discord apps.
-- **[Express](https://expressjs.com)**, a popular JavaScript web framework we'll use to create a server where Discord can send us requests.
-- **[Glitch](https://glitch.com/)**, an online environment that simplifies building and hosting apps during early prototyping and development. You can also develop locally with a tool like **[ngrok](https://ngrok.com/)**.
-
-
----
-
-## Step 1: Creating an app
-
-First, you'll need to create an app in the developer portal if you don't have one already:
-
-
-
-Enter a name for your app, then press **Create**.
-
-After you create your app, you'll land on the **General Overview** page of the app's settings where you can update basic information about your app like its description and icon. You'll also see an **Application ID** and **Interactions Endpoint URL**, which we'll use a bit later in the guide.
-
-### Configuring your bot
-
-Next we'll configure the [bot user](#DOCS_TOPICS_OAUTH2/bot-vs-user-accounts) for your app, which allows it to appear and behave similarly to other server members.
-
-On the left hand sidebar click **Bot**. On this page, you can configure settings like its [privileged intents](#DOCS_TOPICS_GATEWAY/privileged-intents) or whether it can be installed by other users.
-
-
-Intents determine which events Discord will send your app when you're creating a [Gateway API connection](#DOCS_TOPICS_GATEWAY). For example, if you want your app to do something when users add a reaction to a message, you can pass the `GUILD_MESSAGE_REACTIONS` (`1 << 10`) intent.
-
-Some intents are [privileged](#DOCS_TOPICS_GATEWAY/privileged-intents), meaning they allow your app to access data that may be considered sensitive (like the contents of messages). Privileged intents appear and can be toggled on the **Bot** page in your app's settings. Standard, non-privileged intents don't require any additional permissions or configurations.
-
-More information about intents and a full list of available intents, along with their associated events, is in the [Gateway documentation](#DOCS_TOPICS_GATEWAY/gateway-intents).
-
-
-
-
-There's also a **Token** section on the **Bot** page, which allows you to copy and reset your bot's token.
-
-Bot tokens are used to authorize API requests and carry your bot user's permissions, making them *highly sensitive*. Make sure to *never* share your token or check it into any kind of version control.
-
-Go ahead and copy the token, and store the token somewhere safe (like in a password manager).
-
-> warn
-> You won't be able to view your token again unless you regenerate it, so make sure to keep it somewhere safe.
-
-### Adding scopes and bot permissions
-
-Apps need approval from installing users to perform actions in Discord (like creating a slash command or fetching a list of server members). Let's select a few scopes and permissions to request before installing the app.
-
-
-When creating an app, scopes and permissions determine what your app can do and access in Discord servers.
-
-- [OAuth2 Scopes](#DOCS_TOPICS_OAUTH2/shared-resources-oauth2-scopes) determine what data access and actions your app can take, granted on behalf of an installing or authenticating user.
-- [Permissions](#DOCS_TOPICS_PERMISSIONS/permission-overwrites) are the granular permissions for your bot user, the same as other users in Discord have. They can be approved by the installing user or later updated within server settings or with [permission overwrites](#DOCS_TOPICS_PERMISSIONS/permission-overwrites).
-
-
-Click on **OAuth2** in the left sidebar, then select **URL generator**.
-
-> info
-> The URL generator creates an installation link based on the scopes and permissions you select for your app. You can use the link to install the app onto your own server, or share it with others so they can install it.
-
-For now, just add the **`bot` scope**, which adds your bot user.
-
-After you select `bot`, you can also select different permissions for your bot. For now, just check **Send Messages**.
-
-See a list of all [OAuth2 scopes](#DOCS_TOPICS_OAUTH2/shared-resources-oauth2-scopes), or read more on [permissions](#DOCS_TOPICS_PERMISSIONS) in the documentation.
-
-### Installing your app
-
-Once you add scopes, you should see a URL that you can copy to install your app.
-
-
-
-> info
-> When developing apps, you should build and test in a server that isn't actively used by others. If you don't have your own server already, you can [create one for free](https://support.discord.com/hc/en-us/articles/204849977-How-do-I-create-a-server-).
-
-Copy the URL from above, and paste it into your browser. You'll be guided through the installation flow, where you should make sure you're installing your app on a server where you can develop and test it.
-
-After installing your app, you can head over to your server and see that it has joined ✨
-
-With your app configured and installed, let's start developing it.
-
----
-
-## Step 2: Running your app
-
-All of the code used in the example app can be found in [the GitHub repository](https://github.com/discord/discord-example-app).
-
-To make development a bit simpler, the app uses [discord-interactions](https://github.com/discord/discord-interactions-js), which provides types and helper functions. If you prefer to use other languages or libraries, check out the [Community Resources](#DOCS_TOPICS_COMMUNITY_RESOURCES) documentation.
-
-### Remixing the project
-
-This guide uses Glitch, which lets you clone and develop within your browser. If you'd prefer to develop your app locally, there's instructions on using ngrok [in the README](https://github.com/discord/discord-example-app#running-app-locally).
-
-> info
-> While Glitch is great for development and testing, [it has technical restrictions](https://help.glitch.com/kb/article/17-technical-restrictions/) so other hosting providers should be considered for production apps.
-
-To start, **[remix (or clone) the Glitch project 🎏](https://glitch.com/edit/#!/import/git?url=https://github.com/discord/discord-example-app.git)**.
-
-Once you remix the project, you'll land on a new Glitch project.
-
-
-
-
-- Your **project name** is a unique name for your project, found in the upper-left corner
-- **`.env`** is the file where all of your credentials for your app will be stored
-- **Logs** are where your project's output is found—this is helpful to see if the app is running or information about any errors your app encounters
-- The **Share** button in the top-right corner is where you'll find the live project URL, which you'll need to set up interactivity later in this guide
-
-
-#### Project structure
-
-All of the files for the project are on the left-hand side of your Glitch project. Below is an overview of the main folders and files:
-
-```
-├── examples -> short, feature-specific sample apps
-│ ├── app.js -> finished app.js code
-│ ├── button.js
-│ ├── command.js
-│ ├── modal.js
-│ ├── selectMenu.js
-├── .env -> your credentials and IDs
-├── app.js -> main entrypoint for app
-├── commands.js -> slash command payloads + helpers
-├── game.js -> logic specific to RPS
-├── utils.js -> utility functions and enums
-├── package.json
-├── README.md
-└── .gitignore
-```
-
-### Adding credentials
-
-There's already some code in your `app.js` file, but you'll need your app's token and ID to make requests. All of your credentials can be stored directly in the `.env` file.
-
-First, copy your bot user's token from earlier and paste it in the **`DISCORD_TOKEN`** variable in your `.env` file.
-
-Next, navigate to your app's **General Overview** page, then copy the **App ID** and **Public Key**. Paste the values in your `.env` file as **`APP_ID`** and **`PUBLIC_KEY`**.
-
-With your credentials configured, let's install and handle slash commands.
-
-### Installing slash commands
-
-> info
-> To install slash commands, the app is using [`node-fetch`](https://github.com/node-fetch/node-fetch). You can see the implementation for the installation in `utils.js` within the `DiscordRequest()` function.
-
-The project contains a `register` script you can use to install the commands in `ALL_COMMANDS`, which is defined at the bottom of `commands.js`. It installs the commands as global commands by calling the HTTP API's [`PUT /applications//commands`](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/bulk-overwrite-global-application-commands) endpoint.
-
-If you want to customize your commands or add additional ones, you can reference the command structure in the [commands documentation](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/application-command-object-application-command-structure).
-
-Run the `register` script by clicking **Terminal** at the bottom of your Glitch project and pasting the following command:
-
-```
-npm run register
-```
-
-Hit enter to run the command.
-
-If you navigate back to your server, you should see the slash commands appear. But if you try to run them, nothing will happen since your app isn't receiving or handling any requests from Discord.
-
-
-Discord has two APIs that you can mix-and-match to build apps:
-
-- **[HTTP API](#DOCS_REFERENCE/http-api)** is a REST-like API for general operations like sending and updating data in Discord, or fetching data about a resource.
-- **[Gateway API](#DOCS_REFERENCE/gateway-websocket-api)** is a WebSocket-based API that is helpful for maintaining state or listening to events happening in a Discord server. We won't be using it in this guide, but more information about how to create a Gateway connection and the different events you can listen to are in the [Gateway documentation](#DOCS_TOPICS_GATEWAY).
-
-
----
-
-## Step 3: Handling interactivity
-
-To enable your app to receive slash command requests (and other interactions), Discord needs a public URL to send them. This URL can be configured in your app's settings as **Interaction Endpoint URL**.
-
-### Adding an interaction endpoint URL
-
-Glitch projects have a public URL exposed by default. Copy your project's URL by clicking the **Share** button in the top right corner, then copy the "Live site" project link near the bottom of the modal.
-
-> info
-> If you're developing locally, there are instructions for tunneling requests to your local environment [on the GitHub README](https://github.com/discord/discord-example-app#running-app-locally).
-
-With the link copied, go to your app's settings from [the developer portal](https://discord.com/developers/applications).
-
-On your app's **General Information** page, there's an **Interactive Endpoint URL** option, where you can paste your app's URL and append `/interactions` to it, which is where the Express app is configured to listen for requests.
-
-
-
-Click **Save Changes** and ensure your endpoint is successfully verified.
-
-The sample app handles verification in two ways:
-- It uses the `PUBLIC_KEY` and [discord-interactions package](https://github.com/discord/discord-interactions-js#usage) with a wrapper function (imported from `utils.js`) that makes it conform to [Express's `verify` interface](http://expressjs.com/en/5x/api.html#express.json). This is run on every incoming request to your app.
-- It responds to incoming `PING` requests.
-
-You can learn more about preparing your app to receive interactions in [the interactions documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/receiving-an-interaction).
-
-### Handling slash command requests
-
-With the endpoint verified, navigate to your project's `app.js` file and find the code block that handles the `/test` command:
-
-```javascript
-// "test" command
-if (name === 'test') {
- // Send a message into the channel where command was triggered from
- return res.send({
- type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
- data: {
- // Fetches a random emoji to send from a helper function
- content: 'hello world ' + getRandomEmoji(),
- },
- });
-}
-```
-
-The code above is responding to the interaction with a message in the channel it originated from. You can see all available response types, like responding with a modal, [in the documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-response-object-interaction-callback-type).
-
-> info
-> `InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE` is a constant [exported from `discord-interactions`](https://github.com/discord/discord-interactions-js/blob/main/src/index.ts#L33)
-
-Go to your server and make sure your app's `/test` slash command works. When you trigger it, your app should send a message that contains “hello world” followed by a random emoji.
-
-In the following section, we'll add an additional command that uses slash command options, buttons, and select menus to build the rock-paper-scissors game.
-
----
-
-## Step 4: Adding message components
-
-The `/challenge` command will be how our rock-paper-scissors-style game is initiated. When the command is triggered, the app will send message components to the channel, which will guide the users to complete the game.
-
-### Adding a command with options
-
-The `/challenge` command, called `CHALLENGE_COMMAND` in `commands.js`, has an array of `options`. In our app, the options are objects representing different things that a user can select while playing rock-paper-scissors, generated using keys of `RPSChoices` in `game.js`.
-
-You can read more about command options and their structure [in the documentation](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/application-command-object-application-command-option-structure).
-
-> info
-> While this guide won't touch much on the `game.js` file, feel free to poke around and change commands or the options in the commands.
-
-
-
-To handle the `/challenge` command, add the following code after the `if name === “test”` if block:
-
-```javascript
-// "challenge" command
-if (name === 'challenge' && id) {
- const userId = req.body.member.user.id;
- // User's object choice
- const objectName = req.body.data.options[0].value;
-
- // Create active game using message ID as the game ID
- activeGames[id] = {
- id: userId,
- objectName,
- };
-
- return res.send({
- type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
- data: {
- content: `Rock papers scissors challenge from <@${userId}>`,
- components: [
- {
- type: MessageComponentTypes.ACTION_ROW,
- components: [
- {
- type: MessageComponentTypes.BUTTON,
- // Append the game ID to use later on
- custom_id: `accept_button_${req.body.id}`,
- label: 'Accept',
- style: ButtonStyleTypes.PRIMARY,
- },
- ],
- },
- ],
- },
- });
-}
-```
-
-
-> info
-> If you aren't sure where to paste the code, you can see the full code in `examples/app.js` in the Glitch project or the root `app.js` [on GitHub](https://github.com/discord/discord-example-app/blob/main/app.js).
-
-The above code is doing a few things:
-1. Parses the request body to get the ID of the user who triggered the slash command (`userId`), and the option (object choice) they selected (`objectName`).
-2. Adds a new game to the `activeGames` object using the interaction ID. The active game records the `userId` and `objectName`.
-3. Sends a message back to the channel with a button with a `custom_id` of `accept_button_`.
-
-> warn
-> The sample code uses an object as in-memory storage, but for production apps you should use a database.
-
-When sending a message with [message components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/what-is-a-component), the individual payloads are appended to a `components` array. Actionable components (like buttons) need to be inside of an [action row](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/action-rows), which you can see in the code sample.
-
-Note the unique `custom_id` sent with message components, in this case `accept_button_` with the active game's ID appended to it. A `custom_id` can be used to handle requests that Discord sends you when someone interacts with the component, which you'll see in a moment.
-
-Now when you run the `/challenge` command and pick an option, your app will send a message with an **Accept** button. Let's add code to handle the button press.
-
-
-
-
-
-When users interact with a message component, Discord will send a request with an [interaction type](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-object-interaction-type) of `3` (or the `MESSAGE_COMPONENT` value when using `discord-interactions`).
-
-To set up a handler for the button, we'll check the `type` of interaction, followed by matching the `custom_id`.
-
-Paste the following code under the type handler for `APPLICATION_COMMAND`s:
-
-```javascript
-if (type === InteractionType.MESSAGE_COMPONENT) {
-// custom_id set in payload when sending message component
-const componentId = data.custom_id;
-
- if (componentId.startsWith('accept_button_')) {
- // get the associated game ID
- const gameId = componentId.replace('accept_button_', '');
- // Delete message with token in request body
- const endpoint = `webhooks/${process.env.APP_ID}/${req.body.token}/messages/${req.body.message.id}`;
- try {
- await res.send({
- type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
- data: {
- // Fetches a random emoji to send from a helper function
- content: 'What is your object of choice?',
- // Indicates it'll be an ephemeral message
- flags: InteractionResponseFlags.EPHEMERAL,
- components: [
- {
- type: MessageComponentTypes.ACTION_ROW,
- components: [
- {
- type: MessageComponentTypes.STRING_SELECT,
- // Append game ID
- custom_id: `select_choice_${gameId}`,
- options: getShuffledOptions(),
- },
- ],
- },
- ],
- },
- });
- // Delete previous message
- await DiscordRequest(endpoint, { method: 'DELETE' });
- } catch (err) {
- console.error('Error sending message:', err);
- }
- }
-}
-```
-
-The above code:
-1. Checks for a `custom_id` that matches what we originally sent (in this case, it starts with `accept_button_`). The custom ID also has the active game ID appended, so we store that in `gameID`.
-2. [Deletes the original message](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/delete-original-interaction-response) calling a webhook using `node-fetch` and passing the unique interaction `token` in the request body. This is done to clean up the channel, and so other users can't click the button.
-3. Responds to the request by sending a message that contains a select menu with the object choices for the game. The payload should look fairly similar to the previous one, with the exception of the `options` array and `flags: 64`, [which indicates that the message is ephemeral](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/create-followup-message).
-
-The `options` array is populated using the `getShuffledOptions()` method in `game.js`, which manipulates the `RPSChoices` values to conform to the shape of [message component options](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/select-menu-object-select-option-structure).
-
-
-
-
-
-The last thing to add is code to handle select menu interactions, and to send the result of the game to channel.
-
-Since select menus are just another message component, the code to handle their interactions will be almost identical to buttons.
-
-Modify the code above to handle the select menu:
-
-```javascript
-if (type === InteractionType.MESSAGE_COMPONENT) {
-// custom_id set in payload when sending message component
-const componentId = data.custom_id;
-
- if (componentId.startsWith('accept_button_')) {
- // get the associated game ID
- const gameId = componentId.replace('accept_button_', '');
- // Delete message with token in request body
- const endpoint = `webhooks/${process.env.APP_ID}/${req.body.token}/messages/${req.body.message.id}`;
- try {
- await res.send({
- type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
- data: {
- content: 'What is your object of choice?',
- // Indicates it'll be an ephemeral message
- flags: InteractionResponseFlags.EPHEMERAL,
- components: [
- {
- type: MessageComponentTypes.ACTION_ROW,
- components: [
- {
- type: MessageComponentTypes.STRING_SELECT,
- // Append game ID
- custom_id: `select_choice_${gameId}`,
- options: getShuffledOptions(),
- },
- ],
- },
- ],
- },
- });
- // Delete previous message
- await DiscordRequest(endpoint, { method: 'DELETE' });
- } catch (err) {
- console.error('Error sending message:', err);
- }
- } else if (componentId.startsWith('select_choice_')) {
- // get the associated game ID
- const gameId = componentId.replace('select_choice_', '');
-
- if (activeGames[gameId]) {
- // Get user ID and object choice for responding user
- const userId = req.body.member.user.id;
- const objectName = data.values[0];
- // Calculate result from helper function
- const resultStr = getResult(activeGames[gameId], {
- id: userId,
- objectName,
- });
-
- // Remove game from storage
- delete activeGames[gameId];
- // Update message with token in request body
- const endpoint = `webhooks/${process.env.APP_ID}/${req.body.token}/messages/${req.body.message.id}`;
-
- try {
- // Send results
- await res.send({
- type: InteractionResponseType.CHANNEL_MESSAGE_WITH_SOURCE,
- data: { content: resultStr },
- });
- // Update ephemeral message
- await DiscordRequest(endpoint, {
- method: 'PATCH',
- body: {
- content: 'Nice choice ' + getRandomEmoji(),
- components: []
- }
- });
- } catch (err) {
- console.error('Error sending message:', err);
- }
- }
- }
-}
-```
-
-Similar to earlier code, the code above is getting the user ID and their object selection from the interaction request.
-
-That information, along with the original user's ID and selection from the `activeGames` object, are passed to the `getResult()` function. `getResult()` determines the winner, then builds a readable string to send back to the channel.
-
-We're also calling another webhook, this time to [update the follow-up ephemeral message](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/edit-followup-message) since it can't be deleted.
-
-Finally, the results are sent in the channel using the `CHANNEL_MESSAGE_WITH_SOURCE` interaction response type.
-
-
-
-....and that's it 🎊 Go ahead and test your app and make sure everything works.
-
----
-
-## Next steps
-
-Congrats on building your first Discord app! 🤖
-
-Hopefully you learned a bit about Discord apps, how to configure them, and how to make them interactive. From here, you can continue building out your app or explore what else is possible:
-- Read **[the documentation](#DOCS_INTRO)** for in-depth information about API features
-- Browse the `examples/` folder in this project for smaller, feature-specific code examples
-- Check out **[community resources](#DOCS_TOPICS_COMMUNITY_RESOURCES)** for language-specific tools maintained by community members
-- Read our tutorial on [hosting Discord apps on Cloudflare Workers](#DOCS_TUTORIALS_HOSTING_ON_CLOUDFLARE_WORKERS)
-- Join the **[Discord Developers server](https://discord.gg/discord-developers)** to ask questions about the API, attend events hosted by the Discord API team, and interact with other devs
From 95149ed408c5c73352ea6c758f7d8623c806108b Mon Sep 17 00:00:00 2001
From: Gabriele Todaro <109546049+Gabriele73@users.noreply.github.com>
Date: Sat, 18 May 2024 14:51:00 +0200
Subject: [PATCH 4/6] Create Intro.mdx
---
docs/it/Intro.mdx | 49 +++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 docs/it/Intro.mdx
diff --git a/docs/it/Intro.mdx b/docs/it/Intro.mdx
new file mode 100644
index 0000000000..82d862a4c5
--- /dev/null
+++ b/docs/it/Intro.mdx
@@ -0,0 +1,49 @@
+
+
+
+
+# Welcome to the Discord Developer Platform
+
+The Discord developer platform lets you develop apps to customize and extend Discord for millions of users. A toolkit of [APIs](#DOCS_REFERENCE) and [resources](#DOCS_TOPICS_COMMUNITY_RESOURCES) pair splendidly with a supportive community to help you build bots, integrate 3rd party services, and add Discord support to your game.
+
+
+
+---
+
+## Explore the Platform
+
+#### Engage with Users
+
+Add interactivity to your app with [commands](#DOCS_INTERACTIONS_APPLICATION_COMMANDS) and [message components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS) to build engaging experiences in the place where users are already hanging out.
+
+#### Customize Servers
+
+Customize Discord servers by using apps to do things like [send messages](#DOCS_RESOURCES_CHANNEL/create-message), modify [channels](#DOCS_RESOURCES_CHANNEL) and [guilds](#DOCS_RESOURCES_GUILD), [integrate with AutoMod](#DOCS_RESOURCES_AUTO_MODERATION), or [connect to voice](#DOCS_TOPICS_VOICE_CONNECTIONS).
+
+Plus, use the [Gateway API](#DOCS_TOPICS_GATEWAY) to respond to [real-time events](#DOCS_TOPICS_GATEWAY_EVENTS/receive-events) happening in a server, like when a reaction is added to a message.
+
+#### Connect Metadata
+
+Link and update metadata to enhance Discord for users. Add [Rich Presence](#DOCS_GAME_SDK_ACTIVITIES) to display live data on users' profiles, or [connection metadata](#DOCS_RESOURCES_APPLICATION_ROLE_CONNECTION_METADATA) to make it easy for admins to create roles using metadata associated with your app.
+
+#### Build Interactive Activities and Games
+
+Currently in Developer Preview, the [Embedded App SDK](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK) allows you to build [Activities](#DOCS_ACTIVITIES_OVERVIEW), such as multiplayer games or social experiences, that run inside Discord.
+
+## Discover Developer Resources
+
+#### Find Tools and Libraries
+
+The Discord developer community has built and maintained a ton of different [libraries and tools](#DOCS_TOPICS_COMMUNITY_RESOURCES/libraries) over the years. No matter your experience level or language of choice, there are resources to speed up and simplify app development for you over on the [Community Resources](#DOCS_TOPICS_COMMUNITY_RESOURCES) page.
+
+You can also check out our [Postman collections](https://www.postman.com/discord-api) to try and test API endpoints.
+
+#### Connect with Support
+
+- Join the [Discord Developers server](https://discord.gg/discord-developers) for support, discussion, and events about the Discord developer platform.
+- Explore the [Developer Help Center](https://support-dev.discord.com/hc) to find articles about common topics and questions, or to reach directly out to our developer support team.
+- Use our [GitHub](https://github.com/discord/discord-api-docs) to report API bugs, start a discussion about a developer feature request, or suggest an edit to our open source developer documentation.
+
+So go ahead and [build an app](https://discord.com/developers/applications)! We can’t wait to see what you make.
+
+— Discord
From c9dfba21eb385c84acaf41fa60cbd6f59573dbdc Mon Sep 17 00:00:00 2001
From: Gabriele Todaro <109546049+Gabriele73@users.noreply.github.com>
Date: Sat, 18 May 2024 15:07:01 +0200
Subject: [PATCH 5/6] Update Intro.mdx
full Italian translation for Intro.
---
docs/it/Intro.mdx | 46 +++++++++++++++++++++++-----------------------
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/docs/it/Intro.mdx b/docs/it/Intro.mdx
index 82d862a4c5..a21e58c0e8 100644
--- a/docs/it/Intro.mdx
+++ b/docs/it/Intro.mdx
@@ -1,49 +1,49 @@
-
+
-# Welcome to the Discord Developer Platform
+# Benvenuto alla Piattaforma per i Sviluppatori Discord
-The Discord developer platform lets you develop apps to customize and extend Discord for millions of users. A toolkit of [APIs](#DOCS_REFERENCE) and [resources](#DOCS_TOPICS_COMMUNITY_RESOURCES) pair splendidly with a supportive community to help you build bots, integrate 3rd party services, and add Discord support to your game.
+La piattaforma per i sviluppatori Discord ti permette di sviluppare app per personalizzare ed estendere Discord per milioni di utenti. Un toolkit di [API](#DOCS_REFERENCE) e [risorse](#DOCS_TOPICS_COMMUNITY_RESOURCES) si accoppiano perfettamente con una community amichevole per aiutarti a sviluppare bot , integrare risorse di terzi, e aggiungere integrazioni per Discord sul tuo gioco.
-
+
---
-## Explore the Platform
+## Esplora la Piattaforma
-#### Engage with Users
+#### Interagisci con gli utenti
-Add interactivity to your app with [commands](#DOCS_INTERACTIONS_APPLICATION_COMMANDS) and [message components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS) to build engaging experiences in the place where users are already hanging out.
+Aggiungi interazioni alla tua app con i [comandi](#DOCS_INTERACTIONS_APPLICATION_COMMANDS) e [message components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS) per sviluppare esperienze coinvolgenti per tutti gli utenti.
-#### Customize Servers
+#### Personalizzare Server
-Customize Discord servers by using apps to do things like [send messages](#DOCS_RESOURCES_CHANNEL/create-message), modify [channels](#DOCS_RESOURCES_CHANNEL) and [guilds](#DOCS_RESOURCES_GUILD), [integrate with AutoMod](#DOCS_RESOURCES_AUTO_MODERATION), or [connect to voice](#DOCS_TOPICS_VOICE_CONNECTIONS).
+Personalizza dei server Discord utilizzando app per [mandare messaggi](#DOCS_RESOURCES_CHANNEL/create-message), modificare [canali](#DOCS_RESOURCES_CHANNEL) e [guilds](#DOCS_RESOURCES_GUILD), [integrare con AutoMod](#DOCS_RESOURCES_AUTO_MODERATION), o [connettersi a canali vocali](#DOCS_TOPICS_VOICE_CONNECTIONS).
-Plus, use the [Gateway API](#DOCS_TOPICS_GATEWAY) to respond to [real-time events](#DOCS_TOPICS_GATEWAY_EVENTS/receive-events) happening in a server, like when a reaction is added to a message.
+In più, usa le [API Gateway](#DOCS_TOPICS_GATEWAY) per rispondere a [eventi in tempo reale](#DOCS_TOPICS_GATEWAY_EVENTS/receive-events) che accadono in un server, come l'aggiunta di una reazione ad un messaggio.
-#### Connect Metadata
+#### Connetti Metadati
-Link and update metadata to enhance Discord for users. Add [Rich Presence](#DOCS_GAME_SDK_ACTIVITIES) to display live data on users' profiles, or [connection metadata](#DOCS_RESOURCES_APPLICATION_ROLE_CONNECTION_METADATA) to make it easy for admins to create roles using metadata associated with your app.
+Connetti e aggiorna metadati per migliorare Discord per gli utenti. Aggiungi [Rich Presence](#DOCS_GAME_SDK_ACTIVITIES) per visualizzare dati in tempo reale sui profili degli utenti, o [metadati connessioni](#DOCS_RESOURCES_APPLICATION_ROLE_CONNECTION_METADATA) per facilitare gli admin alla creazione di ruoli con connessioni ai metadati delle tue app.
-#### Build Interactive Activities and Games
+#### Costruisci attività e giochi interattivi
-Currently in Developer Preview, the [Embedded App SDK](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK) allows you to build [Activities](#DOCS_ACTIVITIES_OVERVIEW), such as multiplayer games or social experiences, that run inside Discord.
+Al momento solo in Anteprima Sviluppatori, l' [SDK Embedded App](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK) ti permette di sviluppare [Attività](#DOCS_ACTIVITIES_OVERVIEW), come giochi multiplayer o esperienze sociali, che occorrono all'interno di Discord.
-## Discover Developer Resources
+## Risorse per Sviluppatori Discord
-#### Find Tools and Libraries
+#### Trova Strumenti e Librerie
-The Discord developer community has built and maintained a ton of different [libraries and tools](#DOCS_TOPICS_COMMUNITY_RESOURCES/libraries) over the years. No matter your experience level or language of choice, there are resources to speed up and simplify app development for you over on the [Community Resources](#DOCS_TOPICS_COMMUNITY_RESOURCES) page.
+La community degli sviluppatori Discord ha sviluppato e mantenuto molte diverse [librerie e strumenti](#DOCS_TOPICS_COMMUNITY_RESOURCES/libraries) nel corso degli anni. Non importa il tuo livello di esperienza o il linguaggio che preferisci, ci sono risorse per velocizzare e semplificare lo sviluppo di app per te nella pagina delle [Risorse Community](#DOCS_TOPICS_COMMUNITY_RESOURCES).
-You can also check out our [Postman collections](https://www.postman.com/discord-api) to try and test API endpoints.
+Puoi anche dare un'occhiata alle nostre [collezioni Postman](https://www.postman.com/discord-api) per provare i nostri endpoint API.
-#### Connect with Support
+#### Connettiti con l'assistenza
-- Join the [Discord Developers server](https://discord.gg/discord-developers) for support, discussion, and events about the Discord developer platform.
-- Explore the [Developer Help Center](https://support-dev.discord.com/hc) to find articles about common topics and questions, or to reach directly out to our developer support team.
-- Use our [GitHub](https://github.com/discord/discord-api-docs) to report API bugs, start a discussion about a developer feature request, or suggest an edit to our open source developer documentation.
+- Entra nel [server Discord Developers](https://discord.gg/discord-developers) per aiuto, discussioni, ed eventi per la piattaforma sviluppatori Discord.
+- Esplora l' [Help Center Sviluppatori](https://support-dev.discord.com/hc) per trovare articoli su argomenti e domande comuni, o per contattare direttamente il nostro team di supporto per sviluppatori.
+- Usa il nostro [GitHub](https://github.com/discord/discord-api-docs) per segnalare bug API, iniziare una discussione riguardo una richiesta di funzionalità per sviluppatori, o suggerire una modifica alla nostra documentazione per sviluppatori open source.
-So go ahead and [build an app](https://discord.com/developers/applications)! We can’t wait to see what you make.
+Quindi vai pure a [sviluppare un'app](https://discord.com/developers/applications)! Non vediamo l’ora di vedere cosa realizzerai.
— Discord
From d7e89ca5cb94a0b9cce755ee909660ccf6bb639e Mon Sep 17 00:00:00 2001
From: Gabriele Todaro <109546049+Gabriele73@users.noreply.github.com>
Date: Sat, 18 May 2024 15:08:05 +0200
Subject: [PATCH 6/6] Update Intro.mdx
---
docs/Intro.mdx | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/Intro.mdx b/docs/Intro.mdx
index a856f6b8a0..c70ef04e46 100644
--- a/docs/Intro.mdx
+++ b/docs/Intro.mdx
@@ -1,3 +1,4 @@
+
# Welcome to the Discord Developer Platform
@@ -44,4 +45,4 @@ You can also check out our [Postman collections](https://www.postman.com/discord
So go ahead and [build an app](https://discord.com/developers/applications)! We can’t wait to see what you make.
-— Discord
\ No newline at end of file
+— Discord