npm - @knowcode/doc-builder - Versions diffs - 1.5.11 → 1.5.13 - Mend

@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.

Files changed (20) hide show

package/CHANGELOG.md +37 -0
package/README.md +13 -12
package/doc-builder.config.js +2 -1
package/html/README.html +25 -24
package/html/documentation-index.html +10 -9
package/html/guides/authentication-guide.html +19 -18
package/html/guides/claude-workflow-guide.html +24 -23
package/html/guides/documentation-standards.html +21 -20
package/html/guides/google-site-verification-guide.html +6 -5
package/html/guides/seo-guide.html +10 -9
package/html/guides/seo-optimization-guide.html +39 -38
package/html/guides/troubleshooting-guide.html +39 -28
package/html/index.html +25 -24
package/html/sitemap.xml +15 -15
package/html/vercel-cli-setup-guide.html +114 -174
package/html/vercel-first-time-setup-guide.html +134 -217
package/lib/config.js +8 -2
package/lib/core-builder.js +7 -2
package/lib/emoji-mapper.js +267 -0
package/package.json +1 -1

package/html/vercel-first-time-setup-guide.html CHANGED Viewed

@@ -3,19 +3,19 @@
 <head>
     <meta charset="UTF-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="description" content="Generated: 2025-07-21 20:45 UTC">
-    <title>Vercel First-Time Setup Guide - Complete Prompt-by...</title>
+    <meta name="description" content="Generated: 2025-07-22 UTC">
+    <title>Vercel First-Time Setup Guide - Simplified Process</title>
     <meta name="author" content="Lindsay Smith">
-    <meta name="keywords" content="documentation, markdown, static site generator, vercel, notion-style, project, your">
+    <meta name="keywords" content="documentation, markdown, static site generator, vercel, notion-style, your, deployment">
     <meta name="robots" content="index, follow">
     <link rel="canonical" href="https://doc-builder-delta.vercel.app/vercel-first-time-setup-guide.html">
     <!-- Open Graph / Facebook -->
     <meta property="og:type" content="article">
     <meta property="og:url" content="https://doc-builder-delta.vercel.app/vercel-first-time-setup-guide.html">
-    <meta property="og:title" content="Vercel First-Time Setup Guide - Complete Prompt-by...">
-    <meta property="og:description" content="Generated: 2025-07-21 20:45 UTC">
+    <meta property="og:title" content="Vercel First-Time Setup Guide - Simplified Process">
+    <meta property="og:description" content="Generated: 2025-07-22 UTC">
     <meta property="og:image" content="https://doc-builder-delta.vercel.app/og-default.png">
     <meta property="og:site_name" content="Doc Builder">
     <meta property="og:locale" content="en_US">
@@ -24,8 +24,8 @@
     <meta name="twitter:card" content="summary_large_image">
     <meta name="twitter:site" content="@planbbackups">
     <meta name="twitter:creator" content="@planbbackups">
-    <meta name="twitter:title" content="Vercel First-Time Setup Guide - Complete Prompt-by...">
-    <meta name="twitter:description" content="Generated: 2025-07-21 20:45 UTC">
+    <meta name="twitter:title" content="Vercel First-Time Setup Guide - Simplified Process">
+    <meta name="twitter:description" content="Generated: 2025-07-22 UTC">
     <meta name="twitter:image" content="https://doc-builder-delta.vercel.app/og-default.png">
     <!-- Custom Meta Tags -->
@@ -36,6 +36,7 @@
     <!-- Icons -->
     <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css">
+    <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.1/src/regular/style.css">
     <!-- Mermaid -->
     <script src="https://cdn.jsdelivr.net/npm/mermaid@10.6.1/dist/mermaid.min.js"></script>
