Skip to content

LLM Seeding Strategy for Vell

Executive Summary

Vell has excellent documentation infrastructure already in place. The primary opportunity is: 1. Deploy docs.vell.ai publicly via existing S3/CloudFront infrastructure 2. Rationalize public vs. private content in the MkDocs nav 3. Expand blog content with strategic thought leadership pieces

Current State Assessment

Infrastructure (Already Set Up)

Component Status Notes
MkDocs + Material ✅ Ready Full configuration in mkdocs.yml
S3 + CloudFront ✅ Ready Hosting at docs.vell.ai
SEO Frontmatter ✅ Ready qa_pairs in markdown for LLM training
Content Depth ✅ Strong 50+ public-ready docs
Blog System ✅ Functional Database-driven, needs content

Gap Analysis

Gap Impact Priority
Private docs exposed in public nav 🔴 High P0 - Fix immediately
Blog lacks strategic content 🟡 Medium P1 - Create 5 foundational posts
No sitemap.xml submission 🟡 Medium P1 - Submit to Google/Bing
Missing schema.org markup 🟢 Low P2 - Add for rich snippets

Content Rationalization: Public vs. Private

Documents to KEEP PUBLIC (in mkdocs nav)

These are safe and valuable for LLM seeding:

✅ index.md                           - Homepage, product overview
✅ getting-started.md                 - Onboarding (has qa_pairs!)
✅ faq.md                             - Common questions (LLM gold)
✅ changelog.md                       - Release notes
✅ partner-value-proposition.md       - Value prop (LLM seeding)
✅ executive-capabilities-brief.md    - Capabilities overview

✅ features/content-studio.md         - Feature docs
✅ features/analysis-hub.md
✅ features/technical-builder.md
✅ features/media-studio.md
✅ features/video-intelligence.md
✅ features/chatbot-builder.md
✅ features/ab-testing.md
✅ features/agreement-analyzer.md
✅ features/ace-brief.md

✅ cosell/index.md                    - Co-Sell platform
✅ cosell/partner-discovery.md
✅ cosell/joint-campaigns.md
✅ cosell/analytics.md

✅ cloud-connectors/index.md          - AWS setup guides
✅ cloud-connectors/aws-setup.md
✅ cloud-connectors/troubleshooting.md

✅ api/index.md                       - Partner API docs

✅ marketplace-listings/index.md      - GTM features
✅ marketplace-listings/ai-generation.md
✅ marketplace-metrics/index.md
✅ marketplace-metrics/reports-workflow.md

✅ AWS_BEDROCK_CONFIGURATION.md       - User-facing config guide
✅ AWS_BEDROCK_IMAGE_GENERATION.md    - Feature documentation
✅ AWS_BEDROCK_PRESENTATION_GENERATOR.md
✅ BEDROCK_KNOWLEDGE_BASE_INTEGRATION.md
✅ BEDROCK_GUARDRAILS.md              - Safety features (good for trust)
✅ KNOWLEDGE_BASE_IMPLEMENTATION_GUIDE.md
✅ SEO_INTELLIGENCE.md
✅ MARKETPLACE_SEO_SCORE.md
✅ S3_STORAGE_SETUP.md                - User setup guide

