@knowcode/doc-builder 1.7.4 → 1.7.6

package/.claude/settings.local.json

@@ -29,7 +29,12 @@
       "Bash(mkdir:*)",
       "Bash(cp:*)",
       "Bash(./publish.sh)",
-      "Bash(mv:*)"
+      "Bash(mv:*)",
+      "WebFetch(domain:convert-to-markdown.vercel.app)",
+      "Bash(pkill:*)",
+      "Bash(curl:*)",
+      "Bash(./cli.js build:*)",
+      "Bash(./cli.js deploy:*)"
     ],
     "deny": []
   }

package/CHANGELOG.md

@@ -5,6 +5,56 @@ All notable changes to @knowcode/doc-builder will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.7.6] - 2025-07-25
+
+### Added
+- **Attachment Support**: Automatically copy Excel files, PDFs, and other attachments to deployment
+- New configuration option `features.attachments` (enabled by default)
+- Configurable `attachmentTypes` array for supported file extensions
+- `--no-attachments` flag for build and deploy commands to disable attachment copying
+- Support for preserving directory structure when copying attachments
+- Comprehensive file type support including:
+  - Documents: PDF, Excel, Word, PowerPoint, CSV, RTF
+  - Archives: ZIP, TAR, GZ, 7Z, RAR
+  - Images: PNG, JPG, JPEG, GIF, SVG, WEBP, ICO, BMP
+  - Data files: JSON, XML, YAML, YML, TOML
+  - Media: MP4, MP3, WAV, AVI, MOV
+
+### How it Works
+- During build, doc-builder scans for attachment files in your docs directory
+- Files with supported extensions are automatically copied to the output directory
+- Directory structure is preserved (e.g., `docs/data/report.xlsx` → `html/data/report.xlsx`)
+- Links in markdown files to these attachments will work seamlessly in the deployed site
+- Feature is enabled by default but can be disabled with `--no-attachments` flag
+
+### Configuration
+```javascript
+features: {
+  attachments: true  // Enable/disable attachment copying
+},
+attachmentTypes: [
+  '.pdf', '.xlsx', '.docx', // ... etc
+]
+```
+
+## [1.7.5] - 2025-07-25
+
+### Changed
+- **BREAKING**: Authentication is now disabled by default in all configurations
+- Changed default `authentication: false` in both defaultConfig and notionInspiredPreset
+- Public documentation sites now work out of the box without configuration
+- Authentication must be explicitly enabled with `authentication: 'supabase'`
+
+### Added
+- `--no-auth` flag for build command to override authentication settings
+- `--no-auth` flag for deploy command to override authentication settings
+- Documentation for public site deployment workflows
+- Migration guide for authentication changes
+
+### Improved
+- Simplified createDefaultConfig to only prompt for Supabase authentication
+- Better alignment with common use case of public documentation
+
 ## [1.7.4] - 2025-07-24
 
 ### Fixed

package/README.md

@@ -72,11 +72,12 @@ This aligns perfectly with our mission: beautiful documentation should be access
 
 ### 🎯 Advanced Features  
 - 🔍 **SEO Optimized** - Meta tags & structured data
-- 🔐 **Authentication** - Password protection
+- 🔐 **Optional Auth** - Supabase authentication (opt-in)
 - 📊 **Mermaid Diagrams** - Built-in diagram support
 - 🌙 **Dark Mode** - Automatic theme switching
 - ☁️ **Vercel Deploy** - One-command deployment
 - ✅ **Google Verification** - Search Console ready
+- 📎 **Attachment Support** - Excel, PDF & more deploy with docs
 
 </td>
 </tr>
