wiki/content/blog/setup-guide.md

title, description, date, slug, published, tags, readTime, featured, featuredOrder, newsletter, layout, image, authorName, authorImage, excerpt

title	description	date	slug	published	tags	readTime	featured	featuredOrder	newsletter	layout	image	authorName	authorImage	excerpt
Setup Guide - Fork and Deploy Your Own Markdown Framework	Step-by-step guide to fork this markdown sync framework, set up Convex backend, and deploy to Netlify in under 10 minutes.	2025-12-14	setup-guide	true	convex netlify tutorial deployment	8 min read	true	1	true	sidebar	/images/setupguide.png	Markdown	/images/authors/markdown.png	Complete guide to fork, set up, and deploy your own markdown framework in under 10 minutes.

Fork and Deploy Your Own Markdown Framework

This guide walks you through forking this markdown framework, setting up your Convex backend, and deploying to Netlify. The entire process takes about 10 minutes.

How publishing works: Once deployed, you write posts in markdown, run npm run sync for development or npm run sync:prod for production, and they appear on your live site immediately. No rebuild or redeploy needed. Convex handles real-time data sync, so all connected browsers update automatically.

Table of Contents

• Fork and Deploy Your Own Markdown Framework
  • Table of Contents
  • Prerequisites
  • Step 1: Fork the Repository
  • Step 2: Set Up Convex
    • Create a Convex Project
    • Verify the Schema
  • Step 3: Sync Your Blog Posts
  • Step 4: Run Locally
  • Step 5: Get Your Convex HTTP URL
  • Step 6: Verify Edge Functions
  • Step 7: Deploy to Netlify
    • Option A: Netlify CLI
    • Option B: Netlify Dashboard
    • Netlify Build Configuration
  • Step 8: Set Up Production Convex
  • Writing Blog Posts
    • Frontmatter Fields
    • How Frontmatter Works
    • Adding Images
    • Sync After Adding Posts
    • Environment Files
    • When to Sync vs Deploy
  • Customizing Your Framework
    • Fork Configuration Options
      • Option 1: Automated (Recommended)
      • Option 2: Manual
    • Files to Update When Forking
    • Site title and description metadata
    • Update Backend Configuration
    • Change the Favicon
    • Change the Site Logo
    • Change the Default Open Graph Image
    • Update Site Configuration
    • Featured Section
    • GitHub Contributions Graph
    • Visitor Map
    • Logo Gallery
    • Blog page
    • Hardcoded Navigation Items
    • Scroll-to-top button
    • Change the Default Theme
    • Change the Font
    • Change Font Sizes
    • Add Static Pages (Optional)
    • Update SEO Meta Tags
    • Update llms.txt and robots.txt
  • Search
    • Using Search
    • How It Works
  • Real-time Stats
  • Newsletter Admin
  • Mobile Navigation
  • Copy Page Dropdown
  • API Endpoints
  • Import External Content
  • Troubleshooting
    • Posts not appearing
    • RSS/Sitemap not working
    • Build failures on Netlify
  • Project Structure
  • Write Page
  • AI Agent chat
  • Next Steps

Prerequisites

Before you start, make sure you have:

• Node.js 18 or higher installed
• A GitHub account
• A Convex account (free at convex.dev)
• A Netlify account (free at netlify.com)

Step 1: Fork the Repository

Fork the repository to your GitHub account:

# Clone your forked repo
git clone https://github.com/waynesutton/markdown-site.git
cd markdown-site

# Install dependencies
npm install

Step 2: Set Up Convex

Convex is the backend that stores your blog posts and serves the API endpoints.

Create a Convex Project

Run the Convex development command:

npx convex dev

This will

1. Prompt you to log in to Convex (opens browser)
2. Ask you to create a new project or select an existing one
3. Generate a .env.local file with your VITE_CONVEX_URL

Keep this terminal running during development. It syncs your Convex functions automatically.

Verify the Schema

The schema is already defined in convex/schema.ts:

import { defineSchema, defineTable } from "convex/server";
import { v } from "convex/values";

export default defineSchema({
  posts: defineTable({
    slug: v.string(),
    title: v.string(),
    description: v.string(),
    content: v.string(),
    date: v.string(),
    published: v.boolean(),
    tags: v.array(v.string()),
    readTime: v.optional(v.string()),
    image: v.optional(v.string()),
    excerpt: v.optional(v.string()),
    featured: v.optional(v.boolean()),
    featuredOrder: v.optional(v.number()),
    authorName: v.optional(v.string()),
    authorImage: v.optional(v.string()),
    lastSyncedAt: v.number(),
  })
    .index("by_slug", ["slug"])
    .index("by_published", ["published"])
    .index("by_featured", ["featured"]),

  pages: defineTable({
    slug: v.string(),
    title: v.string(),
    content: v.string(),
    published: v.boolean(),
    order: v.optional(v.number()),
    excerpt: v.optional(v.string()),
    image: v.optional(v.string()),
    featured: v.optional(v.boolean()),
    featuredOrder: v.optional(v.number()),
    authorName: v.optional(v.string()),
    authorImage: v.optional(v.string()),
    lastSyncedAt: v.number(),
  })
    .index("by_slug", ["slug"])
    .index("by_published", ["published"])
    .index("by_featured", ["featured"]),

  viewCounts: defineTable({
    slug: v.string(),
    count: v.number(),
  }).index("by_slug", ["slug"]),
});

Step 3: Sync Your Blog Posts

Blog posts live in content/blog/ as markdown files. Sync them to Convex:

Development:

npm run sync              # Sync markdown content
npm run sync:discovery    # Update discovery files (AGENTS.md, llms.txt)
npm run sync:all          # Sync content + discovery files together

Production:

npm run sync:prod              # Sync markdown content
npm run sync:discovery:prod   # Update discovery files
npm run sync:all:prod         # Sync content + discovery files together

This reads all markdown files, parses the frontmatter, and uploads them to your Convex database.

Step 4: Run Locally

Start the development server:

npm run dev

Open http://localhost:5173 to see your blog.

Step 5: Get Your Convex HTTP URL

Your Convex deployment has two URLs:

• Client URL: https://your-deployment.convex.cloud (for the React app)
• HTTP URL: https://your-deployment.convex.site (for API endpoints)

Find your deployment name in the Convex dashboard or check .env.local:

# Your .env.local contains something like:
VITE_CONVEX_URL=https://happy-animal-123.convex.cloud

The HTTP URL uses .convex.site instead of .convex.cloud:

https://happy-animal-123.convex.site

Step 6: Verify Edge Functions

The blog uses Netlify Edge Functions to dynamically proxy RSS, sitemap, and API requests to your Convex HTTP endpoints. No manual URL configuration is needed.

