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
:- Line 211: " Usage dashboard" in free tier email
- Line 308: " Usage dashboard to track your conversions" in pro tier email
- Line 324: Links to
/dashboard
URL - Line 364: "View Dashboard: https://convert-to-markdown.knowcode.tech/dashboard"
docs/setup/webhook-api-key-implementation.md
- Multiple references to dashboard access as a feature
- Line 282: " Usage dashboard access"
- Line 288: "View your dashboard: https://convert-to-markdown.knowcode.tech/dashboard"
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:
Should be:curl -X POST https://convert-to-markdown.knowcode.tech/xlsx-converter
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:
- Internal Monitoring Dashboards (Grafana, ops dashboards) - These are for internal team use
- Stripe Dashboard references - External service
- Future Dashboard mentions in roadmap documents
- Analytics Dashboard for internal metrics
Recommended Updates
Immediate Actions
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
Update pricing.md
- Change "Usage dashboard" to "Usage API access"
- Update feature comparison table
Update webhook documentation
- Remove dashboard access references
- Focus on API-based usage tracking
Documentation Strategy
Clear Distinction:
- Internal dashboards = OK (Grafana, monitoring)
- Customer dashboard = Not implemented (use API instead)
- Stripe dashboard = External service (OK)
Consistent Messaging:
- "We provide an API-first approach"
- "Track usage programmatically via our Usage API"
- "Build your own dashboard with our data"
Update Templates:
- Create standard language for "no dashboard" explanation
- Emphasize API flexibility over fixed UI
Files Requiring Updates
Critical (Customer-Facing)
unified-api/lib/email-gmail-api.js
- Email templatesdocs/pricing.md
- Feature listdocs/api.md
- Ensure no dashboard references
Important (Documentation)
docs/setup/webhook-api-key-implementation.md
docs/prd/prd-commercial-features-pricing.md
docs/launch/launch-strategy-todo.md
Low Priority (Internal/Future)
- PRD documents mentioning future dashboards
- Internal monitoring dashboard references
- Roadmap documents
Conclusion
The main issues are:
- Email templates pointing to non-existent dashboard URLs
- Marketing materials listing dashboard as a current feature
- 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.