@@ -210,20 +211,56 @@ module.exports = {
   
   // Features
   features: {
-    authentication: true,
+    authentication: 'supabase',  // or false for no auth
     changelog: true,
     mermaid: true,
-    darkMode: true
+    darkMode: true,
+    attachments: true           // Copy PDFs, Excel files, etc. (default: true)
   },
   
-  // Authentication
+  // Supabase Authentication
   auth: {
-    username: 'admin',
-    password: 'secret'
+    supabaseUrl: process.env.SUPABASE_URL,
+    supabaseAnonKey: process.env.SUPABASE_ANON_KEY,
+    siteId: process.env.DOC_SITE_ID
   }
 };
 ```
 
+### 🔐 Authentication Setup
+
+For secure documentation sites, use Supabase authentication:
+
+```bash
+# Initialize authentication
+npx @knowcode/doc-builder auth:init
+
+# Add your site to database  
+npx @knowcode/doc-builder auth:add-site --domain docs.example.com --name "My Docs"
+
+# Grant user access
+npx @knowcode/doc-builder auth:grant --email user@example.com --site-id xxx
+```
+
+See the [Supabase Authentication Guide](docs/guides/supabase-auth-setup-guide.md) for complete setup instructions.
+
+### 📎 Attachment Support
+
+doc-builder automatically copies attachment files (Excel, PDF, images, etc.) to your deployment:
+
+- **Enabled by default** - No configuration needed
+- **Preserves directory structure** - Files maintain their relative paths
+- **Supported file types**:
+  - Documents: `.pdf`, `.doc`, `.docx`, `.xls`, `.xlsx`, `.csv`, `.ppt`, `.pptx`
+  - Images: `.png`, `.jpg`, `.jpeg`, `.gif`, `.svg`, `.webp`
+  - Archives: `.zip`, `.tar`, `.gz`, `.7z`, `.rar`
+  - Data files: `.json`, `.xml`, `.yaml`, `.yml`
+  - And more...
+
+**Example**: If you have `docs/data/report.xlsx`, it will be copied to `html/data/report.xlsx` and links like `[Download Report](data/report.xlsx)` will work perfectly.
+
+To disable attachment copying, use the `--no-attachments` flag with build or deploy commands.
+
 ## 📋 Commands Overview
 
 <table>
@@ -273,13 +310,14 @@ Options:
   -i, --input <dir>    Input directory (default: docs)
   -o, --output <dir>   Output directory (default: html)
   --preset <preset>    Use a preset configuration
-  --no-auth           Disable authentication
   --no-changelog      Disable changelog generation
+  --no-attachments    Disable copying of attachment files
 
 Examples:
   doc-builder build                          # Build with defaults
   doc-builder build --input docs --output dist
   doc-builder build --preset notion-inspired
+  doc-builder build --no-attachments         # Build without copying PDFs, Excel files, etc.
 ```
 </details>
 
@@ -294,11 +332,13 @@ Options:
   --no-prod              Deploy as preview
   --force                Force without confirmation
   --production-url <url> Override production URL
+  --no-attachments       Disable copying of attachment files
 
 Examples:
   doc-builder deploy                    # Deploy to production
   doc-builder deploy --no-prod          # Deploy as preview
   doc-builder deploy --production-url my-docs.vercel.app