Edge functions in netlify/edge-functions/:

• rss.ts - Proxies /rss.xml and /rss-full.xml
• sitemap.ts - Proxies /sitemap.xml
• api.ts - Proxies /api/posts and /api/post
• botMeta.ts - Serves Open Graph HTML to social media crawlers

These functions automatically read VITE_CONVEX_URL from your environment and convert it to the Convex HTTP site URL (.cloud becomes .site).

Step 7: Deploy to Netlify

For detailed Convex + Netlify integration, see the official Convex Netlify Deployment Guide.

Option A: Netlify CLI

# Install Netlify CLI
npm install -g netlify-cli

# Login to Netlify
netlify login

# Initialize site
netlify init

# Deploy
npm run deploy

Option B: Netlify Dashboard

1. Go to app.netlify.com
2. Click "Add new site" then "wImport an existing project"
3. Connect your GitHub repository
4. Configure build settings:
   • Build command: npm ci --include=dev && npx convex deploy --cmd 'npm run build'
   • Publish directory: dist
5. Add environment variables:
   • CONVEX_DEPLOY_KEY: Generate from Convex Dashboard > Project Settings > Deploy Key
   • VITE_CONVEX_URL: Your production Convex URL (e.g., https://your-deployment.convex.cloud)
6. Click "Deploy site"

The CONVEX_DEPLOY_KEY deploys functions at build time. The VITE_CONVEX_URL is required for edge functions to proxy RSS, sitemap, and API requests at runtime.

Netlify Build Configuration

The netlify.toml file includes the correct build settings:

[build]
  command = "npm ci --include=dev && npx convex deploy --cmd 'npm run build'"
  publish = "dist"

[build.environment]
  NODE_VERSION = "20"

Key points:

• npm ci --include=dev forces devDependencies to install even when NODE_ENV=production
• The build script uses npx vite build to resolve vite from node_modules
• @types/node is required for TypeScript to recognize process.env

Step 8: Set Up Production Convex

For production, deploy your Convex functions:

npx convex deploy

This creates a production deployment. Update your Netlify environment variable with the production URL if different.

Writing Blog Posts

Create new posts in content/blog/:

---
title: "Your Post Title"
description: "A brief description for SEO and social sharing"
date: "2025-01-15"
slug: "your-post-url"
published: true
tags: ["tag1", "tag2"]
readTime: "5 min read"
image: "/images/my-post-image.png"
---

Your markdown content here...

Frontmatter Fields

Field	Required	Description
title	Yes	Post title
description	Yes	Short description for SEO
date	Yes	Publication date (YYYY-MM-DD)
slug	Yes	URL path (must be unique)
published	Yes	Set to true to publish
tags	Yes	Array of topic tags
readTime	No	Estimated reading time
image	No	Header/Open Graph image URL
excerpt	No	Short excerpt for card view
featured	No	Set true to show in featured section
featuredOrder	No	Order in featured section (lower = first)
authorName	No	Author display name shown next to date
authorImage	No	Round author avatar image URL
rightSidebar	No	Enable right sidebar with CopyPageDropdown (opt-in, requires explicit true)
unlisted	No	Hide from listings but allow direct access via slug. Set true to hide from blog listings, featured sections, tag pages, search results, and related posts. Post remains accessible via direct link.

How Frontmatter Works

Frontmatter is the YAML metadata at the top of each markdown file between --- markers. Here is how it flows through the system:

Content directories:

• content/blog/*.md contains blog posts with frontmatter
• content/pages/*.md contains static pages with frontmatter

Processing flow:

1. Markdown files in content/blog/ and content/pages/ contain YAML frontmatter
2. scripts/sync-posts.ts uses gray-matter to parse frontmatter and validate required fields
3. Parsed data is sent to Convex mutations (api.posts.syncPostsPublic, api.pages.syncPagesPublic)
4. convex/schema.ts defines the database structure for storing the data

Adding a new frontmatter field:

To add a custom frontmatter field, update these files:

1. The interface in scripts/sync-posts.ts (PostFrontmatter or PageFrontmatter)
2. The parsing logic in parseMarkdownFile() or parsePageFile() functions
3. The schema in convex/schema.ts
4. The sync mutation in convex/posts.ts or convex/pages.ts

Adding Images

Place images in public/images/ and reference them in your posts:

Header/OG Image (in frontmatter):

image: "/images/my-header.png"

This image appears when sharing on social media. Recommended: 1200x630 pixels.

Inline Images (in content):

![Alt text description](/images/screenshot.png)

Inline images appear in the post content. Alt text is used as the caption below the image.

Image lightbox: By default, images in blog posts and pages open in a full-screen lightbox when clicked. This allows readers to view images at full size. The lightbox can be closed by clicking outside the image, pressing Escape, or clicking the close button. To disable this feature, set imageLightbox.enabled: false in src/config/siteConfig.ts.

External Images:

![Photo](https://images.unsplash.com/photo-xxx?w=800)

Images require git deploy. Images are served as static files from your repository, not synced to Convex. After adding images to public/images/:

1. Commit the image files to git
2. Push to GitHub
3. Wait for Netlify to rebuild

The npm run sync command only syncs markdown text content. Images are deployed when Netlify builds your site. Use npm run sync:discovery to update discovery files (AGENTS.md, llms.txt) when site configuration changes.

Sync After Adding Posts

After adding or editing posts, sync to Convex.

Development sync:

npm run sync              # Sync markdown content
npm run sync:discovery    # Update discovery files
npm run sync:all          # Sync everything together

Production sync:

First, create .env.production.local in your project root:

VITE_CONVEX_URL=https://your-prod-deployment.convex.cloud

Get your production URL from the Convex Dashboard by selecting your project and switching to the Production deployment.

Then sync:

npm run sync:prod              # Sync markdown content
npm run sync:discovery:prod   # Update discovery files
npm run sync:all:prod         # Sync everything together

Environment Files

File	Purpose	Created by
.env.local	Dev deployment URL	npx convex dev (automatic)
.env.production.local	Prod deployment URL	You (manual)

Both files are gitignored. Each developer creates their own local environment files.

When to Sync vs Deploy

What you're changing	Command	Timing
Blog posts in content/blog/	npm run sync	Instant (no rebuild)
Pages in content/pages/	npm run sync	Instant (no rebuild)
Featured items (via frontmatter)	npm run sync	Instant (no rebuild)
Site config changes	npm run sync:discovery	Updates discovery files
Import external URL	npm run import then sync	Instant (no rebuild)
Images in public/images/	Git commit + push	Requires rebuild
siteConfig in Home.tsx	Redeploy	Requires rebuild
Logo gallery config	Redeploy	Requires rebuild
React components/styles	Redeploy	Requires rebuild

Markdown content syncs instantly via Convex. Images and source code require pushing to GitHub for Netlify to rebuild.

Featured items can now be controlled via markdown frontmatter. Add featured: true and featuredOrder: 1 to any post or page, then run npm run sync.

Customizing Your Framework

Fork Configuration Options

After forking, you have two options to configure your site:

Option 1: Automated (Recommended)

Run a single command to configure all files automatically:

# Copy the example config
cp fork-config.json.example fork-config.json

# Edit fork-config.json with your site information
# Then apply all changes
npm run configure

The fork-config.json file includes:

{
  "siteName": "Your Site Name",
  "siteTitle": "Your Tagline",
  "siteDescription": "Your site description.",
  "siteUrl": "https://yoursite.netlify.app",
  "siteDomain": "yoursite.netlify.app",
  "githubUsername": "yourusername",
  "githubRepo": "your-repo-name",
  "contactEmail": "you@example.com",
  "creator": {
    "name": "Your Name",
    "twitter": "https://x.com/yourhandle",
    "linkedin": "https://www.linkedin.com/in/yourprofile/",
    "github": "https://github.com/yourusername"
  },
  "bio": "Your bio text here.",
  "theme": "tan"
}

This updates all 11 configuration files in one step. See FORK_CONFIG.md for the full JSON schema.

Option 2: Manual

Follow the step-by-step guide in FORK_CONFIG.md to update each file manually. The guide includes code snippets for each file and an AI agent prompt for assisted configuration.

Files to Update When Forking

File	What to update
src/config/siteConfig.ts	Site name, title, intro, bio, blog page, logo gallery, GitHub contributions
src/pages/Home.tsx	Intro paragraph text, footer links
convex/http.ts	SITE_URL, SITE_NAME, description strings (3 locations)
convex/rss.ts	SITE_URL, SITE_TITLE, SITE_DESCRIPTION (RSS feeds)
src/pages/Post.tsx	SITE_URL, SITE_NAME, DEFAULT_OG_IMAGE (OG tags)
index.html	Title, meta description, OG tags, JSON-LD
public/llms.txt	Site name, URL, description, topics
public/robots.txt	Sitemap URL and header comment
public/openapi.yaml	API title, server URL, site name in examples
public/.well-known/ai-plugin.json	Site name, descriptions
src/context/ThemeContext.tsx	Default theme

Site title and description metadata

These files contain the main site description text. Update them with your own tagline:

File	What to change
index.html	meta description, og:description, twitter:description, JSON-LD
README.md	Main description at top of file
src/config/siteConfig.ts	name, title, and bio fields
src/pages/Home.tsx	Intro paragraph (hardcoded JSX with links)
convex/http.ts	SITE_NAME constant and description strings (3 locations)
convex/rss.ts	SITE_TITLE and SITE_DESCRIPTION constants
public/llms.txt	Header quote, Name, and Description fields
public/openapi.yaml	API title and example site name
AGENTS.md	Project overview section
content/blog/about-this-blog.md	Title, description, excerpt, and opening paragraph
content/pages/about.md	excerpt field and opening paragraph
content/pages/docs.md	Opening description paragraph

Update Backend Configuration

These constants affect RSS feeds, API responses, sitemaps, and social sharing metadata.

convex/http.ts:

const SITE_URL = "https://your-site.netlify.app";
const SITE_NAME = "Your Site Name";

convex/rss.ts:

const SITE_URL = "https://your-site.netlify.app";
const SITE_TITLE = "Your Site Name";
const SITE_DESCRIPTION = "Your site description for RSS feeds.";

src/pages/Post.tsx:

const SITE_URL = "https://your-site.netlify.app";
const SITE_NAME = "Your Site Name";
const DEFAULT_OG_IMAGE = "/images/og-default.svg";

Change the Favicon

Replace public/favicon.svg with your own SVG icon. The default is a rounded square with the letter "m":

<svg xmlns="http://www.w3.org/2000/svg" width="512" height="512" viewBox="0 0 512 512">
  <rect x="32" y="32" width="448" height="448" rx="96" ry="96" fill="#000000"/>
  <text x="256" y="330" text-anchor="middle" font-size="300" font-weight="800" fill="#ffffff">m</text>
</svg>

To use a different letter or icon, edit the SVG directly or replace the file.

Change the Site Logo

The site uses two logo configurations:

Homepage logo: Edit src/config/siteConfig.ts:

export default {
  logo: "/images/logo.svg", // Set to null to hide the logo
  // ...
};

Replace public/images/logo.svg with your own logo file. Recommended: SVG format, 512x512 pixels.

Inner page logo: Shows on blog page, individual posts, and static pages. Configure in src/config/siteConfig.ts:

innerPageLogo: {
  enabled: true, // Set to false to hide logo on inner pages
  size: 28, // Logo height in pixels (keeps aspect ratio)
},

The inner page logo appears in the top left corner on desktop and top right on mobile. It uses the same logo file as the homepage logo. Set enabled: false to hide it on inner pages while keeping the homepage logo.

Change the Default Open Graph Image

The default OG image is used when a post does not have an image field in its frontmatter. Replace public/images/og-default.svg with your own image.

Recommended dimensions: 1200x630 pixels. Supported formats: PNG, JPG, or SVG.

Update the reference in src/pages/Post.tsx:

const DEFAULT_OG_IMAGE = "/images/og-default.svg";

Update Site Configuration

Edit src/config/siteConfig.ts to customize:

export default {
  name: "Your Name",
  title: "Your Title",
  logo: "/images/logo.svg", // null to hide homepage logo
  intro: "Your introduction...",
  bio: "Your bio...",

  // Blog page configuration
  blogPage: {
    enabled: true, // Enable /blog route
    showInNav: true, // Show in navigation
    title: "Blog", // Nav link and page title
    order: 0, // Nav order (lower = first)
  },

  // Hardcoded navigation items for React routes
  hardcodedNavItems: [
    {
      slug: "stats",
      title: "Stats",
      order: 10,
      showInNav: true, // Set to false to hide from nav
    },
    {
      slug: "write",
      title: "Write",
      order: 20,
      showInNav: true,
    },
  ],

  // Inner page logo configuration
  innerPageLogo: {
    enabled: true, // Set to false to hide logo on inner pages
    size: 28, // Logo height in pixels (keeps aspect ratio)
  },

  // Featured section options
  featuredViewMode: "list", // 'list' or 'cards'
  showViewToggle: true, // Let users switch between views

  // Logo gallery (static grid or scrolling marquee with clickable links)
  logoGallery: {
    enabled: true, // Set false to hide
    images: [
      { src: "/images/logos/logo1.svg", href: "https://example.com" },
      { src: "/images/logos/logo2.svg", href: "https://another.com" },
    ],
    position: "above-footer", // or 'below-featured'
    speed: 30, // Seconds for one scroll cycle
    title: "Built with",
    scrolling: false, // false = static grid, true = scrolling marquee
    maxItems: 4, // Number of logos when scrolling is false
  },

  links: {
    docs: "/setup-guide",
    convex: "https://convex.dev",
  },
};

Featured Section

The homepage featured section shows posts and pages marked with featured: true in their frontmatter. It supports two display modes:

1. List view (default): Bullet list of links
2. Card view: Grid of cards showing title and excerpt

Add a post to featured section:

Add these fields to any post or page frontmatter:

featured: true
featuredOrder: 1
excerpt: "A short description that appears on the card."
image: "/images/my-thumbnail.png"

Then run npm run sync. The post appears in the featured section instantly. No redeploy needed.

Field	Description
featured	Set true to show in featured section
featuredOrder	Order in featured section (lower = first)
excerpt	Short text shown on card view
image	Thumbnail for card view (displays as square)

Thumbnail images: In card view, the image field displays as a square thumbnail above the title. Non-square images are automatically cropped to center. Square thumbnails: 400x400px minimum (800x800px for retina).

Posts without images: Cards display without the image area. The card shows just the title and excerpt with adjusted padding.

Order featured items:

Use featuredOrder to control display order. Lower numbers appear first. Posts and pages are sorted together. Items without featuredOrder appear after numbered items, sorted by creation time.

Toggle view mode:

Users can toggle between list and card views using the icon button next to "Get started:". To change the default view, set featuredViewMode: "cards" in siteConfig.

GitHub Contributions Graph

Display your GitHub contribution activity on the homepage. Configure in siteConfig:

gitHubContributions: {
  enabled: true,           // Set to false to hide
  username: "yourusername", // Your GitHub username
  showYearNavigation: true, // Show arrows to navigate between years
  linkToProfile: true,      // Click graph to open GitHub profile
  title: "GitHub Activity", // Optional title above the graph
},

Option	Description
enabled	true to show, false to hide
username	Your GitHub username
showYearNavigation	Show prev/next year buttons
linkToProfile	Click graph to visit GitHub profile
title	Text above graph (set to undefined to hide)

The graph displays with theme-aware colors that match each site theme (dark, light, tan, cloud). Uses the public github-contributions-api.jogruber.de API (no GitHub token required).

Visitor Map

Display real-time visitor locations on a world map on the stats page. Uses Netlify's built-in geo detection (no third-party API needed). Privacy friendly: only stores city, country, and coordinates. No IP addresses stored.

Configure in siteConfig:

visitorMap: {
  enabled: true,        // Set to false to hide the visitor map
  title: "Live Visitors", // Optional title above the map
},

Option	Description
enabled	true to show, false to hide
title	Text above map (set to undefined to hide)

The map displays with theme-aware colors. Visitor dots pulse to indicate live sessions. Location data comes from Netlify's automatic geo headers at the edge.

Logo Gallery

The homepage includes a logo gallery that can scroll infinitely or display as a static grid. Customize or disable it in siteConfig:

Disable the gallery:

logoGallery: {
  enabled: false, // Set to false to hide
  // ...
},

Replace with your own logos:

1. Add your logo images to public/images/logos/ (SVG recommended)
2. Update the images array with your logos and links:

logoGallery: {
  enabled: true,
  images: [
    { src: "/images/logos/your-logo-1.svg", href: "https://example.com" },
    { src: "/images/logos/your-logo-2.svg", href: "https://anothersite.com" },
  ],
  position: "above-footer",
  speed: 30,
  title: "Built with",
  scrolling: false, // false = static grid, true = scrolling marquee
  maxItems: 4, // Number of logos to show when scrolling is false
},

Each logo object supports:

• src: Path to the logo image (required)
• href: URL to link to when clicked (optional)

Remove sample logos:

Delete the sample files from public/images/logos/ and clear the images array, or replace them with your own.

Configuration options:

Option	Description
enabled	true to show, false to hide
images	Array of logo objects with src and optional href
position	'above-footer' or 'below-featured'
speed	Seconds for one scroll cycle (lower = faster)
title	Text above gallery (set to undefined to hide)
scrolling	true for infinite scroll, false for static grid
maxItems	Max logos to show when scrolling is false (default: 4)

Display modes:

• Scrolling marquee (scrolling: true): Infinite horizontal scroll animation. All logos display in a continuous loop.
• Static grid (scrolling: false): Centered grid showing the first maxItems logos without animation.

Logos display in grayscale and colorize on hover.

Blog page

The site supports a dedicated blog page at /blog with two view modes: list view (year-grouped posts) and card view (thumbnail grid). Configure in src/config/siteConfig.ts:

blogPage: {
  enabled: true,         // Enable /blog route
  showInNav: true,       // Show in navigation
  title: "Blog",         // Nav link and page title
  order: 0,              // Nav order (lower = first)
  viewMode: "list",      // Default view: "list" or "cards"
  showViewToggle: true,  // Show toggle button to switch views
},
displayOnHomepage: true, // Show posts on homepage

Option	Description
enabled	Enable the /blog route
showInNav	Show Blog link in navigation
title	Text for nav link and page heading
order	Position in navigation (lower = first)
viewMode	Default view: "list" or "cards"
showViewToggle	Show toggle button to switch views
displayOnHomepage	Show post list on homepage

View modes:

• List view: Year-grouped posts with titles, read time, and dates
• Card view: Grid of cards showing thumbnails, titles, excerpts, and metadata

Card view details:

Cards display post thumbnails (from image frontmatter field), titles, excerpts (or descriptions), read time, and dates. Posts without images show cards without thumbnail areas. Grid is responsive: 3 columns on desktop, 2 on tablet, 1 on mobile.

Display options:

• Homepage only: displayOnHomepage: true, blogPage.enabled: false
• Blog page only: displayOnHomepage: false, blogPage.enabled: true
• Both: displayOnHomepage: true, blogPage.enabled: true

Navigation order: The Blog link merges with page links and sorts by order. Pages use the order field in frontmatter. Set blogPage.order: 5 to position Blog after pages with order 0-4.

View preference: User's view mode choice is saved to localStorage and persists across page visits.

Blog page featured layout:

Posts can be marked as featured on the blog page using the blogFeatured frontmatter field:

---
title: "My Featured Post"
blogFeatured: true
---

The first blogFeatured post displays as a hero card with landscape image, tags, date, title, excerpt, author info, and read more link. Remaining blogFeatured posts display in a 2-column featured row with excerpts. Regular (non-featured) posts display in a 3-column grid without excerpts.

Homepage Post Limit

Limit the number of posts shown on the homepage:

postsDisplay: {
  showOnHome: true,
  homePostsLimit: 5, // Limit to 5 most recent posts (undefined = show all)
  homePostsReadMore: {
    enabled: true,
    text: "Read more blog posts",
    link: "/blog",
  },
},

When posts are limited, an optional "read more" link appears below the list. Only shows when there are more posts than the limit.

Hardcoded Navigation Items

Add React route pages (like /stats, /write) to the navigation menu via siteConfig.ts. These pages are React components, not markdown files.

Configure in src/config/siteConfig.ts:

hardcodedNavItems: [
  {
    slug: "stats",
    title: "Stats",
    order: 10,
    showInNav: true, // Set to false to hide from nav
  },
  {
    slug: "write",
    title: "Write",
    order: 20,
    showInNav: true,
  },
],

Navigation combines three sources in this order:

1. Blog link (if blogPage.enabled and blogPage.showInNav are true)
2. Hardcoded nav items (from hardcodedNavItems array)
3. Markdown pages (from content/pages/ with showInNav: true)

All items sort by order field (lower numbers first), then alphabetically by title.

Hide from navigation: Set showInNav: false to keep a route accessible but hidden from the nav menu. The route still works at its URL, just won't appear in navigation links.

Scroll-to-top button

A scroll-to-top button appears after scrolling down on posts and pages. Configure it in src/components/Layout.tsx:

const scrollToTopConfig: Partial<ScrollToTopConfig> = {
  enabled: true, // Set to false to disable
  threshold: 300, // Show after scrolling 300px
  smooth: true, // Smooth scroll animation
};

Option	Description
enabled	true to show, false to hide
threshold	Pixels scrolled before button appears
smooth	true for smooth scroll, false for jump

The button uses Phosphor ArrowUp icon and works with all four themes. It uses a passive scroll listener for performance.

Change the Default Theme

Edit src/context/ThemeContext.tsx:

const DEFAULT_THEME: Theme = "tan"; // Options: "dark", "light", "tan", "cloud"

Change the Font

The blog uses a serif font by default. You can configure the font in two ways:

Option 1: Configure via siteConfig.ts (Recommended)

Edit src/config/siteConfig.ts:

export const siteConfig: SiteConfig = {
  // ... other config
  fontFamily: "serif", // Options: "serif", "sans", or "monospace"
};

Option 2: Edit global.css directly

Edit src/styles/global.css:

body {
  /* Sans-serif */
  font-family:
    -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;

  /* Serif (default) */
  font-family:
    "New York",
    -apple-system-ui-serif,
    ui-serif,
    Georgia,
    serif;

  /* Monospace */
  font-family: "IBM Plex Mono", "Liberation Mono", ui-monospace, monospace;
}

