@knowcode/doc-builder 1.5.11 → 1.5.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,11 +3,11 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
6
- <meta name="description" content="Generated: 2025-07-21 20:30 UTC">
6
+ <meta name="description" content="Generated: 2025-07-22 UTC">
7
7
  <title>Vercel CLI Setup Guide | Doc Builder</title>
8
8
 
9
9
  <meta name="author" content="Lindsay Smith">
10
- <meta name="keywords" content="documentation, markdown, static site generator, vercel, notion-style, https, com">
10
+ <meta name="keywords" content="documentation, markdown, static site generator, vercel, notion-style, cli, https">
11
11
  <meta name="robots" content="index, follow">
12
12
  <link rel="canonical" href="https://doc-builder-delta.vercel.app/vercel-cli-setup-guide.html">
13
13
 
@@ -15,7 +15,7 @@
15
15
  <meta property="og:type" content="article">
16
16
  <meta property="og:url" content="https://doc-builder-delta.vercel.app/vercel-cli-setup-guide.html">
17
17
  <meta property="og:title" content="Vercel CLI Setup Guide | Doc Builder">
18
- <meta property="og:description" content="Generated: 2025-07-21 20:30 UTC">
18
+ <meta property="og:description" content="Generated: 2025-07-22 UTC">
19
19
  <meta property="og:image" content="https://doc-builder-delta.vercel.app/og-default.png">
20
20
  <meta property="og:site_name" content="Doc Builder">
21
21
  <meta property="og:locale" content="en_US">
@@ -25,7 +25,7 @@
25
25
  <meta name="twitter:site" content="@planbbackups">
26
26
  <meta name="twitter:creator" content="@planbbackups">
27
27
  <meta name="twitter:title" content="Vercel CLI Setup Guide | Doc Builder">
28
- <meta name="twitter:description" content="Generated: 2025-07-21 20:30 UTC">
28
+ <meta name="twitter:description" content="Generated: 2025-07-22 UTC">
29
29
  <meta name="twitter:image" content="https://doc-builder-delta.vercel.app/og-default.png">
30
30
 
31
31
  <!-- Custom Meta Tags -->
@@ -36,6 +36,7 @@
36
36
 
37
37
  <!-- Icons -->
38
38
  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css">
39
+ <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.1/src/regular/style.css">
39
40
 
40
41
  <!-- Mermaid -->
41
42
  <script src="https://cdn.jsdelivr.net/npm/mermaid@10.6.1/dist/mermaid.min.js"></script>
@@ -51,7 +52,7 @@
51
52
  "@context": "https://schema.org",
52
53
  "@type": "TechArticle",
53
54
  "headline": "Vercel CLI Setup Guide",
54
- "description": "Generated: 2025-07-21 20:30 UTC",
55
+ "description": "Generated: 2025-07-22 UTC",
55
56
  "author": {
56
57
  "@type": "Person",
57
58
  "name": "Lindsay Smith"
@@ -61,8 +62,8 @@
61
62
  "name": "Knowcode Ltd",
62
63
  "url": "https://knowcode.tech"
63
64
  },
