docs: integrate plugins in setup SDK

Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>

Author: peterpeterparker

docs/reference/plugins.mdx

@@ -49,7 +49,7 @@ import { Bash } from "../components/bash.mdx";
 
 In your Next.js config file — whether it's `next.config.js`, `next.config.ts`, `next.config.mjs` or else — wrap your configuration with `withJuno` to automatically load Juno settings:
 
-```javascript
+```javascript title="next.config.js"
 import { withJuno } from "@junobuild/nextjs-plugin";
 
 export default withJuno();
@@ -63,7 +63,7 @@ The plugin supports following options:
 
 The plugin sets the build output to `export` by default. You can provide additional options as follows:
 
-```javascript
+```javascript title="next.config.js"
 import { withJuno } from "@junobuild/nextjs-plugin";
 
 /** @type {import('next').NextConfig} */
@@ -83,7 +83,7 @@ You can use the `container` option to:
 - Provide a custom container URL (e.g. for an emulator running on a specific port), or
 - Set it to `false` to disable local development behavior entirely.
 
-```javascript title="next.config.mjs"
+```javascript title="next.config.js"
 import { withJuno } from "@junobuild/nextjs-plugin";
 
 /** @type {import('next').NextConfig} */

docs/setup-the-sdk.mdx

@@ -53,25 +53,43 @@ It is generally recommended to initialize globally the library at the top of you
 
 ## Configuration
 
-To connect your application with a container (your Satellite) and other necessary resources, some configuration is required. This setup ensures your application can securely access and initialize the correct Satellite instance, environment variables, and key settings.
+Juno uses a configuration file to determine which Satellite to connect to. Scaffold a minimal config file using:
 
-For most developers, the [Next.js](reference/plugins.mdx#nextjs-plugin) or [Vite](reference/plugins.mdx#vite-plugin) plugins streamline this process by managing environment variables automatically. However, if you're not using one of these plugins, a bit of manual configuration is needed.
+```bash
+npx @junobuild/cli init --minimal
+```
 
-### Automated
+This creates a `juno.config` file — in TypeScript, JavaScript, or JSON depending on your preferences — at the root of your project.
 
-When using the plugins, the configuration handled through a `juno.config` file (TypeScript, JavaScript, or JSON) at your project root is automatically injected within your application. The plugins read the file and automatically load the required information when you build and run your dApp.
+From there, if you're using **Next.js** or **Vite**, install the official plugin. It reads your config file and injects environment variables automatically for the SDK — no need to pass anything manually.
 
-Juno's provided templates come preconfigured with these plugins, so you can quickly get started. For details on setting up the plugin yourself, refer to the [Next.js](reference/plugins.mdx#nextjs-plugin) or [Vite](reference/plugins.mdx#vite-plugin) documentation.
+- [Next.js Plugin](reference/plugins.mdx#nextjs-plugin)
 
-To scaffold a minimal `juno.config` file, run:
+```javascript title="next.config.js"
+import { withJuno } from "@junobuild/nextjs-plugin";
 
-```bash
-npx @junobuild/cli init --minimal
+export default withJuno();
 ```
 
-### Manually configure your application
+- [Vite Plugin](reference/plugins.mdx#vite-plugin)
+
+```javascript title="vite.config.js"
+import juno from "@junobuild/vite-plugin";
 
-If you aren't using a plugin, you can still configure your application by providing the `satelliteId` directly. In this case, add or update the following in your configuration file:
+export default defineConfig({
+  plugins: [juno()]
+});
+```
+
+:::note
+
+The templates already include both the config file and the plugin setup.
+
+:::
+
+#### Not using a plugin?
+
+You can also pass the Satellite ID manually to the SDK, though using the plugins is the preferred approach:
 
 ```typescript
 import { initSatellite } from "@junobuild/core";
@@ -81,6 +99,4 @@ await initSatellite({
 });
 ```
 
-Replace `your-actual-satellite-id` with your actual ID, available in the [console](https://console.juno.build) on the overview page.
-
 [satellite]: terminology.md#satellite