Available font options:

• serif: New York serif font (default)
• sans: System sans-serif fonts
• monospace: IBM Plex Mono monospace font

Change Font Sizes

All font sizes use CSS variables defined in :root. Customize sizes by editing these variables in src/styles/global.css:

:root {
  /* Base size scale */
  --font-size-base: 16px;
  --font-size-sm: 13px;
  --font-size-lg: 17px;
  --font-size-xl: 18px;
  --font-size-2xl: 20px;
  --font-size-3xl: 24px;

  /* Component-specific (examples) */
  --font-size-blog-content: 17px;
  --font-size-post-title: 32px;
  --font-size-nav-link: 14px;
}

Mobile responsive sizes are defined in a @media (max-width: 768px) block.

Add Static Pages (Optional)

Create optional pages like About, Projects, or Contact. These appear as navigation links in the top right corner.

1. Create a content/pages/ directory
2. Add markdown files with frontmatter:

---
title: "About"
slug: "about"
published: true
order: 1
---

Your page content here...

Field	Required	Description
title	Yes	Page title (shown in nav)
slug	Yes	URL path (e.g., /about)
published	Yes	Set true to show
order	No	Display order (lower = first)
showInNav	No	Show in navigation menu (default: true)
authorName	No	Author display name shown next to date
authorImage	No	Round author avatar image URL
layout	No	Set to "sidebar" for docs-style layout with TOC

