Format extend-document-automation talk to match project documentation standards

Author: jxnl

.cursor/rules/documentation-style.mdc

@@ -0,0 +1,35 @@
+# Documentation Writing Style Guide
+
+When writing or editing documentation in the `docs/` directory, follow these style guidelines:
+
+## Writing Standards
+- **Reading level**: Write at 9th-grade reading level for accessibility
+- **No emojis**: Keep documentation professional and emoji-free
+- **Conversational tone**: Use "you", "we", "I" to make content personal and engaging
+- **Active voice**: Prefer active over passive voice
+- **Specific examples**: Include concrete examples and metrics when possible
+
+## Technical Content
+- **Actionable insights**: Focus on practical, implementable advice over theory
+- **Code examples**: Include working code snippets with proper syntax highlighting
+- **Performance metrics**: Include specific numbers and improvements when available
+- **Company attribution**: Reference companies and speakers for credibility
+
+## Markdown Formatting
+- **Headers**: Use proper hierarchy (H1 for titles, H2 for main sections, H3 for subsections)
+- **Bold text**: Use `**bold**` for emphasis and labels
+- **Code blocks**: Use triple backticks with language specification
+- **Lists**: Use `-` for bullet points with consistent formatting
+- **Links**: Use descriptive link text, not "click here"
+
+## Content Organization
+- **Clear structure**: Organize content with logical flow and clear headings
+- **Key takeaways**: Highlight main insights with `**Key Takeaway:**` format
+- **Scannable content**: Use bullet points, short paragraphs, and clear headings
+- **Consistent formatting**: Match existing document styles in the same directory
+
+## Technical Accuracy
+- **Verify examples**: Ensure all code examples work and are up-to-date
+- **Check links**: Verify all internal and external links are functional
+- **Consistent terminology**: Use the same terms throughout related documents
+- **Proper citations**: Reference sources and speakers appropriately

.cursor/rules/mkdocs-navigation.mdc

@@ -0,0 +1,39 @@
+# MkDocs Navigation Standards
+
+When updating the navigation in [mkdocs.yml](mdc:mkdocs.yml), follow these standards:
+
+## Talk Navigation Format
+For talks in the navigation, use the format: `"Topic - Speaker Name (Company)": talks/filename.md`
+
+### Examples:
+```yaml
+- "Coding Agents - Nik Pash (Cline)": talks/rag-is-dead-cline-nik.md
+- "RAG Anti-patterns - Skylar Payne": talks/rag-antipatterns-skylar-payne.md
+- "Semantic Search - Will Bryk (Exa)": talks/semantic-search-exa-will-bryk.md
+```
+
+## Navigation Organization
+Organize talks into logical chapters and subsections:
+
+### Chapter 5 Structure:
+```yaml
+- "Chapter 5: User Experience":
+  - "Coding Agents":
+    - "Coding Agents - Nik Pash (Cline)": talks/rag-is-dead-cline-nik.md
+    - "SWE-Bench Agent - Colin Flaherty (Augment)": talks/colin-rag-agents.md
+  - "Document Processing":
+    - "Document Parsing - Adit (Reducto)": talks/reducto-docs-adit.md
+    - "Browser RAG - Michael (OpenBB)": talks/rag-without-apis-browser-michael-struwig.md
+  - "Search Technologies":
+    - "Semantic Search - Will Bryk (Exa)": talks/semantic-search-exa-will-bryk.md
+    - "RAG Anti-patterns - Skylar Payne": talks/rag-antipatterns-skylar-payne.md
+```
+
+## Guidelines
+- Keep navigation titles shorter than full article titles for better UX
+- Include company names in parentheses when available
+- Group related talks into logical subsections
+- Maintain consistent formatting across all talk entries
+- Use descriptive topic names that indicate the main focus
+
+Reference [AGENTS.md](mdc:docs/talks/AGENTS.md) for complete talk organization guidelines.

.cursor/rules/project-structure.mdc

