Skip to content

Feedback: guides

Original URL: https://www.assemblyai.com/docs/guides
Category: other
Generated: 05/08/2025, 4:26:41 pm


Generated: 05/08/2025, 4:26:40 pm

Technical Documentation Analysis & Recommendations

Section titled “Technical Documentation Analysis & Recommendations”

This documentation serves as a guides/cookbooks index page, but suffers from several structural and usability issues that create friction for users trying to find relevant content.


Issues:

  • No clear explanation of what “Cookbooks” vs “API Guides” means
  • Missing difficulty levels, time estimates, or prerequisites
  • No indication of which programming languages are used
  • Broken image references (file:838a4072-bf1c-44d8-856e-915b7e51a95f)

Recommendations:

# Cookbooks & Guides
## What's the difference?
- **Cookbooks**: Complete, real-world implementations with SDKs and frameworks
- **API Guides**: Direct API usage examples without additional dependencies
Each guide includes:
- ⏱️ Estimated completion time
- 🔧 Required tools/languages
- 📚 Prerequisites
- 💰 API usage costs (where applicable)

Issues:

  • “All” section is overwhelming (60+ items in a flat list)
  • No search functionality
  • Inconsistent categorization
  • Duplicate entries between sections

Recommendations:

A. Add filtering capabilities:

## Find Your Guide
**Filter by:**
- Language: [ Python ] [ JavaScript ] [ cURL ] [ All ]
- Use Case: [ Transcription ] [ Analysis ] [ Real-time ] [ Integration ]
- Difficulty: [ Beginner ] [ Intermediate ] [ Advanced ]

B. Restructure the “All” section:

## All Guides
### 🎯 Popular Use Cases
- Video/Audio Processing (12 guides)
- Real-time Applications (8 guides)
- Data Analysis & Intelligence (15 guides)
### 🔧 Integration & Migration
- Cloud Platform Integrations (6 guides)
- Migration from Other Services (4 guides)
### 🛠️ Advanced Techniques
- Error Handling & Optimization (5 guides)
- Custom Implementations (8 guides)

Issues:

  • Many titles are too technical/verbose
  • No preview of what users will learn
  • Missing context about real-world applications

Recommendations:

Before:

"Use Automatic Language Detection as a Separate Step From Transcription"

After:

**Automatic Language Detection Workflow**
*Improve accuracy by detecting language first, then transcribing*
⏱️ 15 min | 🔧 Python | 📚 Basic API knowledge
Perfect for: Multi-language content, international applications

Issues:

  • No breadcrumbs or “back to guides” navigation
  • Missing “What’s next?” suggestions
  • No related content recommendations

Recommendations:

A. Add guide cards with better information architecture:

┌─────────────────────────────────────┐
│ 🎥 Generate Video Subtitles │
│ │
│ Create SRT files from any video │
│ ⏱️ 20 min | 🔧 Python | 💰 ~$0.10 │
│ │
│ You'll learn: │
│ • Extract audio from video │
│ • Generate timestamped text │
│ • Export multiple subtitle formats │
│ │
│ [ View Guide → ] │
└─────────────────────────────────────┘

Issues:

  • No onboarding path for new users
  • No progression from beginner to advanced
  • Missing prerequisites and dependencies

Recommendations:

A. Add a “Getting Started” section:

## 🚀 New to AssemblyAI?
### Start Here (5 min setup)
1. [Get your API key](link)
2. [Basic transcription example](link)
3. [Choose your first project](#recommended-first-projects)
### Recommended First Projects
- **For beginners**: Transcribe a YouTube video
- **For developers**: Build a transcription UI with Gradio
- **For businesses**: Analyze customer call sentiment

Issues:

  • Broken image references
  • Inconsistent link formatting
  • Missing error handling in the documentation structure

Recommendations:

A. Fix image references:

<!-- Replace file: references with proper URLs -->
<img src="/images/speech-to-text-icon.svg" alt="Speech to Text" />

B. Add error states:

<!-- If guide is unavailable -->
🚧 This guide is being updated. Check back soon or try [similar guide].

  1. Add filtering tags to each guide card
  2. Include time estimates for each guide
  3. Fix broken image references
  4. Add “Prerequisites” section to the page header
  5. Group migration guides into a dedicated section
  1. Create learning paths: “Beginner → Intermediate → Advanced”
  2. Add use-case landing pages: “Content Creation”, “Business Analytics”, “Developer Tools”
  3. Include cost estimates: Help users understand API usage costs upfront
  4. Add community examples: Link to user-submitted implementations

This restructure would transform the page from a simple directory into a guided learning experience that helps users find exactly what they need based on their skill level, use case, and available time.