3. Run npm run sync to sync pages

Pages appear automatically in the navigation when published.

Hide pages from navigation: Set showInNav: false in page frontmatter to keep a page published and accessible via direct URL, but hidden from the navigation menu. Useful for pages like /projects that you want to link directly but not show in the main nav. Pages with showInNav: false remain searchable and available via API endpoints.

Home intro content: Create content/pages/home.md (slug: home-intro) to sync homepage intro text from markdown. Headings (h1-h6) use blog post styling (blog-h1 through blog-h6) with clickable anchor links. Lists, blockquotes, horizontal rules, and links also use blog styling for consistent typography. Set textAlign: "left", "center", or "right" to control alignment. Run npm run sync to update homepage text instantly without redeploying. Falls back to siteConfig.bio if home-intro page not found.

Footer content via markdown: Create content/pages/footer.md (slug: footer) to manage footer content via markdown sync instead of hardcoding in siteConfig.ts. Run npm run sync to update footer text instantly without touching code. Supports full markdown including links, paragraphs, and line breaks. Falls back to siteConfig.footer.defaultContent if page not found.

Sidebar layout: Add layout: "sidebar" to any post or page frontmatter to enable a docs-style layout with a table of contents sidebar. The sidebar extracts headings (H1, H2, H3) automatically and provides smooth scroll navigation. Only appears if headings exist in the content.