@@ -50,8 +51,8 @@
 {
   "@context": "https://schema.org",
   "@type": "TechArticle",
-  "headline": "Vercel First-Time Setup Guide - Complete Prompt-by-Prompt Walkthrough",
-  "description": "Generated: 2025-07-21 20:45 UTC",
+  "headline": "Vercel First-Time Setup Guide - Simplified Process",
+  "description": "Generated: 2025-07-22 UTC",
   "author": {
     "@type": "Person",
     "name": "Lindsay Smith"
@@ -61,8 +62,8 @@
     "name": "Knowcode Ltd",
     "url": "https://knowcode.tech"
   },
-  "datePublished": "2025-07-22T08:32:13.147Z",
-  "dateModified": "2025-07-22T08:32:13.147Z",
+  "datePublished": "2025-07-22T11:03:54.353Z",
+  "dateModified": "2025-07-22T11:03:54.353Z",
   "mainEntityOfPage": {
     "@type": "WebPage",
     "@id": "https://doc-builder-delta.vercel.app/vercel-first-time-setup-guide.html"
@@ -95,7 +96,7 @@
             <div class="header-actions">
                 <div class="deployment-info">
-                    <span class="deployment-date" title="Built with doc-builder v1.5.9">Last updated: Jul 22, 2025, 08:32 AM UTC</span>
+                    <span class="deployment-date" title="Built with doc-builder v1.5.12">Last updated: Jul 22, 2025, 11:03 AM UTC</span>
                 </div>
@@ -146,8 +147,8 @@
         <div class="nav-content" >
         <a href="/README.html" class="nav-item" data-tooltip="@knowcode/doc-builder."><i class="fas fa-file-alt"></i> Overview</a>
         <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>
-        <a href="/vercel-cli-setup-guide.html" class="nav-item" 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>
-        <a href="/vercel-first-time-setup-guide.html" class="nav-item active" 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>
+        <a href="/vercel-cli-setup-guide.html" class="nav-item" 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>
+        <a href="/vercel-first-time-setup-guide.html" class="nav-item active" 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>
       <div class="nav-section" data-level="1">
         <a class="nav-title collapsible" href="#" data-target="nav-guides-1" >
           <i class="fas fa-chevron-right collapse-icon"></i><i class="fas fa-folder"></i> Guides
@@ -167,251 +168,167 @@
         <!-- Content Area -->
         <main class="content">
             <div class="content-inner">
-                <h1>Vercel First-Time Setup Guide - Complete Prompt-by-Prompt Walkthrough</h1>
-<p><strong>Generated</strong>: 2025-07-21 20:45 UTC<br><strong>Status</strong>: Complete<br><strong>Verified</strong>: ✅</p>
+                <h1>Vercel First-Time Setup Guide - Simplified Process</h1>
+<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>
 <h2>Overview</h2>
-<p>This guide provides a detailed explanation of every prompt you&#39;ll encounter during the first-time Vercel setup process when using <code>@knowcode/doc-builder deploy</code>. Understanding these prompts helps avoid common configuration errors and ensures successful deployment.</p>
-<h2>Pre-Setup Prompts (doc-builder specific)</h2>
-<p>Before Vercel CLI starts, doc-builder asks several configuration questions:</p>
-<h3>1. Project Name Prompt</h3>
+<p>This guide walks you through the streamlined Vercel deployment process when using <code>@knowcode/doc-builder deploy</code>. The new Vercel CLI experience has fewer prompts and clearer instructions, making deployment much simpler than before.</p>
+<h2>The Simplified Process</h2>
+<h3>Step 1: Run the Deploy Command</h3>
+<pre><code class="language-bash">npx @knowcode/doc-builder deploy
+</code></pre>
+<h3>Step 2: doc-builder Configuration</h3>
+<p>The tool will ask a few simple questions:</p>
+<h4>Project Name</h4>
 <pre><code>? What is your project name? › my-docs
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
 <ul>
 <li>This becomes your Vercel project identifier</li>
-<li>It will form part of your deployment URL: <code>project-name.vercel.app</code></li>
-<li>Must be lowercase, alphanumeric with hyphens only</li>
-<li>Auto-generated from your site name with special characters removed</li>
-</ul>
-<p><strong>Best practice</strong>: </p>
-<ul>
-<li>Keep it short and memorable</li>
-<li>Use hyphens instead of spaces</li>
-<li>Example: <code>my-docs</code>, <code>company-docs</code>, <code>api-reference</code></li>
+<li>Will be part of your URL: <code>project-name.vercel.app</code></li>
+<li>Use lowercase letters, numbers, and hyphens only</li>
 </ul>
-<h3>2. Custom Production URL</h3>
+<h4>Custom Production URL (Optional)</h4>
 <pre><code>? Custom production URL (optional)? ›
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
-<ul>
-<li>Leave empty for auto-detection (recommended for new projects)</li>
-<li>Or enter your custom domain/alias if you already have one</li>
-<li>Can be a full URL or just the domain</li>
-</ul>
-<p><strong>Examples</strong>:</p>
-<ul>
-<li>Empty (press Enter) - Vercel will auto-assign</li>
-<li><code>docs.mycompany.com</code> - Custom domain</li>
-<li><code>my-docs-v2.vercel.app</code> - Specific Vercel subdomain</li>
-</ul>
-<h3>3. Framework Preset</h3>
-<pre><code>? Which framework preset? › - Use arrow-keys. Return to submit.
-❯   Other (Static HTML)
-    Next.js
-    Vite
-</code></pre>
-<p><strong>What it means</strong>: ✅</p>
-<ul>
-<li>Determines build settings and optimizations</li>
-<li><strong>ALWAYS choose &quot;Other (Static HTML)&quot;</strong> for doc-builder</li>
-<li>This ensures Vercel treats your docs as pre-built static files</li>
-</ul>
-<p><strong>Why this matters</strong>:</p>
-<ul>
-<li>Wrong selection can trigger unwanted build processes</li>
-<li>May cause deployment failures or missing files</li>
-</ul>
-<h3>4. Public Access</h3>
-<pre><code>? Make the deployment publicly accessible? › (Y/n)
-</code></pre>
-<p><strong>What it means</strong>: ✅</p>
-<ul>
-<li><strong>Yes (Y)</strong>: Anyone with the URL can view your docs</li>
-<li><strong>No (n)</strong>: Only team members can access (requires Vercel login)</li>
-</ul>
-<p><strong>Considerations</strong>:</p>
-<ul>
-<li>Choose Yes for public documentation</li>
-<li>Choose No for internal/private docs</li>
-<li>Can be changed later in Vercel dashboard</li>
-</ul>
-<h2>Vercel CLI Link Process</h2>
-<p>After the initial configuration, Vercel CLI takes over with its own prompts:</p>
-<h3>5. Directory Confirmation</h3>
-<pre><code>? Set up and deploy &quot;~/Documents/.../html&quot;? [Y/n]
-</code></pre>
-<p><strong>What it means</strong>: ✅</p>
-<ul>
-<li>Vercel is asking to deploy from the current directory</li>
-<li>This should show your <code>html</code> output directory path</li>
-<li><strong>ALWAYS answer YES</strong></li>
-</ul>
-<p><strong>Common mistake</strong>: </p>
 <ul>
-<li>If you see a different path, you may be running from wrong directory</li>
-<li>Should be run from project root, not from inside <code>html</code> folder</li>
+<li>Press Enter to skip (recommended for first-time setup)</li>
+<li>Or enter your custom domain if you have one</li>
 </ul>
-<h3>6. Scope Selection</h3>
-<pre><code>? Which scope should contain your project? ›
-❯   Lindsay Smith (lindsay-smith)
-    Another Team (team-slug)
+<h3>Step 3: Vercel CLI Takes Over</h3>
+<p>The new Vercel CLI experience is much simpler with clearer prompts:</p>
+<h4>Deploy Confirmation</h4>
+<pre><code>Vercel CLI 28.0.0
+? Set up and deploy &quot;~/path/to/your/project/html&quot;? [Y/n]
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
 <ul>
-<li>Determines which account/team owns the project</li>
-<li>Personal accounts show as &quot;Your Name (username)&quot;</li>
-<li>Team accounts show as &quot;Team Name (team-slug)&quot;</li>
-<li><strong>Select your personal account for individual projects</strong></li>
+<li>Answer <strong>Yes</strong> to proceed</li>
+<li>This confirms you want to deploy the current directory</li>
 </ul>
-<p><strong>When to use teams</strong>:</p>
-<ul>
-<li>Collaborative projects</li>
-<li>Company/organization deployments</li>
-<li>Shared billing and permissions</li>
-</ul>
-<h3>7. Existing Project Detection</h3>
-<pre><code>? Found project &quot;lindsay-1340s-projects/html&quot;. Link to it? [Y/n]
+<h4>Account Selection</h4>
+<pre><code>? Which scope do you want to deploy to? ›
+  ○ Your Name
+  ○ Your Team (if applicable)
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
 <ul>
-<li>Vercel found a project with similar name/path</li>
-<li>This is often a <strong>false match</strong> - generic names like &quot;html&quot; are common</li>
-<li><strong>ALWAYS answer NO unless you&#39;re 100% sure it&#39;s YOUR project</strong></li>
+<li>Select your personal account or team</li>
+<li>Use arrow keys to navigate, Enter to select</li>
 </ul>
-<p><strong>Why this happens</strong>:</p>
-<ul>
-<li>Vercel searches for projects with matching directory names</li>
-<li>Common folder names (html, docs, dist) often match other projects</li>
-<li>The suggested project usually belongs to someone else</li>
-</ul>
-<h3>8. Link to Different Project</h3>
-<pre><code>? Link to different existing project? [Y/n]
+<h4>Project Name Confirmation</h4>
+<pre><code>? What&#39;s your project&#39;s name? (my-docs)
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
-<ul>
-<li><strong>Yes (Y)</strong>: You have an existing Vercel project to connect to</li>
-<li><strong>No (n)</strong>: Create a brand new project</li>
-</ul>
-<p><strong>When to answer YES</strong>:</p>
-<ul>
-<li>You&#39;ve deployed before and want to update existing project</li>
-<li>You created a project in Vercel dashboard first</li>
-<li>You&#39;re reconnecting after deleting <code>.vercel</code> folder</li>
-</ul>
-<p><strong>When to answer NO</strong>:</p>
 <ul>
-<li>First time deploying this documentation</li>
-<li>Want a fresh project with new URL</li>
-<li>Previous project had configuration issues</li>
+<li>Vercel suggests the name you provided earlier</li>
+<li>Press Enter to accept or type a new name</li>
 </ul>
-<h3>9A. Existing Project Name (if answered YES to #8)</h3>
-<pre><code>? What&#39;s the name of your existing project? ›
+<h4>Framework Detection</h4>
+<pre><code>? In which directory is your code located? ./
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
 <ul>
-<li>Enter the exact name of your existing Vercel project</li>
-<li>Must match the project name in your Vercel dashboard</li>
-<li>Case-sensitive</li>
+<li>Vercel automatically detects this is a static site</li>
+<li>Usually defaults to <code>./</code> which is correct</li>
+<li>Press Enter to accept</li>
 </ul>
-<p><strong>How to find project name</strong>:</p>
+<h3>Step 4: Deployment Begins</h3>
+<p>That&#39;s it! Vercel will now:</p>
 <ol>
-<li>Go to <a href="https://vercel.com/dashboard">https://vercel.com/dashboard</a></li>
-<li>Look for your project in the list</li>
-<li>Use the exact name shown</li>
+<li>Upload your files</li>
+<li>Deploy to their global CDN</li>
+<li>Provide your live URL</li>
 </ol>
-<h3>9B. New Project Name (if answered NO to #8)</h3>
-<pre><code>? What is your project name? › my-docs
+<pre><code><i class="ph ph-check" aria-label="check"></i> Production: https://my-docs.vercel.app [copied to clipboard]
 </code></pre>
-<p><strong>What it means</strong>: ✅</p>
-<ul>
-<li>Creates a new project with this name</li>
-<li>Will become your default URL: <code>project-name.vercel.app</code></li>
-<li>Must be unique across all Vercel projects</li>
-</ul>
-<p><strong>Best practices</strong>:</p>
+<h2>What Changed from the Old Process?</h2>
+<p>The new Vercel CLI is much simpler:</p>
+<h3>Removed Prompts</h3>
 <ul>
-<li>Use same name as initial prompt for consistency</li>
-<li>Keep it descriptive but concise</li>
-<li>Avoid generic names like &quot;docs&quot; or &quot;html&quot;</li>
+<li><i class="ph ph-x-circle" aria-label="error"></i> No more &quot;Found project xyz/html. Link to it?&quot; confusion</li>
+<li><i class="ph ph-x-circle" aria-label="error"></i> No more &quot;Link to different existing project?&quot; complexity</li>
+<li><i class="ph ph-x-circle" aria-label="error"></i> No more manual framework selection (auto-detected)</li>
+<li><i class="ph ph-x-circle" aria-label="error"></i> No more &quot;Make deployment publicly accessible?&quot; (configured later)</li>
 </ul>
-<h2>Critical Post-Setup Configuration</h2>
-<h3>Root Directory Warning</h3>
-<p>After linking, you may see an error about &quot;html/html does not exist&quot;. This means Vercel incorrectly set the Root Directory.</p>
-<p><strong>The Problem</strong>: ❌</p>
+<h3>Improved Experience</h3>
 <ul>
-<li>Vercel sometimes auto-sets Root Directory to &quot;html&quot;</li>
-<li>But we&#39;re already deploying FROM the html directory</li>
-<li>This creates a path like <code>html/html</code> which doesn&#39;t exist</li>
+<li><i class="ph ph-check-circle" aria-label="checked"></i> Clearer prompts with better wording</li>
+<li><i class="ph ph-check-circle" aria-label="checked"></i> Automatic framework detection</li>
+<li><i class="ph ph-check-circle" aria-label="checked"></i> Fewer steps overall</li>
+<li><i class="ph ph-check-circle" aria-label="checked"></i> Less chance for configuration errors</li>
 </ul>
-<p><strong>The Solution</strong>: ✅</p>
+<h2>Post-Deployment Configuration</h2>
+<h3>Making Your Docs Public</h3>
+<p>By default, Vercel may protect your deployment. To make docs publicly accessible:</p>
 <ol>
-<li>Go to your project settings: <code>https://vercel.com/[your-project]/settings</code></li>
-<li>Find &quot;Root Directory&quot; under &quot;Build &amp; Development Settings&quot;</li>
-<li><strong>DELETE any value</strong> - leave it completely empty</li>
-<li>Click &quot;Save&quot;</li>
+<li>Go to your <a href="https://vercel.com/dashboard">Vercel Dashboard</a></li>
+<li>Click on your project</li>
+<li>Navigate to <strong>Settings → Deployment Protection</strong></li>
+<li>Set <strong>Vercel Authentication</strong> to <strong>Disabled</strong></li>
+<li>Click <strong>Save</strong></li>
 </ol>
-<h3>Build Settings Configuration</h3>
-<p>Vercel may also auto-detect build commands that interfere with static deployment.</p>
-<p><strong>Check these settings</strong>:</p>
-<ul>
-<li><strong>Build Command</strong>: Should be empty</li>
-<li><strong>Output Directory</strong>: Should be empty or &quot;./&quot;</li>
-<li><strong>Install Command</strong>: Should be empty</li>
-<li><strong>Development Command</strong>: Should be empty</li>
-</ul>
-<p><strong>If any have values</strong>:</p>
+<h3>Custom Domain (Optional)</h3>
+<p>To add a custom domain:</p>
+<ol>
+<li>Go to <strong>Settings → Domains</strong></li>
+<li>Add your domain</li>
+<li>Follow DNS configuration instructions</li>
+</ol>
+<h3>Environment Variables (If Using Authentication)</h3>
+<p>If you enabled authentication in doc-builder:</p>
 <ol>
-<li>Clear them completely</li>
-<li>Save changes</li>
-<li>Redeploy</li>
+<li>Go to <strong>Settings → Environment Variables</strong></li>
+<li>Add your auth credentials</li>
+<li>Redeploy to apply changes</li>
 </ol>
-<h2>Deployment Protection Settings</h2>
-<p>For public documentation:</p>
+<h2>Troubleshooting</h2>
+<h3>&quot;Vercel CLI not found&quot;</h3>
+<p>If you see this error, install Vercel CLI:</p>
+<pre><code class="language-bash">npm install -g vercel
+</code></pre>
+<h3>&quot;404 Not Found&quot; After Deployment</h3>
+<p>Make sure you:</p>
+<ol>
+<li>Ran the deploy command from your project root</li>
+<li>Have markdown files in your <code>docs/</code> folder</li>
+<li>Didn&#39;t modify the build output</li>
+</ol>
+<h3>&quot;Authentication Required&quot; Error</h3>
+<p>Your deployment is protected. Follow the &quot;Making Your Docs Public&quot; steps above.</p>
+<h3>Deployment Fails</h3>
+<p>Check that:</p>
 <ol>
-<li>Navigate to <strong>Project Settings &gt; General</strong></li>
-<li>Find <strong>&quot;Deployment Protection&quot;</strong> under Security</li>
-<li>Set to <strong>&quot;Disabled&quot;</strong> for public access</li>
-<li>Or configure password protection if needed</li>
+<li>You&#39;re using the latest version: <code>npx @knowcode/doc-builder@latest deploy</code></li>
+<li>Your <code>docs/</code> folder contains <code>.md</code> files</li>
+<li>You have internet connection</li>
 </ol>
-<h2>Common Issues and Solutions</h2>
-<h3>Issue 1: &quot;Cannot read properties of null&quot;</h3>
-<p><strong>Cause</strong>: Build settings conflict<br><strong>Solution</strong>: Clear all build settings in Vercel dashboard</p>
-<h3>Issue 2: &quot;Directory html/html does not exist&quot;</h3>
-<p><strong>Cause</strong>: Root Directory misconfiguration<br><strong>Solution</strong>: Remove &quot;html&quot; from Root Directory setting</p>
-<h3>Issue 3: &quot;404 errors on deployment&quot;</h3>
-<p><strong>Cause</strong>: Files not in correct location<br><strong>Solution</strong>: Ensure you ran <code>doc-builder build</code> before deploying</p>
-<h3>Issue 4: &quot;Permission denied&quot;</h3>
-<p><strong>Cause</strong>: Not logged into Vercel<br><strong>Solution</strong>: Run <code>vercel login</code> first</p>
-<h2>Quick Reference Checklist</h2>
-<pre><code>✅ 1. Project name? → your-project-name
-✅ 2. Custom URL? → [Leave empty or enter domain]
-✅ 3. Framework? → Other (Static HTML)
-✅ 4. Public? → Yes (for public docs)
-✅ 5. Set up ~/html? → YES
-✅ 6. Which scope? → Your account
-✅ 7. Found project &quot;xyz/html&quot;? → NO
-✅ 8. Link to different project? → YES/NO (your choice)
-✅ 9. Project name? → [Based on #8 answer]
-✅ 10. Check Root Directory → Must be EMPTY
+<h2>Quick Checklist</h2>
+<pre><code><i class="ph ph-check-circle" aria-label="checked"></i> 1. Run: npx @knowcode/doc-builder deploy
+<i class="ph ph-check-circle" aria-label="checked"></i> 2. Enter project name (e.g., my-docs)
+<i class="ph ph-check-circle" aria-label="checked"></i> 3. Skip custom URL (press Enter)
+<i class="ph ph-check-circle" aria-label="checked"></i> 4. Confirm deployment when Vercel asks
+<i class="ph ph-check-circle" aria-label="checked"></i> 5. Select your account/scope
+<i class="ph ph-check-circle" aria-label="checked"></i> 6. Accept suggested project name
+<i class="ph ph-check-circle" aria-label="checked"></i> 7. Get your live URL!
 </code></pre>
-<h2>Pro Tips</h2>
+<h2>Best Practices</h2>
 <ol>
-<li><strong>Save your answers</strong>: Document your choices for future reference</li>
-<li><strong>Verify URLs</strong>: Always check the deployment URL matches expectations</li>
-<li><strong>Use unique names</strong>: Avoid conflicts with generic project names</li>
-<li><strong>Check settings</strong>: Always verify Vercel dashboard settings after setup</li>
-<li><strong>Keep it simple</strong>: Don&#39;t add build commands for static sites</li>
+<li><strong>First Time</strong>: Just accept all defaults</li>
+<li><strong>Project Names</strong>: Use descriptive names like <code>company-api-docs</code></li>
+<li><strong>Custom Domains</strong>: Add them after successful deployment</li>
+<li><strong>Updates</strong>: Future deploys are even simpler - just run the same command</li>
 </ol>
 <h2>Next Steps</h2>
-<p>After successful setup:</p>
+<p>After successful deployment:</p>
 <ol>
-<li>Your docs are live at <code>https://[project-name].vercel.app</code></li>
-<li>Future deploys just need: <code>npx @knowcode/doc-builder deploy</code></li>
-<li>Add custom domain in Vercel dashboard if needed</li>
-<li>Configure team access if required</li>
+<li>Visit your live docs at the provided URL</li>
+<li>Make your docs public in Vercel settings if needed</li>
+<li>Add a custom domain if desired</li>
+<li>Share your documentation with the world!</li>
 </ol>
+<h2>Getting Help</h2>
+<ul>
+<li><strong>Vercel Dashboard</strong>: <a href="https://vercel.com/dashboard">https://vercel.com/dashboard</a></li>
+<li><strong>Vercel Support</strong>: <a href="https://vercel.com/support">https://vercel.com/support</a></li>
+<li><strong>doc-builder Issues</strong>: File on GitHub or npm</li>
+</ul>
 <hr>
-<p>This guide covers every prompt in the Vercel first-time setup process. For additional help, refer to the main <a href="./vercel-cli-setup-guide.md">Vercel CLI Setup Guide</a>.</p>
+<p>This guide reflects the new, simplified Vercel deployment process. For additional Vercel CLI configuration options, see the <a href="./vercel-cli-setup-guide.md">Vercel CLI Setup Guide</a>.</p>
             </div>
         </main>

package/lib/config.js CHANGED Viewed

@@ -21,7 +21,10 @@ const defaultConfig = {
     mermaid: true,
     tooltips: true,
     search: false,
-    darkMode: true
+    darkMode: true,
+    phosphorIcons: true,
+    phosphorWeight: 'regular', // Options: thin, light, regular, bold, fill, duotone
+    phosphorSize: '1.2em'      // Relative to text size
   },
   // Authentication (if enabled)
@@ -86,7 +89,10 @@ const notionInspiredPreset = {
     mermaid: true,
     tooltips: true,
     search: false,
-    darkMode: true
+    darkMode: true,
+    phosphorIcons: true,
+    phosphorWeight: 'regular',
+    phosphorSize: '1.2em'
   },
   auth: {

package/lib/core-builder.js CHANGED Viewed

@@ -12,6 +12,7 @@ const {
   generateSitemap,
   generateRobotsTxt
 } = require('./seo');
+const { replaceEmojisWithIcons } = require('./emoji-mapper');
 // Configure marked options
 marked.setOptions({
@@ -144,7 +145,7 @@ function extractSummary(content, maxLength = 150) {
 }
 // Process markdown content
-function processMarkdownContent(content) {
+function processMarkdownContent(content, config = {}) {
   // Convert mermaid code blocks to mermaid divs with titles
   // Process before markdown parsing to prevent breaking up the content
   const mermaidBlocks = [];
@@ -186,6 +187,9 @@ function processMarkdownContent(content) {
     html = html.replace(`MERMAID_BLOCK_${index}`, block);
   });
+  // Replace emojis with Phosphor icons if enabled
+  html = replaceEmojisWithIcons(html, config);
   return html;
 }
@@ -281,6 +285,7 @@ ${seoTags}
     <!-- Icons -->
     <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css">
+    ${config.features?.phosphorIcons ? `<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.1/src/${config.features?.phosphorWeight || 'regular'}/style.css">` : ''}
     <!-- Mermaid -->
     <script src="https://cdn.jsdelivr.net/npm/mermaid@10.6.1/dist/mermaid.min.js"></script>
@@ -612,7 +617,7 @@ async function processMarkdownFile(filePath, outputPath, allFiles, config) {
   const summary = frontMatter.description || extractSummary(content);
   // Process content
-  const htmlContent = processMarkdownContent(content);
+  const htmlContent = processMarkdownContent(content, config);
   // Build navigation
   const navigation = buildNavigationStructure(allFiles, urlPath);