64
- "datePublished": "2025-07-22T08:32:13.144Z",
65
- "dateModified": "2025-07-22T08:32:13.144Z",
65
+ "datePublished": "2025-07-22T11:03:54.351Z",
66
+ "dateModified": "2025-07-22T11:03:54.351Z",
66
67
  "mainEntityOfPage": {
67
68
  "@type": "WebPage",
68
69
  "@id": "https://doc-builder-delta.vercel.app/vercel-cli-setup-guide.html"
@@ -95,7 +96,7 @@
95
96
 
96
97
  <div class="header-actions">
97
98
  <div class="deployment-info">
98
- <span class="deployment-date" title="Built with doc-builder v1.5.9">Last updated: Jul 22, 2025, 08:32 AM UTC</span>
99
+ <span class="deployment-date" title="Built with doc-builder v1.5.12">Last updated: Jul 22, 2025, 11:03 AM UTC</span>
99
100
  </div>
100
101
 
101
102
 
@@ -146,8 +147,8 @@
146
147
  <div class="nav-content" >
147
148
  <a href="/README.html" class="nav-item" data-tooltip="@knowcode/doc-builder."><i class="fas fa-file-alt"></i> Overview</a>
148
149
  <a href="/documentation-index.html" class="nav-item" data-tooltip="This directory contains additional documentation for the @knowcode/doc-builder project, organized by topic and purpose."><i class="fas fa-file-alt"></i> Documentation Index</a>
149
- <a href="/vercel-cli-setup-guide.html" class="nav-item active" data-tooltip="This guide provides comprehensive instructions for installing and configuring the Vercel CLI across different operating systems and environments."><i class="fas fa-file-alt"></i> Vercel Cli Setup Guide</a>
150
- <a href="/vercel-first-time-setup-guide.html" class="nav-item" data-tooltip="This guide provides a detailed explanation of every prompt you&#039;ll encounter during the first-time Vercel setup process when using."><i class="fas fa-file-alt"></i> Vercel First Time Setup Guide</a></div></div>
150
+ <a href="/vercel-cli-setup-guide.html" class="nav-item active" data-tooltip="This guide provides comprehensive instructions for installing the Vercel CLI across different operating systems."><i class="fas fa-file-alt"></i> Vercel Cli Setup Guide</a>
151
+ <a href="/vercel-first-time-setup-guide.html" class="nav-item" data-tooltip="This guide walks you through the streamlined Vercel deployment process when using."><i class="fas fa-file-alt"></i> Vercel First Time Setup Guide</a></div></div>
151
152
  <div class="nav-section" data-level="1">
152
153
  <a class="nav-title collapsible" href="#" data-target="nav-guides-1" >
153
154
  <i class="fas fa-chevron-right collapse-icon"></i><i class="fas fa-folder"></i> Guides
@@ -168,14 +169,14 @@
168
169
  <main class="content">
169
170
  <div class="content-inner">
170
171
  <h1>Vercel CLI Setup Guide</h1>
171
- <p><strong>Generated</strong>: 2025-07-21 20:30 UTC<br><strong>Status</strong>: Complete<br><strong>Verified</strong>: ✅</p>
172
+ <p><strong>Generated</strong>: 2025-07-22 UTC<br><strong>Status</strong>: Complete<br><strong>Verified</strong>: <i class="ph ph-check-circle" aria-label="checked"></i></p>
172
173
  <h2>Overview</h2>
173
- <p>This guide provides comprehensive instructions for installing and configuring the Vercel CLI across different operating systems and environments. The Vercel CLI enables you to deploy projects, manage deployments, and configure projects directly from your terminal.</p>
174
+ <p>This guide provides comprehensive instructions for installing the Vercel CLI across different operating systems. While <code>@knowcode/doc-builder</code> handles most deployment complexity for you, understanding Vercel CLI installation and advanced features can be helpful for power users.</p>
174
175
  <h2>Prerequisites</h2>
175
176
  <ul>
176
- <li><strong>Node.js</strong>: Version 14.x or higher ✅</li>
177
- <li><strong>npm</strong> or <strong>yarn</strong>: Package manager ✅</li>
178
- <li><strong>Git</strong>: For version control (optional but recommended) ✅</li>
177
+ <li><strong>Node.js</strong>: Version 14.x or higher <i class="ph ph-check-circle" aria-label="checked"></i></li>
178
+ <li><strong>npm</strong> or <strong>yarn</strong>: Package manager <i class="ph ph-check-circle" aria-label="checked"></i></li>
179
+ <li><strong>Git</strong>: For version control (optional but recommended) <i class="ph ph-check-circle" aria-label="checked"></i></li>
179
180
  </ul>
180
181
  <h2>Installation Methods</h2>
181
182
  <h3>Method 1: npm (Recommended)</h3>
@@ -194,112 +195,114 @@
194
195
  <p><strong>Homebrew Formula</strong>: <a href="https://formulae.brew.sh/formula/vercel-cli">https://formulae.brew.sh/formula/vercel-cli</a></p>
195
196
  <h3>Method 5: Standalone Binary</h3>
196
197
  <p>Download directly from: <a href="https://vercel.com/download">https://vercel.com/download</a></p>
197
- <h2>Initial Setup</h2>
198
- <h3>1. Verify Installation</h3>
199
- <pre><code class="language-bash">vercel --version
198
+ <h2>Quick Start for doc-builder Users</h2>
199
+ <p>If you&#39;re using <code>@knowcode/doc-builder</code>, you only need to:</p>
200
+ <ol>
201
+ <li><p><strong>Install Vercel CLI</strong> (if not already installed):</p>
202
+ <pre><code class="language-bash">npm install -g vercel
200
203
  </code></pre>
201
- <h3>2. Login to Vercel</h3>
204
+ </li>
205
+ <li><p><strong>Login to Vercel</strong> (one-time setup):</p>
202
206
  <pre><code class="language-bash">vercel login
203
207
  </code></pre>
204
- <p>This will open your browser for authentication or provide email-based login options.</p>
205
- <p><strong>Authentication Guide</strong>: <a href="https://vercel.com/docs/cli#commands/login">https://vercel.com/docs/cli#commands/login</a></p>
206
- <h3>3. Check Authentication Status</h3>
207
- <pre><code class="language-bash">vercel whoami
208
+ </li>
209
+ <li><p><strong>Deploy with doc-builder</strong>:</p>
210
+ <pre><code class="language-bash">npx @knowcode/doc-builder deploy
208
211
  </code></pre>
209
- <h2>Configuration</h2>
210
- <h3>Global Configuration</h3>
212
+ </li>
213
+ </ol>
214
+ <p>That&#39;s it! doc-builder handles all the configuration for you.</p>
215
+ <h2>Detailed Installation Instructions</h2>
216
+ <h2>Understanding Vercel CLI</h2>
217
+ <h3>What Gets Installed</h3>
211
218
  <p>The Vercel CLI stores configuration in:</p>
212
219
  <ul>
213
220
  <li><strong>macOS/Linux</strong>: <code>~/.vercel/</code></li>
214
221
  <li><strong>Windows</strong>: <code>%USERPROFILE%\.vercel\</code></li>
215
222
  </ul>
216
- <p><strong>Configuration Documentation</strong>: <a href="https://vercel.com/docs/cli#configuration">https://vercel.com/docs/cli#configuration</a></p>
217
- <h3>Project Configuration</h3>
218
- <p>Create <code>vercel.json</code> in your project root:</p>
219
- <pre><code class="language-json">{
220
- &quot;version&quot;: 2,
221
- &quot;builds&quot;: [
222
- {
223
- &quot;src&quot;: &quot;package.json&quot;,
224
- &quot;use&quot;: &quot;@vercel/static-build&quot;
225
- }
226
- ],
227
- &quot;routes&quot;: [
228
- {
229
- &quot;src&quot;: &quot;/(.*)&quot;,
230
- &quot;dest&quot;: &quot;/$1&quot;
231
- }
232
- ]
233
- }
234
- </code></pre>
235
- <p><strong>Project Configuration Guide</strong>: <a href="https://vercel.com/docs/project-configuration">https://vercel.com/docs/project-configuration</a></p>
236
- <h2>Common Commands</h2>
237
- <h3>Deploy Commands</h3>
238
- <pre><code class="language-bash"># Deploy to preview
239
- vercel
223
+ <h3>Authentication</h3>
224
+ <pre><code class="language-bash"># Check who you&#39;re logged in as
225
+ vercel whoami
240
226
 
241
- # Deploy to production
242
- vercel --prod
227
+ # Log out
228
+ vercel logout
243
229
 
244
- # Deploy with specific name
245
- vercel --name my-project
230
+ # Log in again
231
+ vercel login
246
232
  </code></pre>
247
- <p><strong>Deployment Documentation</strong>: <a href="https://vercel.com/docs/cli#commands/deploy">https://vercel.com/docs/cli#commands/deploy</a></p>
233
+ <p><strong>Note</strong>: doc-builder automatically generates the necessary <code>vercel.json</code> configuration for you, so you don&#39;t need to create it manually.</p>
234
+ <h2>Advanced Vercel CLI Commands</h2>
235
+ <p>While doc-builder handles deployment, you might want to use these Vercel CLI commands directly:</p>
248
236
  <h3>Project Management</h3>
249
- <pre><code class="language-bash"># List all projects
237
+ <pre><code class="language-bash"># List your projects
250
238
  vercel project ls
251
239
 
252
- # Create new project
253
- vercel project add
240
+ # View project details
241
+ vercel project &lt;project-name&gt;
254
242
 
255
- # Remove project
243
+ # Remove a project
256
244
  vercel project rm &lt;project-name&gt;
257
245
  </code></pre>
258
- <p><strong>Project Commands</strong>: <a href="https://vercel.com/docs/cli#commands/project">https://vercel.com/docs/cli#commands/project</a></p>
246
+ <h3>Domain Management</h3>
247
+ <pre><code class="language-bash"># List domains
248
+ vercel domains ls
249
+
250
+ # Add a domain to a project
251
+ vercel domains add &lt;domain&gt; &lt;project&gt;
252
+
253
+ # Remove a domain
254
+ vercel domains rm &lt;domain&gt;
255
+ </code></pre>
256
+ <h3>Deployment Management</h3>
257
+ <pre><code class="language-bash"># List recent deployments
258
+ vercel ls
259
+
260
+ # Inspect a deployment
261
+ vercel inspect &lt;deployment-url&gt;
262
+
263
+ # Remove a deployment
264
+ vercel rm &lt;deployment-url&gt;
265
+ </code></pre>
259
266
  <h3>Environment Variables</h3>
260
267
  <pre><code class="language-bash"># Add environment variable
261
- vercel env add
268
+ vercel env add &lt;name&gt;
262
269
 
263
270
  # List environment variables
264
271
  vercel env ls
265
272
 
266
273
  # Remove environment variable
267
- vercel env rm &lt;variable-name&gt;
274
+ vercel env rm &lt;name&gt;
268
275
  </code></pre>
269
- <p><strong>Environment Variables Guide</strong>: <a href="https://vercel.com/docs/concepts/projects/environment-variables">https://vercel.com/docs/concepts/projects/environment-variables</a></p>
270
276
  <h2>Troubleshooting</h2>
271
- <h3>Common Issues</h3>
272
- <h4>1. Command Not Found</h4>
277
+ <h3>Common Installation Issues</h3>
278
+ <h4>Command Not Found</h4>
273
279
  <p>If <code>vercel</code> command is not found after installation:</p>
274
- <p><strong>Solution</strong>: Add npm global bin to PATH</p>
275
- <pre><code class="language-bash"># Find npm bin location
280
+ <pre><code class="language-bash"># Find npm global bin location
276
281
  npm bin -g
277
282
 
278
- # Add to PATH (bash/zsh)
283
+ # Add to PATH (add to your ~/.bashrc or ~/.zshrc)
279
284
  export PATH=&quot;$(npm bin -g):$PATH&quot;
280
285
  </code></pre>
281
- <p><strong>PATH Configuration Guide</strong>: <a href="https://vercel.com/docs/cli#installation/troubleshooting">https://vercel.com/docs/cli#installation/troubleshooting</a></p>
282
- <h4>2. Authentication Issues</h4>
283
- <p>If login fails or tokens expire:</p>
284
- <pre><code class="language-bash"># Logout and login again
286
+ <h4>Permission Errors</h4>
287
+ <p>If you get EACCES errors during installation:</p>
288
+ <pre><code class="language-bash"># Option 1: Use npx instead (recommended)
289
+ npx vercel
290
+
291
+ # Option 2: Fix npm permissions
292
+ # See: https://docs.npmjs.com/resolving-eacces-permissions-errors
293
+
294
+ # Option 3: Use a Node version manager like nvm
295
+ # See: https://github.com/nvm-sh/nvm
296
+ </code></pre>
297
+ <h4>Authentication Issues</h4>
298
+ <pre><code class="language-bash"># If login fails, try:
285
299
  vercel logout
286
300
  vercel login
287
- </code></pre>
288
- <p><strong>Authentication Troubleshooting</strong>: <a href="https://vercel.com/docs/cli#authentication/troubleshooting">https://vercel.com/docs/cli#authentication/troubleshooting</a></p>
289
- <h4>3. Permission Errors</h4>
290
- <p>For npm permission errors during global install:</p>
291
- <p><strong>Option 1</strong>: Use npm&#39;s official guide<br><a href="https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally">https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally</a></p>
292
- <p><strong>Option 2</strong>: Use Node Version Manager (nvm)<br><a href="https://github.com/nvm-sh/nvm">https://github.com/nvm-sh/nvm</a></p>
293
- <h4>4. Proxy Configuration</h4>
294
- <p>For corporate environments:</p>
295
- <pre><code class="language-bash"># Set proxy
296
- vercel --proxy http://proxy.company.com:8080
297
301
 
298
- # Or use environment variables
302
+ # For corporate proxies:
299
303
  export HTTP_PROXY=http://proxy.company.com:8080
300
304
  export HTTPS_PROXY=http://proxy.company.com:8080
301
305
  </code></pre>
302
- <p><strong>Proxy Documentation</strong>: <a href="https://vercel.com/docs/cli#using-behind-a-proxy">https://vercel.com/docs/cli#using-behind-a-proxy</a></p>
303
306
  <h2>Platform-Specific Instructions</h2>
304
307
  <h3>macOS</h3>
305
308
  <ol>
@@ -344,107 +347,44 @@ sudo pacman -S nodejs npm
344
347
  </li>
345
348
  </ol>
346
349
  <p><strong>Linux Guide</strong>: <a href="https://vercel.com/docs/cli#linux-installation">https://vercel.com/docs/cli#linux-installation</a></p>
347
- <h2>CI/CD Integration</h2>
348
- <h3>GitHub Actions</h3>
349
- <pre><code class="language-yaml">- name: Install Vercel CLI
350
- run: npm install -g vercel
351
-
352
- - name: Deploy to Vercel
353
- run: vercel --prod --token=${{ secrets.VERCEL_TOKEN }}
354
- </code></pre>
355
- <p><strong>GitHub Actions Guide</strong>: <a href="https://vercel.com/guides/how-can-i-use-github-actions-with-vercel">https://vercel.com/guides/how-can-i-use-github-actions-with-vercel</a></p>
356
- <h3>GitLab CI</h3>
357
- <pre><code class="language-yaml">deploy:
358
- script:
359
- - npm install -g vercel
360
- - vercel --prod --token=$VERCEL_TOKEN
361
- </code></pre>
362
- <p><strong>GitLab CI Guide</strong>: <a href="https://vercel.com/docs/concepts/deployments/git/gitlab">https://vercel.com/docs/concepts/deployments/git/gitlab</a></p>
363
- <h2>Advanced Configuration</h2>
364
- <h3>Custom Build Commands</h3>
365
- <pre><code class="language-json">{
366
- &quot;buildCommand&quot;: &quot;npm run build&quot;,
367
- &quot;outputDirectory&quot;: &quot;dist&quot;,
368
- &quot;devCommand&quot;: &quot;npm run dev&quot;
369
- }
370
- </code></pre>
371
- <h3>Monorepo Support</h3>
372
- <pre><code class="language-bash"># Deploy from subdirectory
373
- vercel --cwd ./apps/web
350
+ <h2>Using Vercel CLI with doc-builder</h2>
351
+ <h3>Deploying to Production</h3>
352
+ <p>While doc-builder handles deployment, you can also use Vercel CLI directly:</p>
353
+ <pre><code class="language-bash"># From your html output directory
354
+ cd html
355
+ vercel --prod
374
356
  </code></pre>
375
- <p><strong>Monorepo Guide</strong>: <a href="https://vercel.com/docs/concepts/monorepos">https://vercel.com/docs/concepts/monorepos</a></p>
376
- <h3>Team Collaboration</h3>
377
- <pre><code class="language-bash"># Switch team context
357
+ <h3>Working with Teams</h3>
358
+ <pre><code class="language-bash"># Switch between personal and team accounts
378
359
  vercel switch
379
360
 
380
- # Invite team member
381
- vercel team invite &lt;email&gt;
361
+ # Deploy to a specific team
362
+ vercel --scope team-name
382
363
  </code></pre>
383
- <p><strong>Team Management</strong>: <a href="https://vercel.com/docs/cli#commands/teams">https://vercel.com/docs/cli#commands/teams</a></p>
384
- <h2>Security Best Practices</h2>
385
- <h3>1. Token Management</h3>
386
- <ul>
387
- <li><strong>Never commit tokens</strong> to version control ✅</li>
388
- <li><strong>Use environment variables</strong> for CI/CD ✅</li>
389
- <li><strong>Rotate tokens regularly</strong> ✅</li>
390
- </ul>
391
- <p><strong>Security Guide</strong>: <a href="https://vercel.com/docs/security">https://vercel.com/docs/security</a></p>
392
- <h3>2. Scoped Tokens</h3>
393
- <p>Create scoped tokens for specific projects:<br><a href="https://vercel.com/account/tokens">https://vercel.com/account/tokens</a></p>
394
- <h3>3. Two-Factor Authentication</h3>
395
- <p>Enable 2FA on your Vercel account:<br><a href="https://vercel.com/docs/accounts/team-members/two-factor-authentication">https://vercel.com/docs/accounts/team-members/two-factor-authentication</a></p>
396
- <h2>Additional Resources</h2>
364
+ <h3>CI/CD Integration</h3>
365
+ <p>For automated deployments:</p>
366
+ <pre><code class="language-yaml"># GitHub Actions example
367
+ - name: Deploy Documentation
368
+ run: |
369
+ npm install -g @knowcode/doc-builder vercel
370
+ doc-builder build
371
+ vercel --prod --token=${{ secrets.VERCEL_TOKEN }}
372
+ </code></pre>
373
+ <h2>Key Resources</h2>
397
374
  <h3>Official Documentation</h3>
398
375
  <ul>
399
- <li><strong>Main CLI Documentation</strong>: <a href="https://vercel.com/docs/cli">https://vercel.com/docs/cli</a></li>
400
- <li><strong>API Reference</strong>: <a href="https://vercel.com/docs/rest-api">https://vercel.com/docs/rest-api</a></li>
401
- <li><strong>Examples Repository</strong>: <a href="https://github.com/vercel/examples">https://github.com/vercel/examples</a></li>
402
- </ul>
403
- <h3>Community Resources</h3>
404
- <ul>
405
- <li><strong>Discord Community</strong>: <a href="https://vercel.com/discord">https://vercel.com/discord</a></li>
406
- <li><strong>GitHub Discussions</strong>: <a href="https://github.com/vercel/vercel/discussions">https://github.com/vercel/vercel/discussions</a></li>
407
- <li><strong>Stack Overflow</strong>: <a href="https://stackoverflow.com/questions/tagged/vercel">https://stackoverflow.com/questions/tagged/vercel</a></li>
408
- </ul>
409
- <h3>Video Tutorials</h3>
410
- <ul>
411
- <li><strong>Official YouTube Channel</strong>: <a href="https://www.youtube.com/c/VercelHQ">https://www.youtube.com/c/VercelHQ</a></li>
412
- <li><strong>Getting Started Playlist</strong>: <a href="https://vercel.com/docs/getting-started-with-vercel">https://vercel.com/docs/getting-started-with-vercel</a></li>
413
- </ul>
414
- <h2>Version History</h2>
415
- <table>
416
- <thead>
417
- <tr>
418
- <th>Version</th>
419
- <th>Release Date</th>
420
- <th>Notes</th>
421
- </tr>
422
- </thead>
423
- <tbody><tr>
424
- <td>Latest</td>
425
- <td>Check npm</td>
426
- <td><a href="https://www.npmjs.com/package/vercel">https://www.npmjs.com/package/vercel</a></td>
427
- </tr>
428
- <tr>
429
- <td>Changelog</td>
430
- <td>All versions</td>
431
- <td><a href="https://github.com/vercel/vercel/releases">https://github.com/vercel/vercel/releases</a></td>
432
- </tr>
433
- </tbody></table>
434
- <h2>Support</h2>
435
- <h3>Getting Help</h3>
436
- <ul>
437
- <li><strong>Documentation</strong>: <a href="https://vercel.com/docs">https://vercel.com/docs</a></li>
438
- <li><strong>Support Portal</strong>: <a href="https://vercel.com/support">https://vercel.com/support</a></li>
439
- <li><strong>Status Page</strong>: <a href="https://www.vercel-status.com/">https://www.vercel-status.com/</a></li>
376
+ <li><strong>Vercel CLI Docs</strong>: <a href="https://vercel.com/docs/cli">https://vercel.com/docs/cli</a></li>
377
+ <li><strong>Vercel Dashboard</strong>: <a href="https://vercel.com/dashboard">https://vercel.com/dashboard</a></li>
378
+ <li><strong>Support</strong>: <a href="https://vercel.com/support">https://vercel.com/support</a></li>
440
379
  </ul>
441
- <h3>Reporting Issues</h3>
380
+ <h3>For doc-builder Users</h3>
442
381
  <ul>
443
- <li><strong>GitHub Issues</strong>: <a href="https://github.com/vercel/vercel/issues">https://github.com/vercel/vercel/issues</a></li>
444
- <li><strong>Feature Requests</strong>: <a href="https://github.com/vercel/vercel/discussions/categories/ideas">https://github.com/vercel/vercel/discussions/categories/ideas</a></li>
382
+ <li><strong>First-Time Setup Guide</strong>: <a href="./vercel-first-time-setup-guide.md">vercel-first-time-setup-guide.md</a></li>
383
+ <li><strong>Troubleshooting Guide</strong>: <a href="./troubleshooting-guide.md">troubleshooting-guide.md</a></li>
384
+ <li><strong>doc-builder Documentation</strong>: <a href="https://www.npmjs.com/package/@knowcode/doc-builder">https://www.npmjs.com/package/@knowcode/doc-builder</a></li>
445
385
  </ul>
446
386
  <hr>
447
- <p>This guide provides comprehensive coverage of Vercel CLI setup and configuration. For the most up-to-date information, always refer to the official Vercel documentation at <a href="https://vercel.com/docs">https://vercel.com/docs</a>.</p>
387
+ <p>This guide covers Vercel CLI installation and advanced usage. For most doc-builder users, the simplified deployment process handles everything automatically. See the <a href="./vercel-first-time-setup-guide.md">First-Time Setup Guide</a> for the streamlined deployment experience.</p>
448
388
 
449
389
  </div>
450
390
  </main>