Right sidebar: When enabled in siteConfig.rightSidebar.enabled, posts and pages can display a right sidebar containing the CopyPageDropdown at 1135px+ viewport width. Add rightSidebar: true to frontmatter to enable. Without this field, pages render normally with CopyPageDropdown in the nav bar. When enabled, CopyPageDropdown moves from the navigation bar to the right sidebar on wide screens. The right sidebar is hidden below 1135px, and CopyPageDropdown returns to the nav bar automatically.

Show image at top: Add showImageAtTop: true to display the image field at the top of the post/page above the header. Default behavior: if showImageAtTop is not set or false, image only used for Open Graph previews and featured card thumbnails.

Image lightbox: Images in blog posts and pages automatically open in a full-screen lightbox when clicked (if enabled in siteConfig.imageLightbox.enabled). This allows readers to view images at full size. The lightbox can be closed by clicking outside the image, pressing Escape, or clicking the close button. To disable this feature, set imageLightbox.enabled: false in src/config/siteConfig.ts.

Footer: Footer content can be managed three ways: (1) Create content/pages/footer.md to sync footer content via markdown (recommended), (2) set in frontmatter footer field for per-page overrides, or (3) use siteConfig.footer.defaultContent for static content. The markdown page takes priority over siteConfig when present. Control visibility globally via siteConfig.footer.enabled and per-page via showFooter: true/false frontmatter.