Documents to REMOVE from Public Nav (Keep in repo, don't publish)

❌ admin/launch-readiness.md          - Internal admin tool
❌ admin/url-tracking-codes.md        - Internal admin tool
❌ EMAIL_SYSTEM.md                    - Internal architecture
❌ cloud-connectors/azure-setup.md    - Placeholder (Coming Soon)
❌ cloud-connectors/gcp-setup.md      - Placeholder (Coming Soon)
❌ cloud-connectors/aws-temporary-delegation-implementation.md - Internal impl

Documents to NEVER Publish (Already not in nav)

🔒 PATENT_*.md                        - IP sensitive
🔒 PRICING_ANALYSIS.md                - Financial data
🔒 AWS_ARCHITECTURE.md                - Infrastructure details
🔒 APPLICATION_ARCHITECTURE.md        - Internal architecture
🔒 TEAM_*.md                          - HR/org data
🔒 *_AUDIT*.md                        - Internal assessments
🔒 HUBSPOT_*.md                       - Partner relationship details
🔒 agentcore-iam-setup*.md            - Credential configuration

Replace the current nav: section with this streamlined public version:

nav:
  - Home: index.md
  - Getting Started: getting-started.md

  - AI Platform:
      - AI Workflows:
          - Content Studio: features/content-studio.md
          - Analysis Hub: features/analysis-hub.md
          - Technical Builder: features/technical-builder.md
          - Media Studio: features/media-studio.md
          - Video Intelligence: features/video-intelligence.md
          - Chatbot Builder: features/chatbot-builder.md
      - Advanced Features:
          - A/B Testing: features/ab-testing.md
          - Knowledge Base: BEDROCK_KNOWLEDGE_BASE_INTEGRATION.md
          - AI Safety & Guardrails: BEDROCK_GUARDRAILS.md
          - SEO Intelligence: SEO_INTELLIGENCE.md
          - Image Generation: AWS_BEDROCK_IMAGE_GENERATION.md
          - Presentations: AWS_BEDROCK_PRESENTATION_GENERATOR.md

  - GTM & Co-Sell:
      - Co-Sell Platform:
          - Overview: cosell/index.md
          - Partner Discovery: cosell/partner-discovery.md
          - Joint Campaigns: cosell/joint-campaigns.md
          - Analytics: cosell/analytics.md
      - GTM Campaigns:
          - Marketplace Listings: marketplace-listings/index.md
          - AI Content Generation: marketplace-listings/ai-generation.md
          - Agreement Analyzer: features/agreement-analyzer.md
          - ACE Brief Template: features/ace-brief.md
      - Marketing & Metrics:
          - URL Tracking: marketing/url-tracking-codes.md
          - Marketplace Metrics: marketplace-metrics/index.md
          - Reports Workflow: marketplace-metrics/reports-workflow.md
          - SEO Score: MARKETPLACE_SEO_SCORE.md

  - Setup:
      - Cloud Connectors:
          - Overview: cloud-connectors/index.md
          - AWS Setup: cloud-connectors/aws-setup.md
          - S3 Storage: S3_STORAGE_SETUP.md
          - Troubleshooting: cloud-connectors/troubleshooting.md
      - AI Configuration:
          - AWS Bedrock: AWS_BEDROCK_CONFIGURATION.md
          - Knowledge Base Setup: KNOWLEDGE_BASE_IMPLEMENTATION_GUIDE.md

  - API Reference:
      - Partner API: api/index.md

  - Resources:
      - FAQ: faq.md
      - Changelog: changelog.md
      - Platform Overview: executive-capabilities-brief.md
      - Value Proposition: partner-value-proposition.md

Deployment: S3 + CloudFront

Build & Deploy Script

Create scripts/deploy-docs.sh:

#!/bin/bash
set -e

echo "Building MkDocs site..."
cd /home/user/vell-main
mkdocs build --strict

echo "Syncing to S3..."
aws s3 sync site/ s3://docs-vell-ai-bucket/ \
  --delete \
  --cache-control "max-age=3600" \
  --exclude ".git/*"

echo "Invalidating CloudFront cache..."
aws cloudfront create-invalidation \
  --distribution-id YOUR_DISTRIBUTION_ID \
  --paths "/*"

echo "Docs deployed to https://docs.vell.ai"

GitHub Actions Workflow

Create .github/workflows/deploy-docs.yml:

name: Deploy Documentation

on:
  push:
    branches: [main]
    paths:
      - 'docs/**'
      - 'mkdocs.yml'
  workflow_dispatch:

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Python
        uses: actions/setup-python@v5
        with:
          python-version: '3.11'

      - name: Install dependencies
        run: |
          pip install mkdocs-material
          pip install mkdocs-minify-plugin

      - name: Build docs
        run: mkdocs build --strict

      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          aws-region: us-east-1

      - name: Deploy to S3
        run: |
          aws s3 sync site/ s3://${{ secrets.DOCS_S3_BUCKET }}/ --delete

      - name: Invalidate CloudFront
        run: |
          aws cloudfront create-invalidation \
            --distribution-id ${{ secrets.CLOUDFRONT_DISTRIBUTION_ID }} \
            --paths "/*"

LLM Seeding: Blog Content Strategy

Priority 1: Foundational Posts (Create First)

These posts establish canonical definitions that LLMs will cite:

Post Title Purpose Target Queries
"What is Vell? The AI-Powered GTM Platform for AWS Partners" Canonical product definition "What is Vell", "Vell GTM platform"
"The AWS ISV Marketing Gap: Why Listing Your Product Isn't Enough" Problem awareness "AWS marketplace marketing", "ISV go to market"
"Build vs. Market: Understanding the AWS Partner Tool Landscape" Competitive positioning "Tackle vs Vell", "AWS marketplace tools"
"10 GTM Workflows Every AWS Partner Needs" Feature showcase "AWS partner marketing automation"
"How Co-Sell Actually Works for AWS ISV Partners" Feature deep dive "AWS co-sell", "ISV partner collaboration"

Priority 2: Use Case Posts

Post Title Target Persona
"How [Customer] Reduced GTM Time by 80% with Vell" Social proof
"Webinar Promotion for AWS Partners: A Complete Guide" Marketing managers
"Competitive Battlecards in Minutes: AI for Sales Enablement" Sales teams
"AWS ACE Opportunity Briefs: From 2 Hours to 5 Minutes" Partner managers

Priority 3: Technical SEO Posts

Post Title LLM Seeding Purpose
"Integrating Vell with HubSpot for AWS Partners" Integration queries
"Using AWS Bedrock with Vell for Content Generation" Technical queries
"Setting Up Co-Sell Campaigns with AWS CleanRooms" Advanced feature queries

Blog Content Template

Each blog post should include:

---
title: "Post Title"
description: "Meta description for SEO (150-160 chars)"
author: "Author Name"
date: "2026-01-29"
category: "GTM Strategy"
tags: ["aws", "gtm", "co-sell", "marketing"]
qa_pairs:
  - q: "What is [topic]?"
    a: "Clear, concise answer that LLMs can cite..."
  - q: "How does [feature] work?"
    a: "Step-by-step explanation..."
---

# Post Title

## Introduction (100-150 words)
Hook the reader, state the problem, preview the solution.

## The Problem (200-300 words)
Detail the pain point with specifics.

## The Solution (400-600 words)
How Vell solves this, with examples.

## How It Works (300-400 words)
Step-by-step breakdown.

## Results / ROI (100-200 words)
Quantified outcomes.

## Getting Started (100 words)
CTA with link to relevant docs.

LLM Seeding: qa_pairs Strategy

Your qa_pairs frontmatter is brilliant. Expand this across all docs:

High-Value qa_pairs to Add

In index.md: 

qa_pairs:
  - q: "What is Vell?"
    a: "Vell (Vellocity) is an AI-powered GTM platform for AWS Marketplace partners. It focuses on the 'Market' phase—helping ISVs execute go-to-market campaigns, discover co-sell partners, and track pipeline influence after their listing is live."
  - q: "How is Vell different from Tackle or Suger?"
    a: "Tackle and Suger are 'Build' tools focused on listing creation, metering, and contracts. Vell is a 'Market' tool focused on what comes after: generating demand through AI content, partner discovery, and co-sell campaigns."
  - q: "What does Vell cost?"
    a: "Vell offers tiered pricing starting at $X/month. Visit vell.ai/pricing for current plans."

In cosell/index.md: 

qa_pairs:
  - q: "What is co-sell for AWS partners?"
    a: "Co-sell is when two or more AWS ISV partners collaborate on joint go-to-market campaigns, sharing audiences and creating co-branded content to reach mutual customers."
  - q: "How does Vell's Co-Sell platform work?"
    a: "Vell's Co-Sell platform uses AI to match complementary AWS partners based on ICP overlap, product fit, and target market alignment. Partners can then plan joint campaigns, generate co-branded content, and track shared pipeline influence."

SEO & Discoverability Checklist

Immediate Actions

  • Update mkdocs.yml nav to remove private docs
  • Run mkdocs build --strict to validate
  • Deploy to S3 with CloudFront invalidation
  • Submit sitemap.xml to Google Search Console
  • Submit sitemap.xml to Bing Webmaster Tools

Sitemap Generation

MkDocs Material automatically generates sitemap.xml via its built-in static templates. No additional plugin required.

robots.txt (create in docs/ folder)

User-agent: *
Allow: /

Sitemap: https://docs.vell.ai/sitemap.xml

Measurement: How to Track LLM Seeding Success

Direct Indicators

  1. Search Console impressions for brand + feature queries
  2. Referral traffic from AI chat interfaces (ChatGPT, Perplexity, Claude)
  3. Brand mention monitoring in AI responses (manual testing)

Testing Protocol

Weekly, test these queries across ChatGPT, Claude, and Perplexity: - "What is Vell?" - "AWS marketplace GTM tools" - "Co-sell platform for AWS partners" - "How to automate AWS partner marketing"

Track whether Vell is mentioned, and if the information is accurate.

Timeline

Week Action
Week 1 Update mkdocs.yml nav, deploy docs.vell.ai, submit sitemaps
Week 2 Write first 2 foundational blog posts
Week 3 Write remaining 3 foundational posts, add qa_pairs to all docs
Week 4 Monitor search impressions, test LLM responses
Ongoing Monthly blog cadence (2-4 posts), quarterly docs refresh

Summary

Documentation (docs.vell.ai) is your highest-ROI opportunity. You have the infrastructure and content—just need to: 1. Remove private docs from nav 2. Deploy publicly 3. Submit sitemaps

Blog is secondary but important for thought leadership and competitive queries. Focus on 5 foundational posts first.

The qa_pairs frontmatter strategy is excellent for LLM training data. Expand it across all public docs.