@@ -0,0 +1,31 @@
+# Systematically Improving RAG Project Structure
+
+This is a documentation and workshop project for RAG (Retrieval-Augmented Generation) applications.
+
+## Key Directories
+- **`docs/`** - Main documentation using MkDocs
+  - **`docs/talks/`** - Industry expert talks and presentations
+  - **`docs/workshops/`** - Workshop chapters and exercises
+  - **`docs/office-hours/`** - Office hours summaries and FAQs
+- **`latest/`** - Current cohort materials and case studies
+- **`cohort_1/`** & **`cohort_2/`** - Previous cohort materials
+- **`data/`** - Sample datasets and examples
+
+## Important Files
+- **[mkdocs.yml](mdc:mkdocs.yml)** - Site navigation and configuration
+- **[docs/talks/AGENTS.md](mdc:docs/talks/AGENTS.md)** - Talk formatting guidelines
+- **[docs/talks/index.md](mdc:docs/talks/index.md)** - Talk directory index
+- **[pyproject.toml](mdc:pyproject.toml)** - Python dependencies using `uv`
+
+## User Preferences
+- Always use `uv` instead of `pip` for Python package management
+- Write at 9th-grade reading level
+- Use async over synchronous Python code when possible
+- Match existing document styles when writing
+- No emojis in documentation
+
+## Build System
+- Uses MkDocs for documentation site generation
+- Deployed to GitHub Pages
+- Run `mkdocs serve` for local development
+- Run `mkdocs build` for production builds

.cursor/rules/talks-formatting.mdc

@@ -0,0 +1,47 @@
+# Talks Formatting Standards
+
+When working with files in the `docs/talks/` directory, follow these formatting standards:
+
+## Title Format
+All talk titles must follow a **catchy, conversational format** with these principles:
+- Use conversational tone with "I", "You", "Why", "How" to make it personal
+- Include specific benefits, numbers, or percentages when possible
+- Reference the company/organization for credibility
+- Use controversial hooks that challenge conventional wisdom
+- Suggest actionable implications for readers
+
+### Title Pattern Examples:
+- "Why I Stopped Using RAG for Coding Agents (And You Should Too)"
+- "The RAG Mistakes That Are Killing Your AI (Lessons from Google & LinkedIn)"
+- "Stop Trusting MTEB Rankings - Here's How Chroma Actually Tests Embeddings"
+- "The 12% RAG Performance Boost You're Missing (LanceDB's Re-ranking Secrets)"
+
+## YAML Frontmatter Requirements
+```yaml
+---
+title: [Catchy conversational title]
+speaker: [Name, Company]
+cohort: [Number]
+description: [Brief description of key insights]
+tags: [relevant, tags, including, company, technology]
+date: [YYYY-MM-DD]
+---
+```
+
+## Content Structure
+- **H1 title**: Must match YAML frontmatter title exactly
+- **Main sections**: Use `##` for primary sections
+- **Subsections**: Use `###` for subsections
+- **Key takeaways**: Use `**Key Takeaway:**` format for main insights
+- **Quotes**: Use `>` blockquotes for speaker quotes
+- **Lists**: Use `-` with **bold** labels for bullet points
+- **Company attribution**: Always include company names in titles and content
+
+## Writing Style
+- 9th-grade reading level for accessibility
+- Technical depth with practical examples
+- Actionable insights over theoretical concepts
+- Conversational tone that matches catchy titles
+- Specific metrics and performance improvements noted
+
+Reference [AGENTS.md](mdc:docs/talks/AGENTS.md) for complete formatting guidelines.

docs/talks/AGENTS.md

@@ -4,35 +4,68 @@
 This directory contains industry talks and presentations from the Systematically Improving RAG Applications series. Each talk provides insights from experts at companies like ChromaDB, Zapier, Glean, Exa, and others, covering practical RAG implementation strategies and lessons learned.
 
 ## File Structure
-- **Industry expert talks**: 15 markdown files covering specific RAG topics
+- **Industry expert talks**: 15+ markdown files covering specific RAG topics
 - **Organized by chapter**: Talks align with workshop chapters (evaluation, training, UX, etc.)
-- **Consistent format**: YAML frontmatter with title, description, tags, speakers, and date
+- **Consistent format**: YAML frontmatter with catchy titles, descriptions, tags, speakers, and dates
 - **Study notes format**: Key takeaways and technical insights highlighted
 