Social footer: Display social icons and copyright below the main footer. Configure via siteConfig.socialFooter. Control visibility per-page via showSocialFooter: true/false frontmatter.

Contact form: Enable contact forms on any page or post via contactForm: true frontmatter. Requires AGENTMAIL_API_KEY and AGENTMAIL_INBOX environment variables in Convex. See the Contact Form section below.

AI Agent chat: The site includes an AI writing assistant (Agent) powered by Anthropic Claude API. Enable Agent on the Write page via siteConfig.aiChat.enabledOnWritePage or in the right sidebar on posts/pages using aiChat: true frontmatter (requires rightSidebar: true). Requires ANTHROPIC_API_KEY environment variable in Convex. See the AI Agent chat section below for setup instructions.

Update SEO Meta Tags

Edit index.html to update:

• Site title
• Meta description
• Open Graph tags
• JSON-LD structured data

Update llms.txt and robots.txt

Edit public/llms.txt and public/robots.txt with your site information.

Tag Pages and Related Posts

Tag pages are available at /tags/[tag] for each tag used in your posts. They display all posts with that tag in a list or card view.

Related posts: Individual blog posts show up to 3 related posts in the footer based on shared tags. Posts are sorted by relevance (number of shared tags) then by date. Only appears on blog posts (not static pages).

Tag links: Tags in post footers link to their respective tag archive pages.

Search

Your blog includes full text search with Command+K keyboard shortcut.

Using Search

Press Command+K (Mac) or Ctrl+K (Windows/Linux) to open the search modal. You can also click the search icon in the top navigation.

Features:

• Real-time results as you type
• Keyboard navigation with arrow keys
• Press Enter to select, Escape to close
• Result snippets with context around matches
• Distinguishes between posts and pages with type badges
• Works with all four themes

How It Works

Search uses Convex full text search indexes on the posts and pages tables. The search queries both title and content fields, deduplicates results, and sorts with title matches first.

Search is automatically available once you deploy. No additional configuration needed.

Real-time Stats

Your blog includes a real-time analytics page at /stats:

• Active visitors: See who is currently on your site and which pages they are viewing
• Total page views: All-time view count across the site
• Unique visitors: Count based on anonymous session IDs
• Views by page: Every page and post ranked by view count

Stats update automatically without refreshing. Powered by Convex subscriptions.

How it works:

• Page views are recorded as event records (not counters) to prevent write conflicts
• Active sessions use a heartbeat system (30 second interval)
• Sessions expire after 2 minutes of inactivity
• A cron job cleans up stale sessions every 5 minutes
• No personal data is stored (only anonymous UUIDs)

Footer Configuration

The footer component displays markdown content and can be configured globally or per-page.

Global configuration:

In src/config/siteConfig.ts:

footer: {
  enabled: true,              // Global toggle for footer
  showOnHomepage: true,       // Show footer on homepage
  showOnPosts: true,          // Default: show footer on blog posts
  showOnPages: true,          // Default: show footer on static pages
  showOnBlogPage: true,       // Show footer on /blog page
  defaultContent: "...",      // Default markdown content
},

Frontmatter override:

Set showFooter: false in post/page frontmatter to hide footer on specific pages. Set footer: "..." to provide custom markdown content.

Footer images: Footer markdown supports images with size control via HTML attributes (width, height, style, class).

Social Footer Configuration

Display social icons and copyright information below the main footer.

Configuration:

In src/config/siteConfig.ts:

socialFooter: {
  enabled: true,
  showOnHomepage: true,
  showOnPosts: true,
  showOnPages: true,
  showOnBlogPage: true,
  socialLinks: [
    { platform: "github", url: "https://github.com/username" },
    { platform: "twitter", url: "https://x.com/handle" },
    { platform: "linkedin", url: "https://linkedin.com/in/profile" },
  ],
  copyright: {
    siteName: "Your Site Name",
    showYear: true, // Auto-updates to current year
  },
},

Supported platforms: github, twitter, linkedin, instagram, youtube, tiktok, discord, website

Frontmatter override:

Set showSocialFooter: false in post/page frontmatter to hide social footer on specific pages.

Right Sidebar Configuration

Enable a right sidebar on posts and pages that displays CopyPageDropdown at wide viewport widths.

Configuration:

In src/config/siteConfig.ts:

rightSidebar: {
  enabled: true,      // Set to false to disable globally
  minWidth: 1135,     // Minimum viewport width to show sidebar
},

Frontmatter usage:

Enable right sidebar on specific posts/pages:

---
title: My Post
rightSidebar: true
---

Features:

• Right sidebar appears at 1135px+ viewport width
• Contains CopyPageDropdown with sharing options
• Three-column layout: left sidebar (TOC), main content, right sidebar
• Hidden below 1135px, CopyPageDropdown returns to nav

Contact Form Configuration

Enable contact forms on any page or post via frontmatter. Messages are sent via AgentMail.

Environment Variables:

Set these in the Convex dashboard:

Variable	Description
AGENTMAIL_API_KEY	Your AgentMail API key
AGENTMAIL_INBOX	Your inbox address for sending
AGENTMAIL_CONTACT_EMAIL	Optional: recipient for contact form messages (defaults to AGENTMAIL_INBOX)

Site Config:

In src/config/siteConfig.ts:

contactForm: {
  enabled: true, // Global toggle for contact form feature
  title: "Get in Touch",
  description: "Send us a message and we'll get back to you.",
},

Frontmatter Usage:

Enable contact form on any page or post:

---
title: Contact Us
slug: contact
contactForm: true
---

The form includes name, email, and message fields. Submissions are stored in Convex and sent via AgentMail to the configured recipient.

Newsletter Admin

A newsletter management interface is available at /newsletter-admin. Use it to view subscribers, send newsletters, and compose custom emails.

Features:

• View and search all subscribers with filtering options (search bar in header)
• Delete subscribers from the admin UI
• Send published blog posts as newsletters
• Write custom emails using markdown formatting
• View recent newsletter sends (last 10, tracks both posts and custom emails)
• Email statistics dashboard with comprehensive metrics

Setup:

1. Enable in src/config/siteConfig.ts:

newsletterAdmin: {
  enabled: true,
  showInNav: false, // Keep hidden, access via direct URL
},

2. Set environment variables in Convex Dashboard:

