Add page about start command (e2b-dev#566)

This PR adds a page in docs explaining details about the start command

Author: mlejva

apps/web/src/app/(docs)/docs/legacy/sandbox/templates/start-cmd/page.mdx apps/web/src/app/(docs)/docs/sandbox-template/start-cmd/page.mdx

@@ -7,7 +7,7 @@ The idea behind the start command feature is to lower the wait times for your us
 
 ## How to add start command
 
-When you are building a sandbox template you can specify the start command by using the [`-c`](/docs/cli/commands#build) option:
+When you are building a sandbox template you can specify the start command by using the [`-c`](/docs/sdk-reference/cli/v1.0.9/template#e2b-template-build) option:
 
 ```bash
 e2b build -c "<your-start-command>"
@@ -17,7 +17,7 @@ When you spawn the custom sandbox you built, the start command will be already r
 
 
 ## How it works
-Every time you are building a [custom sandbox](/docs/guide/custom-sandbox), we create a container based on the [`e2b.Dockerfile`](/docs/sandbox/templates/template-file) file you create in the process.
+Every time you are building a [custom sandbox](/docs/sandbox-template), we create a container based on the [`e2b.Dockerfile`](/docs/sandbox-template#3-customize-e2b-dockerfile) file you create in the process.
 We extract the container's filesystem and start a sandbox with this extracted filesystem.
 We call this sandbox a _template sandbox_.
 
@@ -36,12 +36,16 @@ This allows us to load the sandbox in a few hundred milliseconds any time later
 
 
 ## Limits
-- The network isn't accessible when running the start command.
+- The network isn't accessible when running the start command during the build phase.
 - We wait 15 seconds after we execute the start command before we snapshot the sandbox.
 
 
 ## Logs
-You can retrieve the start command's logs using the SDK during runtime:
+You can retrieve the start command's logs using the SDK during runtime.
+
+<Note>
+These logs are the logs from the start command during the build phase.
+</Note>
 
 <CodeGroup title="Check start command logs" isRunnable={false}>
 ```js {{ language: 'js' }}
@@ -77,6 +81,13 @@ sandbox.close()
 ```
 </CodeGroup>
 
+Or you can use the CLI:
+
+<CodeGroup isTerminalCommand>
+```bash {{ language: 'bash' }}
+e2b sandbox logs <sandbox-id>
+```
+</CodeGroup>
 
 ## Sandbox template config
 The start command is specified inside the `e2b.toml` in the same directory where you ran `e2b build -c "<your-start-command>"`.

apps/web/src/components/Navigation/routes.tsx

@@ -319,6 +319,10 @@ export const docRoutes: NavGroup[] = [
         title: 'Sandbox customization',
         href: '/docs/sandbox-template',
       },
+      {
+        title: 'Start command',
+        href: '/docs/sandbox-template/start-cmd',
+      },
       {
         title: 'Customize CPU & RAM',
         href: '/docs/sandbox-template/customize-cpu-ram',