Last updated: Jul 25, 2025, 10:08 AM UTC

Obsolete Email and Dashboard References Report

Generated: 2025-01-25 18:00 UTC
Status: Complete
Verified:

Executive Summary

This document identifies obsolete references to dashboards and email configurations throughout the documentation. Many references to "dashboard" features need to be updated to reflect the API-first approach, and email templates contain outdated URLs and features.

Key Findings

1. Dashboard References to Update

High Priority - User-Facing Documents

docs/pricing.md

  • Line 208: "Usage dashboard" listed as Pro feature
  • Should be: "Usage API access"

Email Templates (in code)

  • unified-api/lib/email-gmail-api.js:

docs/setup/webhook-api-key-implementation.md

Medium Priority - PRD Documents

docs/prd/prd-monitoring-analytics.md

  • Contains internal monitoring dashboard references (OK - these are for ops team)
  • Line 368-370: "Usage Dashboard" interface spec needs clarification it's via API

docs/prd/prd-commercial-features-pricing.md

  • Line 205: "Reseller dashboard" - future feature
  • Line 220: "Real-time usage dashboard" - should be "usage API"

docs/launch/launch-strategy-todo.md

  • Line 114: "Billing Dashboard" marked as
  • Line 417: "Set up authentication system and user dashboard"

2. Email System References to Update

Incorrect URLs in Email Templates

Welcome Email - Free Tier

  • Line 202: Points to old standalone function URL:
    curl -X POST https://convert-to-markdown.knowcode.tech/xlsx-converter
    
    Should be:
    curl -X POST https://api.convert-to-markdown.knowcode.tech/v1/convert/excel-to-json
    

Welcome Email - Pro Tier

  • Line 318: Same issue with standalone function URL
  • Line 324: Dashboard URL that doesn't exist
  • Line 364: Dashboard URL in plain text version

Obsolete Email Configuration

docs/setup/email-setup-comprehensive-guide.md

  • References dashboard features that don't exist
  • Line 271-272: Dashboard link CTAs

3. Correct References (No Change Needed)

These references are appropriate and should remain:

  1. Internal Monitoring Dashboards (Grafana, ops dashboards) - These are for internal team use
  2. Stripe Dashboard references - External service
  3. Future Dashboard mentions in roadmap documents
  4. Analytics Dashboard for internal metrics

Recommended Updates

Immediate Actions

  1. Update Email Templates

    // Replace in welcome emails:
    // OLD: "📊 Usage dashboard"
    // NEW: "📊 Usage API for tracking"
    
    // OLD: https://convert-to-markdown.knowcode.tech/xlsx-converter
    // NEW: https://api.convert-to-markdown.knowcode.tech/v1/convert/excel-to-json
    
    // Remove: Dashboard links
    // Add: Usage API documentation links
    
  2. Update pricing.md

    • Change "Usage dashboard" to "Usage API access"
    • Update feature comparison table
  3. Update webhook documentation

    • Remove dashboard access references
    • Focus on API-based usage tracking

Documentation Strategy

  1. Clear Distinction:

    • Internal dashboards = OK (Grafana, monitoring)
    • Customer dashboard = Not implemented (use API instead)
    • Stripe dashboard = External service (OK)
  2. Consistent Messaging:

    • "We provide an API-first approach"
    • "Track usage programmatically via our Usage API"
    • "Build your own dashboard with our data"
  3. Update Templates:

    • Create standard language for "no dashboard" explanation
    • Emphasize API flexibility over fixed UI

Files Requiring Updates

Critical (Customer-Facing)

  1. unified-api/lib/email-gmail-api.js - Email templates
  2. docs/pricing.md - Feature list
  3. docs/api.md - Ensure no dashboard references

Important (Documentation)

  1. docs/setup/webhook-api-key-implementation.md
  2. docs/prd/prd-commercial-features-pricing.md
  3. docs/launch/launch-strategy-todo.md

Low Priority (Internal/Future)

  1. PRD documents mentioning future dashboards
  2. Internal monitoring dashboard references
  3. Roadmap documents

Conclusion

The main issues are:

  1. Email templates pointing to non-existent dashboard URLs
  2. Marketing materials listing dashboard as a current feature
  3. Documentation mixing internal monitoring dashboards with customer-facing features

Priority should be given to updating customer-facing content (emails and pricing page) to accurately reflect the API-first approach and remove references to non-existent dashboard features.