Variable	Description
AGENTMAIL_API_KEY	Your AgentMail API key
AGENTMAIL_INBOX	Your AgentMail inbox address
AGENTMAIL_CONTACT_EMAIL	Optional recipient for contact forms

Important: If environment variables are not configured, users will see an error message when attempting to use newsletter or contact form features: "AgentMail Environment Variables are not configured in production. Please set AGENTMAIL_API_KEY and AGENTMAIL_INBOX."

Sending newsletters:

Two modes are available:

1. Send Post: Select a blog post to send to all active subscribers
2. Write Email: Compose custom content with markdown support

The admin UI shows send results and provides CLI commands as alternatives.

Mobile Navigation

On mobile and tablet screens (under 768px), a hamburger menu provides navigation. The menu slides out from the left with keyboard navigation (Escape to close) and a focus trap for accessibility. It auto-closes when you navigate to a new route.

Copy Page Dropdown

Each post and page includes a share dropdown with options for AI tools:

Option	Description
Copy page	Copies formatted markdown to clipboard
Open in ChatGPT	Opens ChatGPT with raw markdown URL
Open in Claude	Opens Claude with raw markdown URL
Open in Perplexity	Opens Perplexity with raw markdown URL
View as Markdown	Opens raw .md file in new tab
Download as SKILL.md	Downloads skill file for AI agent training

Git push required for AI links: The "Open in ChatGPT," "Open in Claude," and "Open in Perplexity" options use GitHub raw URLs to fetch content. For these to work, your content must be pushed to GitHub with git push. The npm run sync command syncs content to Convex for your live site, but AI services fetch directly from GitHub.

What you want	Command needed
Content visible on your site	npm run sync or sync:prod
Discovery files updated	npm run sync:discovery or sync:discovery:prod
AI links (ChatGPT/Claude/Perplexity)	git push to GitHub
Both content and discovery	npm run sync:all or sync:all:prod

Download as SKILL.md formats the content as an Anthropic Agent Skills file with metadata, triggers, and instructions sections.

API Endpoints

Your blog includes these API endpoints for search engines and AI:

Endpoint	Description
/stats	Real-time site analytics
/rss.xml	RSS feed with descriptions
/rss-full.xml	RSS feed with full content
/sitemap.xml	Dynamic XML sitemap
/api/posts	JSON list of all posts
/api/post?slug=xxx	Single post as JSON
/api/post?slug=xxx&format=md	Single post as raw markdown
/api/export	Batch export all posts
/raw/{slug}.md	Static raw markdown file
/.well-known/ai-plugin.json	AI plugin manifest
/openapi.yaml	OpenAPI 3.0 specification
/llms.txt	AI agent discovery

Import External Content

Use Firecrawl to import articles from external URLs as markdown posts:

npm run import https://example.com/article

Setup:

1. Get an API key from firecrawl.dev
2. Add to .env.local:

FIRECRAWL_API_KEY=fc-your-api-key

The import script will:

1. Scrape the URL and convert to markdown
2. Create a draft post in content/blog/ locally
3. Extract title and description from the page

Why no npm run import:prod? The import command only creates local markdown files. It does not interact with Convex directly. After importing:

• Run npm run sync to push to development
• Run npm run sync:prod to push to production
• Use npm run sync:all or npm run sync:all:prod to sync content and update discovery files together

Imported posts are created as drafts (published: false). Review, edit, set published: true, then sync to your target environment.

Troubleshooting

Posts not appearing

1. Check that published: true in frontmatter
2. Run npm run sync to sync posts to development
3. Run npm run sync:prod to sync posts to production
4. Use npm run sync:all or npm run sync:all:prod to sync content and update discovery files together
5. Verify posts exist in Convex dashboard

RSS/Sitemap not working

1. Verify VITE_CONVEX_URL is set in Netlify environment variables
2. Check that Convex HTTP endpoints are deployed (npx convex deploy)
3. Test the Convex HTTP URL directly: https://your-deployment.convex.site/rss.xml
4. Verify edge functions exist in netlify/edge-functions/

Build failures on Netlify

Common errors and fixes:

"vite: not found" or "Cannot find package 'vite'"

Netlify sets NODE_ENV=production which skips devDependencies. Fix by using npm ci --include=dev in your build command:

[build]
  command = "npm ci --include=dev && npx convex deploy --cmd 'npm run build'"

Also ensure your build script uses npx:

"build": "npx vite build"

"Cannot find name 'process'"

Add @types/node to devDependencies:

npm install --save-dev @types/node

General checklist:

1. Verify CONVEX_DEPLOY_KEY environment variable is set in Netlify
2. Check that @types/node is in devDependencies
3. Ensure Node.js version is 20 or higher
4. Verify build command includes --include=dev

See netlify-deploy-fix.md for detailed troubleshooting.

Project Structure

markdown-site/
├── content/
│   ├── blog/           # Markdown posts
│   └── pages/          # Static pages (About, Docs, etc.)
├── convex/             # Convex backend functions
│   ├── http.ts         # HTTP endpoints
│   ├── posts.ts        # Post queries/mutations
│   ├── pages.ts        # Page queries/mutations
│   ├── rss.ts          # RSS feed generation
│   ├── stats.ts        # Analytics functions
│   └── schema.ts       # Database schema
├── netlify/
│   └── edge-functions/ # Netlify edge functions
│       ├── rss.ts      # RSS proxy
│       ├── sitemap.ts  # Sitemap proxy
│       ├── api.ts      # API proxy
│       └── botMeta.ts  # OG crawler detection
├── public/
│   ├── images/         # Static images
│   ├── raw/            # Generated raw markdown files
│   ├── robots.txt      # Crawler rules
│   └── llms.txt        # AI agent discovery
├── src/
│   ├── components/     # React components
│   ├── context/        # Theme context
│   ├── hooks/          # Custom hooks
│   ├── pages/          # Page components
│   └── styles/         # Global CSS
├── netlify.toml        # Netlify configuration
└── package.json        # Dependencies

Write Page

A markdown writing page is available at /write (not linked in navigation). Use it to draft content before saving to your markdown files.

Features:

• Three-column Cursor docs-style layout
• Content type selector (Blog Post or Page) with dynamic frontmatter templates
• Frontmatter field reference with individual copy buttons
• Font switcher (Serif/Sans-serif)
• Theme toggle matching site themes
• Word, line, and character counts
• localStorage persistence for content, type, and font preference
• Works with Grammarly and browser spellcheck

Workflow:

1. Go to yourdomain.com/write
2. Select content type (Blog Post or Page)
3. Write your content using the frontmatter reference
4. Click "Copy All" to copy the markdown
5. Save to content/blog/ or content/pages/
6. Run npm run sync or npm run sync:prod