+  doc-builder deploy --no-attachments  # Deploy without attachment files
 ```
 </details>
 

package/RELEASE-NOTES-1.7.5.md

@@ -0,0 +1,64 @@
+# Release Notes - v1.7.5
+
+## 🎉 Major Change: Authentication is Now Optional by Default!
+
+Starting with v1.7.5, @knowcode/doc-builder defaults to creating **public documentation sites** without authentication. This aligns with the most common use case and makes it even easier to get started.
+
+### What's New
+
+#### 🔓 No Authentication by Default
+- Documentation sites are now public by default
+- No configuration needed for public docs
+- Authentication must be explicitly enabled when needed
+
+#### 🚀 New CLI Flags
+- `--no-auth` flag for both build and deploy commands
+- Override any authentication settings in your config
+- Perfect for quick public deployments
+
+### Examples
+
+```bash
+# Deploy public documentation (default behavior)
+npx @knowcode/doc-builder deploy
+
+# Force public deployment even if config has auth
+npx @knowcode/doc-builder deploy --no-auth
+
+# Enable authentication in config
+# doc-builder.config.js
+module.exports = {
+  features: {
+    authentication: 'supabase'  // Explicitly enable
+  }
+};
+```
+
+### Migration Guide
+
+#### If you want PUBLIC documentation:
+No changes needed! Your sites are now public by default.
+
+#### If you want PRIVATE documentation:
+Add this to your config:
+```javascript
+features: {
+  authentication: 'supabase'
+}
+```
+
+### Why This Change?
+
+- Most documentation should be publicly accessible
+- Reduces friction for new users
+- Makes the tool more intuitive
+- Authentication becomes an intentional choice
+
+### Full Changelog
+
+- **Changed**: Authentication disabled by default in all configurations
+- **Added**: `--no-auth` flags for build and deploy commands
+- **Improved**: Simplified configuration prompts
+- **Docs**: Added public site deployment guide
+
+This is a breaking change, but one that makes the tool simpler and more aligned with common use cases.

package/add-user-clive.sql

@@ -0,0 +1,35 @@
+-- =====================================================
+-- ADD SINGLE USER: clive@hyperforma.co.uk
+-- Site: https://wru-bid-analysis.vercel.app/
+-- =====================================================
+
+-- STEP 1: Check if clive@hyperforma.co.uk exists
+SELECT email, id, created_at, last_sign_in_at
+FROM auth.users 
+WHERE email = 'clive@hyperforma.co.uk';
+
+-- If NO RESULTS above, create the user:
+-- 1. Go to: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka/auth/users
+-- 2. Click "Invite user"
+-- 3. Enter: clive@hyperforma.co.uk
+-- 4. Click "Send invitation"
+
+-- STEP 2: After user is created, grant access
+INSERT INTO docbuilder_access (user_id, site_id)
+VALUES (
+    (SELECT id FROM auth.users WHERE email = 'clive@hyperforma.co.uk'),
+    '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+)
+ON CONFLICT (user_id, site_id) DO NOTHING;
+
+-- STEP 3: Verify access was granted
+SELECT 
+    u.email,
+    u.id as user_id,
+    da.created_at as access_granted,
+    ds.domain as site_domain
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+JOIN docbuilder_sites ds ON ds.id = da.site_id
+WHERE u.email = 'clive@hyperforma.co.uk'
+AND da.site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';

package/add-user-lindsay-fixed.sql

@@ -0,0 +1,85 @@
+-- =====================================================
+-- ADD SINGLE USER: lindsay@knowcode.tech
+-- Site: https://wru-bid-analysis.vercel.app/
+-- =====================================================
+
+-- STEP 1: Update domain (only run once - you've already done this)
+-- UPDATE docbuilder_sites 
+-- SET domain = 'wru-bid-analysis.vercel.app',
+--     name = 'WRU Bid Analysis Documentation'
+-- WHERE id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- =====================================================
+-- STEP 2: CHECK IF USER EXISTS (RUN THIS FIRST!)
+-- =====================================================
+SELECT email, id, created_at 
+FROM auth.users 
+WHERE email = 'lindsay@knowcode.tech';
+
+-- ⚠️ IF THE ABOVE QUERY RETURNS NO ROWS, YOU MUST CREATE THE USER FIRST!
+
+-- =====================================================
+-- STEP 3: CREATE USER IN SUPABASE (if not exists)
+-- =====================================================
+-- Go to: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka/auth/users
+-- 1. Click the "Invite user" button
+-- 2. Enter email: lindsay@knowcode.tech
+-- 3. Click "Send invitation"
+-- 4. User will receive email to set password
+-- 5. WAIT for user to appear in the auth.users table before continuing!
+
+-- =====================================================
+-- STEP 4: VERIFY USER NOW EXISTS
+-- =====================================================
+-- Run this again to get the user ID:
+SELECT email, id 
+FROM auth.users 
+WHERE email = 'lindsay@knowcode.tech';
+
+-- Copy the ID from above (it will look like: 123e4567-e89b-12d3-a456-426614174000)
+
+-- =====================================================
+-- STEP 5: GRANT ACCESS (only after user exists!)
+-- =====================================================
+-- Option A: If Step 4 returned a user, run this:
+INSERT INTO docbuilder_access (user_id, site_id)
+SELECT 
+    u.id,
+    '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+FROM auth.users u
+WHERE u.email = 'lindsay@knowcode.tech'
+AND EXISTS (
+    SELECT 1 FROM auth.users WHERE email = 'lindsay@knowcode.tech'
+);
+
+-- Option B: If you have the user ID from Step 4, use it directly:
+-- INSERT INTO docbuilder_access (user_id, site_id)
+-- VALUES (
+--     'paste-user-id-here',
+--     '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+-- );
+
+-- =====================================================
+-- STEP 6: VERIFY ACCESS WAS GRANTED
+-- =====================================================
+SELECT 
+    u.email,
+    u.id as user_id,
+    da.created_at as access_granted
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+WHERE u.email = 'lindsay@knowcode.tech';
+
+-- =====================================================
+-- TROUBLESHOOTING
+-- =====================================================
+-- If you still get errors, check:
+-- 1. Does the user exist? 
+SELECT COUNT(*) as user_exists FROM auth.users WHERE email = 'lindsay@knowcode.tech';
+
+-- 2. Do they already have access?
+SELECT COUNT(*) as has_access 
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+WHERE u.email = 'lindsay@knowcode.tech' 
+AND da.site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';

package/add-user-lindsay.sql

@@ -0,0 +1,68 @@
+-- =====================================================
+-- ADD SINGLE USER: lindsay@knowcode.tech
+-- Site: https://wru-bid-analysis.vercel.app/
+-- =====================================================
+
+-- STEP 1: Update domain (only run once)
+UPDATE docbuilder_sites 
+SET domain = 'wru-bid-analysis.vercel.app',
+    name = 'WRU Bid Analysis Documentation'
+WHERE id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- Verify domain is correct
+SELECT id, domain, name FROM docbuilder_sites 
+WHERE id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- =====================================================
+-- STEP 2: Check if lindsay@knowcode.tech exists
+-- =====================================================
+SELECT email, id, created_at, last_sign_in_at
+FROM auth.users 
+WHERE email = 'lindsay@knowcode.tech';
+
+-- If NO RESULTS above, create the user:
+-- 1. Go to: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka/auth/users
+-- 2. Click "Invite user"
+-- 3. Enter: lindsay@knowcode.tech
+-- 4. Click "Send invitation"
+
+-- =====================================================
+-- STEP 3: After user is created, grant access
+-- =====================================================
+-- Run this AFTER the user exists in Supabase
+INSERT INTO docbuilder_access (user_id, site_id)
+VALUES (
+    (SELECT id FROM auth.users WHERE email = 'lindsay@knowcode.tech'),
+    '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+)
+ON CONFLICT (user_id, site_id) DO NOTHING;
+
+-- =====================================================
+-- STEP 4: Verify access was granted
+-- =====================================================
+SELECT 
+    u.email,
+    u.id as user_id,
+    da.created_at as access_granted,
+    ds.domain as site_domain
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+JOIN docbuilder_sites ds ON ds.id = da.site_id
+WHERE u.email = 'lindsay@knowcode.tech'
+AND da.site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- Should show:
+-- email: lindsay@knowcode.tech
+-- access_granted: (timestamp)
+-- site_domain: wru-bid-analysis.vercel.app
+
+-- =====================================================
+-- TROUBLESHOOTING
+-- =====================================================
+-- If access wasn't granted, check for errors:
+SELECT id, email FROM auth.users WHERE email = 'lindsay@knowcode.tech';
+
+-- If user can't log in after getting access:
+-- 1. Clear browser cache
+-- 2. Check they're using correct URL: https://wru-bid-analysis.vercel.app/
+-- 3. Verify they set their password from invite email

package/add-user-pmorgan.sql

@@ -0,0 +1,35 @@
+-- =====================================================
+-- ADD SINGLE USER: pmorgan@wru.cymru
+-- Site: https://wru-bid-analysis.vercel.app/
+-- =====================================================
+
+-- STEP 1: Check if pmorgan@wru.cymru exists
+SELECT email, id, created_at, last_sign_in_at
+FROM auth.users 
+WHERE email = 'pmorgan@wru.cymru';
+
+-- If NO RESULTS above, create the user:
+-- 1. Go to: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka/auth/users
+-- 2. Click "Invite user"
+-- 3. Enter: pmorgan@wru.cymru
+-- 4. Click "Send invitation"
+
+-- STEP 2: After user is created, grant access
+INSERT INTO docbuilder_access (user_id, site_id)
+VALUES (
+    (SELECT id FROM auth.users WHERE email = 'pmorgan@wru.cymru'),
+    '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+)
+ON CONFLICT (user_id, site_id) DO NOTHING;
+
+-- STEP 3: Verify access was granted
+SELECT 
+    u.email,
+    u.id as user_id,
+    da.created_at as access_granted,
+    ds.domain as site_domain
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+JOIN docbuilder_sites ds ON ds.id = da.site_id
+WHERE u.email = 'pmorgan@wru.cymru'
+AND da.site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';

package/add-user-robbie.sql

@@ -0,0 +1,35 @@
+-- =====================================================
+-- ADD SINGLE USER: robbie.macintosh@marbledropper.com
+-- Site: https://wru-bid-analysis.vercel.app/
+-- =====================================================
+
+-- STEP 1: Check if robbie.macintosh@marbledropper.com exists
+SELECT email, id, created_at, last_sign_in_at
+FROM auth.users 
+WHERE email = 'robbie.macintosh@marbledropper.com';
+
+-- If NO RESULTS above, create the user:
+-- 1. Go to: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka/auth/users
+-- 2. Click "Invite user"
+-- 3. Enter: robbie.macintosh@marbledropper.com
+-- 4. Click "Send invitation"
+
+-- STEP 2: After user is created, grant access
+INSERT INTO docbuilder_access (user_id, site_id)
+VALUES (
+    (SELECT id FROM auth.users WHERE email = 'robbie.macintosh@marbledropper.com'),
+    '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+)
+ON CONFLICT (user_id, site_id) DO NOTHING;
+
+-- STEP 3: Verify access was granted
+SELECT 
+    u.email,
+    u.id as user_id,
+    da.created_at as access_granted,
+    ds.domain as site_domain
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+JOIN docbuilder_sites ds ON ds.id = da.site_id
+WHERE u.email = 'robbie.macintosh@marbledropper.com'
+AND da.site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';

package/add-wru-users.sql

@@ -0,0 +1,105 @@
+-- =====================================================
+-- ADD USERS TO WRU BID ANALYSIS DOCUMENTATION
+-- Site: https://wru-bid-analysis.vercel.app/
+-- Date: 2025-07-25
+-- =====================================================
+
+-- STEP 1: Update the domain to match your Vercel deployment
+UPDATE docbuilder_sites 
+SET domain = 'wru-bid-analysis.vercel.app',
+    name = 'WRU Bid Analysis Documentation'
+WHERE id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- Verify the domain update
+SELECT id, domain, name FROM docbuilder_sites 
+WHERE id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- =====================================================
+-- STEP 2: CHECK IF USERS EXIST
+-- =====================================================
+-- Run this first to see which users already exist
+SELECT email, id, created_at 
+FROM auth.users 
+WHERE email IN (
+    'pmorgan@wru.cymru',
+    'clive@hyperforma.co.uk',
+    'robbie.macintosh@marbledropper.com',
+    'lindsay@knowcode.tech'
+);
+
+-- =====================================================
+-- IMPORTANT: CREATE MISSING USERS FIRST!
+-- =====================================================
+-- For any users that don't exist above:
+-- 1. Go to Supabase Dashboard: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka
+-- 2. Navigate to Authentication → Users
+-- 3. Click "Invite user" 
+-- 4. Enter each missing email address
+-- 5. They'll receive an email to set their password
+
+-- =====================================================
+-- STEP 3: GRANT ACCESS TO ALL USERS
+-- =====================================================
+-- Run this after all users have been created
+WITH users_to_add AS (
+    SELECT email FROM (VALUES 
+        ('pmorgan@wru.cymru'),
+        ('clive@hyperforma.co.uk'),
+        ('robbie.macintosh@marbledropper.com'),
+        ('lindsay@knowcode.tech')
+    ) AS t(email)
+)
+INSERT INTO docbuilder_access (user_id, site_id)
+SELECT u.id, '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+FROM auth.users u
+JOIN users_to_add ua ON u.email = ua.email
+WHERE NOT EXISTS (
+    -- This prevents duplicate entries if someone already has access
+    SELECT 1 FROM docbuilder_access 
+    WHERE user_id = u.id AND site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+);
+
+-- =====================================================
+-- STEP 4: VERIFY ACCESS WAS GRANTED
+-- =====================================================
+-- Check who now has access to the site
+SELECT 
+    u.email,
+    u.created_at as user_created,
+    da.created_at as access_granted,
+    CASE 
+        WHEN u.last_sign_in_at IS NULL THEN 'Never logged in'
+        ELSE 'Has logged in'
+    END as login_status
+FROM docbuilder_access da
+JOIN auth.users u ON u.id = da.user_id
+WHERE da.site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735'
+ORDER BY da.created_at DESC;
+
+-- =====================================================
+-- TROUBLESHOOTING
+-- =====================================================
+
+-- If someone can't log in, check if they exist:
+SELECT * FROM auth.users WHERE email = 'user@example.com';
+
+-- If someone still can't access after login, verify their access:
+SELECT * FROM docbuilder_access 
+WHERE user_id = (SELECT id FROM auth.users WHERE email = 'user@example.com')
+AND site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- To remove a user's access:
+-- DELETE FROM docbuilder_access
+-- WHERE user_id = (SELECT id FROM auth.users WHERE email = 'user@example.com')
+-- AND site_id = '4d8a53bf-dcdd-48c0-98e0-cd1451518735';
+
+-- =====================================================
+-- USERS BEING ADDED:
+-- =====================================================
+-- 1. pmorgan@wru.cymru
+-- 2. clive@hyperforma.co.uk
+-- 3. robbie.macintosh@marbledropper.com
+-- 4. lindsay@knowcode.tech
+--
+-- Site URL: https://wru-bid-analysis.vercel.app/
+-- Site ID: 4d8a53bf-dcdd-48c0-98e0-cd1451518735