+## Title Format Standards
+All talk titles follow a **catchy, conversational format** designed to grab attention and communicate value:
+
+### Title Pattern Examples:
+- **"Why I Stopped Using RAG for Coding Agents (And You Should Too)"** - Personal story + actionable advice
+- **"The RAG Mistakes That Are Killing Your AI (Lessons from Google & LinkedIn)"** - Problem identification + company credibility
+- **"Stop Trusting MTEB Rankings - Here's How Chroma Actually Tests Embeddings"** - Contrarian take + insider knowledge
+- **"The 12% RAG Performance Boost You're Missing (LanceDB's Re-ranking Secrets)"** - Specific benefit + insider secrets
+
+### Title Principles:
+- **Conversational tone**: Use "I", "You", "Why", "How" to make it personal
+- **Specific benefits**: Include numbers, percentages, or concrete outcomes when possible
+- **Company attribution**: Reference the company/organization for credibility
+- **Controversial hooks**: Challenge conventional wisdom or common practices
+- **Actionable implications**: Suggest there's something readers should do differently
+
 ## Content Standards
-- **YAML frontmatter**: title, description, tags, speakers, date
-- **Study notes structure**: Technical insights with `***Key Takeaway:***` summaries
+- **YAML frontmatter**: catchy title, speaker with company, description, tags, date
+- **H1 title**: Matches the YAML title exactly for consistency
+- **Study notes structure**: Technical insights with `**Key Takeaway:**` summaries
 - **Question-answer format**: Practical insights organized by topic
 - **Code examples**: Where applicable, include implementation details
 - **Performance metrics**: Specific numbers and improvements mentioned
 
 ## Key Topics Covered
-- **Text chunking strategies** (ChromaDB - Anton)
-- **Feedback systems** (Zapier - Vitor)
-- **Embedding performance** (Kelly Hong)
-- **Enterprise search** (Glean - Manav)
-- **Query routing** (Anton)
-- **RAG anti-patterns** (Skylar Payne)
-- **Semantic search** (Exa - Will Bryk)
-- **Online evaluations** (Ben & Sidhant)
-- **Browser-based RAG** (Michael Struwig)
+- **"Why I Stopped Using RAG for Coding Agents (And You Should Too)"** - Nik Pash (Cline)
+- **"The RAG Mistakes That Are Killing Your AI (Lessons from Google & LinkedIn)"** - Skylar Payne
+- **"Stop Trusting MTEB Rankings - Here's How Chroma Actually Tests Embeddings"** - Kelly Hong (Chroma)
+- **"Why Glean Builds Custom Embedding Models for Every Customer"** - Manav (Glean)
+- **"Why Google Search Sucks for AI (And How Exa Is Building Something Better)"** - Will Bryk (Exa)
+- **"Why Your AI Is Failing in Production (Lessons from Raindrop & Oleve)"** - Ben & Sidhant
+- **"How OpenBB Ditched APIs and Put RAG in the Browser Instead"** - Michael (OpenBB)
+- **"Why Grep Beat Embeddings in Our SWE-Bench Agent (Lessons from Augment)"** - Colin Flaherty
+- **"Why Most Document Parsing Sucks (And How Reducto Fixed It)"** - Adit (Reducto)
+- **"The 12% RAG Performance Boost You're Missing (LanceDB's Re-ranking Secrets)"** - Ayush (LanceDB)
 
 ## Writing Style
 - **9th-grade reading level** for accessibility
 - **Technical depth** with practical examples
 - **Actionable insights** over theoretical concepts
 - **Surprising discoveries** and counter-intuitive findings highlighted
 - **Specific metrics** and performance improvements noted
+- **Conversational tone** that matches the catchy titles
+
+## Formatting Standards
+- **Consistent H1 titles**: Match YAML frontmatter exactly
+- **Proper markdown structure**: Use ## for main sections, ### for subsections
+- **Bold key takeaways**: `**Key Takeaway:**` format for main insights
+- **Blockquotes for quotes**: Use `>` for speaker quotes
+- **Bullet points**: Use `-` for lists with **bold** labels
+- **Company attribution**: Always include company names in titles and content
 
 ## Tags and Organization
-Common tags include: text chunking, evaluation, feedback systems, embedding models, query routing, performance optimization, user experience, production monitoring
+Common tags include: RAG, coding agents, embeddings, evaluation, feedback systems, enterprise search, query routing, performance optimization, user experience, production monitoring, document parsing, fine-tuning, re-ranking
+
+---
+
+IF you want to get discounts and 6 day email source on the topic make sure to subscribe to
+
+<script async data-uid="010fd9b52b" src="https://fivesixseven.kit.com/010fd9b52b/index.js"></script>