Content is stored in localStorage only and not synced to the database. Refreshing the page preserves your content, but clearing browser data will lose it.

AI Agent mode: When siteConfig.aiChat.enabledOnWritePage is enabled, a toggle button appears in the Actions section. Clicking it replaces the textarea with the AI Agent chat interface. The page title changes to "Agent" when in chat mode. Requires ANTHROPIC_API_KEY environment variable in Convex. See the AI Agent chat section below for setup instructions.

AI Agent chat

The site includes an AI writing assistant (Agent) powered by Anthropic Claude API. Agent can be enabled in two places:

1. Write page (/write)

Enable Agent mode on the Write page via siteConfig.aiChat.enabledOnWritePage. When enabled, a toggle button appears in the Actions section. Clicking it replaces the textarea with the Agent chat interface. The page title changes to "Agent" when in chat mode.

Configuration:

// src/config/siteConfig.ts
aiChat: {
  enabledOnWritePage: true, // Enable Agent toggle on /write page
  enabledOnContent: true,    // Allow Agent on posts/pages via frontmatter
},

2. Right sidebar on posts/pages

Enable Agent in the right sidebar on individual posts or pages using the aiChat frontmatter field. Requires both rightSidebar: true and siteConfig.aiChat.enabledOnContent: true.

Frontmatter example:

---
title: "My Post"
rightSidebar: true
aiChat: true # Enable Agent in right sidebar
---

Environment variables:

Agent requires the following Convex environment variables:

• ANTHROPIC_API_KEY (required): Your Anthropic API key for Claude API access
• CLAUDE_PROMPT_STYLE (optional): First part of system prompt
• CLAUDE_PROMPT_COMMUNITY (optional): Second part of system prompt
• CLAUDE_PROMPT_RULES (optional): Third part of system prompt
• CLAUDE_SYSTEM_PROMPT (optional): Single system prompt (fallback if split prompts not set)

Setting environment variables:

1. Go to Convex Dashboard
2. Select your project
3. Navigate to Settings > Environment Variables
4. Add ANTHROPIC_API_KEY with your API key value
5. Optionally add system prompt variables (CLAUDE_PROMPT_STYLE, etc.)
6. Deploy changes

How it works:

• Agent uses anonymous session IDs stored in localStorage for chat history
• Each post/page has its own chat context (identified by slug)
• Chat history is stored per-session, per-context in Convex (aiChats table)
• Page content can be provided as context for AI responses
• Chat history limited to last 20 messages for efficiency
• If API key is not set, Agent displays "API key is not set" error message

Error handling:

If ANTHROPIC_API_KEY is not configured in Convex environment variables, Agent displays a user-friendly error message: "API key is not set". This helps identify when the API key is missing in production deployments.

Dashboard

The Dashboard at /dashboard provides a centralized UI for managing content, configuring the site, and performing sync operations. It's designed for developers who fork the repository to set up and manage their markdown blog.

Access: Navigate to /dashboard in your browser. The dashboard is not linked in the navigation by default.

Authentication: WorkOS authentication is optional. Configure it in siteConfig.ts:

dashboard: {
  enabled: true,
  requireAuth: false, // Set to true to require WorkOS authentication
},

When requireAuth is false, the dashboard is open access. When requireAuth is true and WorkOS is configured, users must log in to access the dashboard. See How to setup WorkOS for authentication setup.

Key Features:

• Content Management: Posts and Pages list views with filtering, search, pagination, and items per page selector
• Post/Page Editor: Markdown editor with live preview, draggable/resizable frontmatter sidebar, download markdown
• Write Post/Page: Full-screen writing interface with markdown editor and frontmatter reference
• AI Agent: Dedicated AI chat section separate from Write page
• Newsletter Management: All Newsletter Admin features integrated (subscribers, send newsletter, write email, recent sends, email stats)
• Content Import: Firecrawl import UI for importing external URLs as markdown drafts
• Site Configuration: Config Generator UI for all siteConfig.ts settings
• Index HTML Editor: View and edit index.html content
• Analytics: Real-time stats dashboard (always accessible in dashboard)
• Sync Commands: UI with buttons for all sync operations (sync, sync:discovery, sync:all for dev and prod)
• Sync Server: Execute sync commands directly from dashboard with real-time output
• Header Sync Buttons: Quick sync buttons in dashboard header for npm run sync:all (dev and prod)

Sync Commands Available:

• npm run sync - Sync markdown content (development)
• npm run sync:prod - Sync markdown content (production)
• npm run sync:discovery - Update discovery files (development)
• npm run sync:discovery:prod - Update discovery files (production)
• npm run sync:all - Sync content + discovery files (development)
• npm run sync:all:prod - Sync content + discovery files (production)
• npm run sync-server - Start local HTTP server for executing commands from dashboard

Sync Server:

The dashboard can execute sync commands directly without opening a terminal. Start the sync server:

npm run sync-server

This starts a local HTTP server on localhost:3001 that:

• Executes sync commands when requested from the dashboard
• Streams output in real-time to the dashboard terminal view
• Shows server status (online/offline) in the dashboard
• Supports optional token authentication via SYNC_TOKEN environment variable
• Only executes whitelisted commands for security

When the sync server is running, the dashboard shows "Execute" buttons that run commands directly. When offline, buttons show commands in a modal for copying to your terminal.

The dashboard provides a UI for these commands, but you can also run them directly from the terminal. See the Dashboard documentation for complete details.

Next Steps

After deploying:

1. Add your own blog posts
2. Customize the theme colors in global.css
3. Update the featured essays list
4. Submit your sitemap to Google Search Console
5. Share your first post

Your blog is now live with real-time updates, SEO optimization, and AI-friendly APIs. Every time you sync new posts, they appear immediately without redeploying.

MCP Server

Your site includes an HTTP-based Model Context Protocol (MCP) server for AI tool integration.

Endpoint: https://your-site.netlify.app/mcp

The MCP server runs 24/7 on Netlify Edge Functions and allows AI assistants like Cursor and Claude Desktop to access your blog content programmatically. No local machine required.

Features:

• Public access with rate limiting (50 req/min per IP)
• Optional API key for higher limits (1000 req/min)
• Seven tools: list_posts, get_post, list_pages, get_page, get_homepage, search_content, export_all

Configuration:

Add to your Cursor config (~/.cursor/mcp.json):

{
  "mcpServers": {
    "my-blog": {
      "url": "https://your-site.netlify.app/mcp"
    }
  }
}

For higher rate limits: Set MCP_API_KEY in your Netlify environment variables, then add the Authorization header to your client config.

See How to Use the MCP Server for full documentation.