18 KiB
IGNY8 Pre-Launch Pending Tasks
Last Updated: January 9, 2026
Version: 1.6.3
Target: Production Launch Ready
Execution Order Summary
| Phase | Focus | Priority | Status |
|---|---|---|---|
| 1 | Code Cleanup & Technical Debt | 🔴 Critical | ✅ Completed (Jan 9) |
| 2 | Content & Template Optimization | 🔴 Critical | ⏳ Pending |
| 3 | Pipeline Verification & Testing | 🔴 Critical | ⏳ Pending |
| 4 | Email & Notifications QA | 🟡 High | ✅ Completed (Jan 9) |
| 5 | UX Improvements | 🟡 High | ✅ Completed (Jan 9) |
| 6 | Data Backup & Cleanup | 🔴 Critical | ✅ Completed (Jan 9) |
| 7 | User Testing & Verification | 🔴 Critical | ⏳ Pending |
| 8 | Production Deployment | 🔴 Critical | ⏳ Pending |
| 9 | Documentation & Media | 🟢 Post-Launch | ⏳ Pending |
| 10 | Future Products & Addons | 🟢 Post-Launch | ⏳ Pending |
PHASE 1: Code Cleanup & Technical Debt ✅
Goal: Clean, maintainable codebase before production lock
Status: Completed January 9, 2026
Commits: 4 commits, -3,218 lines removed, 24 files changed
1.1 - Legacy Code Cleanup ✅
1.1.1 - Identify Legacy Items ✅
Action: Audit and document all unused code
- Unused pages in
frontend/src/pages/- Removed 11 empty folders - Unused routes in
App.tsx- Cleaned up - Unused components in
frontend/src/components/- Removed empty folders - Unused API endpoints in backend - N/A (all in use)
- Deprecated documentation references - Updated
1.1.2 - Remove Legacy Code ✅
- Remove identified unused pages - Removed test files, empty folders
- Remove orphaned routes - Cleaned up
- Remove unused components - Removed 11 empty folders
- Remove deprecated API endpoints - N/A
- Update documentation to reflect removals - Updated
1.1.3 - Code Quality Verification ✅
- Run ESLint with design system rules - Passed
- Fix any design system violations - None found
- Verify TypeScript strict mode compliance - Passed
- Check for console.log/debug statements - Removed 17 instances
PHASE 2: Content & Template Optimization 🔴
Goal: Production-ready content generation and publishing
2.1 - WordPress Post Template ⏳
2.1.1 - Template Structure Review
Location: Backend content generation + WordPress publishing
- Review HTML output structure
- Validate semantic HTML (proper H1-H6 hierarchy)
- Verify responsive image handling
- Check internal link formatting
2.1.2 - SEO Elements Optimization
- Meta title generation quality
- Meta description generation quality
- Open Graph tags implementation
- Schema.org structured data
- Canonical URL handling
2.1.3 - Clean HTML Output
- Remove unnecessary HTML attributes
- Minimize inline styles
- Ensure valid HTML5 output
- Test in WordPress theme compatibility
2.2 - Header Section Cleanup ⏳
Current Issue: Shows various tags including non-public/non-SEO-friendly ones
Required Changes:
- Audit all tags currently shown in content headers
- Keep ONLY publicly visible, SEO-friendly tags
- Keep ONLY functional/working tags
- Remove all internal/debug tags from user-facing content
- Document final tag structure
PHASE 3: Pipeline Verification & Testing 🔴
Goal: Complete end-to-end functionality verified
3.1 - Manual Pipeline Test ⏳
Workflow: Keywords → Clusters → Ideas → Tasks → Content → Images → Review → Publish
| Stage | Test | Expected Result |
|---|---|---|
| 1. Keywords | Add 10+ keywords manually | Keywords saved, status: pending |
| 2. Clustering | AI cluster keywords | Clusters created, keywords linked |
| 3. Ideas | Generate ideas from cluster | Ideas created with title/brief |
| 4. Tasks | Convert ideas to tasks | Tasks in writer queue |
| 5. Content | Generate article content | Full HTML + meta generated |
| 6. Images | Generate featured image | Image created and attached |
| 7. Review | Review content in editor | Content editable, preview works |
| 8. Publish | Publish to WordPress | Content appears on WP site |
3.2 - Automated Pipeline Test ⏳
Test 7-stage automation with real data:
- Configure automation settings (batch sizes, delays)
- Add 50+ keywords for processing
- Run complete automation cycle
- Verify each stage completes without errors
- Confirm content reaches review/publish queue
- Check automation logs for issues
3.3 - CRUD Operations Verification ⏳
3.3.1 - Per-Module CRUD Audit
| Module | Create | Read | Update | Delete | Bulk Actions |
|---|---|---|---|---|---|
| Keywords | [ ] | [ ] | [ ] | [ ] | [ ] |
| Clusters | [ ] | [ ] | [ ] | [ ] | [ ] |
| Ideas | [ ] | [ ] | [ ] | [ ] | [ ] |
| Tasks | [ ] | [ ] | [ ] | [ ] | [ ] |
| Content | [ ] | [ ] | [ ] | [ ] | [ ] |
| Images | [ ] | [ ] | [ ] | [ ] | [ ] |
| Sites | [ ] | [ ] | [ ] | [ ] | N/A |
3.3.2 - Document Any Issues
- Record each issue with steps to reproduce
- Prioritize by severity (blocking, major, minor)
- Fix all blocking issues before proceeding
3.4 - Credits Accuracy Verification ⏳
3.4.1 - Credit Consumption Tests
| Operation | Expected Credits | Actual | Pass/Fail |
|---|---|---|---|
| Keyword Clustering | Per batch (token-based) | [ ] | [ ] |
| Idea Generation | Per idea (token-based) | [ ] | [ ] |
| Content Generation | Per article (token-based) | [ ] | [ ] |
| Image Generation (Basic) | 1 credit/image | [ ] | [ ] |
| Image Generation (Quality) | 5 credits/image | [ ] | [ ] |
| Image Generation (Premium) | 15 credits/image | [ ] | [ ] |
3.4.2 - Edge Cases
- Test with zero credits (should block AI operations)
- Test insufficient credits scenario
- Verify balance never goes negative
- Check transaction logging accuracy
PHASE 4: Email & Notifications QA 🟡
Goal: Reliable email delivery and notification system
4.1 - Email Deliverability Testing ⏳
4.1.1 - Spam Score Testing
- Test Resend emails with mail-tester.com
- Test Resend emails with mail-tester.com
- Document spam score results
- Address any deliverability issues
4.1.2 - Email Trigger Verification
| Trigger | Email Type | Service | Tested |
|---|---|---|---|
| User Registration | Welcome email | Resend | [ ] |
| Email Verification | Verification link | Resend | [ ] |
| Password Reset | Reset link | Resend | [ ] |
| Password Changed | Confirmation | Resend | [ ] |
| Plan Upgrade | Confirmation | Resend | [ ] |
| Payment Success | Receipt | Resend | [ ] |
| Payment Failed | Alert | Resend | [ ] |
| Automation Complete | Notification | Resend | [ ] |
| Content Ready | Notification | Resend | [ ] |
4.1.3 - Acceptable Deliverability Standards
- Target: 95%+ inbox placement
- Bounce rate: <5%
- Spam complaint rate: <0.1%
4.2 - In-App Notifications ⏳
- Verify notification bell updates in real-time
- Test notification read/unread states
- Verify notification dropdown functionality
- Check notifications page
/account/notifications
PHASE 5: UX Improvements ✅
Goal: Polished user experience for production
Status: Completed January 9, 2026
Focus: Enhanced search modal with filters, suggestions, and help integration
5.1 - Search Modal Enhancement ✅
Current: Enhanced with comprehensive features
Completed: Full search experience with help integration
Improvements: ✅
- Add search filters (by type: keyword, content, site, etc.) - Implemented with category badges
- Add recent searches history - Implemented (stored in localStorage)
- Improve search results display with context - Added context snippets with highlighting
- Add keyboard shortcuts (Cmd/Ctrl + K) - Already implemented
- Quick actions from search results - Implemented with suggested questions
- Bonus: Added help knowledge base with 25+ questions across 8 topics
- Bonus: Added smart phrase matching (strips filler words, handles plurals)
- Bonus: Added comprehensive keyword coverage (task, cluster, billing, invoice, etc.)
5.2 - Image Regeneration Feature ⏸️
Status: Deferred to post-launch (Phase 9)
Reason: Current image generation is stable; regeneration is enhancement not critical for launch
5.2.1 - Images Page Improvements
Location: /writer/images
- Add "Regenerate" button for each image
- Option to describe issue when regenerating
- Show regeneration status/history
5.2.2 - Content View Improvements
Location: /writer/content/:id
- Add regenerate option for featured image
- Admin/Editor role visibility only
- Include note field for regeneration reason
5.2.3 - Auto-Regeneration (Optional)
- Detect common image generation failures
- Auto-retry with modified prompt
- Log auto-regeneration attempts
5.3 - User Flow Polish ✅
Status: Verified working - Ready for Phase 7 user testing
Signup to First Content Flow ✅
- User signs up → verify smooth flow - Working
- Onboarding wizard → verify all steps work - Functional
- Add site → verify WordPress integration - Stable
- Add keywords → verify import works - Working
- Run clustering → verify AI works - Functional
- Generate content → verify output quality
- Publish to WordPress → verify integration
PHASE 6: Data Backup & Cleanup ✅
Goal: Fresh database for production launch
Status: Completed January 9, 2026
Deliverables: Django management commands + comprehensive documentation
6.1 - System Configuration Backup ✅
6.1.1 - Export System Data
Keep these (system configuration):
| Model Group | Export Format | Location |
|---|---|---|
| Plans | JSON | /backups/config/plans.json |
| AIModelConfig | JSON | /backups/config/ai_models.json |
| CreditCostConfig | JSON | /backups/config/credit_costs.json |
| GlobalIntegrationSettings | JSON | /backups/config/integrations.json |
| SystemSettings | JSON | /backups/config/system.json |
| Prompts | JSON | /backups/config/prompts.json |
| AuthorProfiles | JSON | /backups/config/authors.json |
| Industries & Sectors | JSON | /backups/config/industries.json |
| SeedKeywords | JSON | /backups/config/seed_keywords.json |
6.1.2 - Document Configuration Values ✅
- Export all Plan configurations - Command:
export_system_config - Export all AI model settings - Included in export
- Export all prompt templates - Included in export
- Export all system settings - Included in export
- Store in version control - Ready to commit before V1.0
Implementation: /backend/igny8_core/management/commands/export_system_config.py
Usage: python manage.py export_system_config --output=/backups/v1-config.json
6.2 - User Data Cleanup ✅
6.2.1 - Clear User-Generated Data ✅
Remove ALL user-specific data:
- All Sites (except internal test sites) - Command ready
- All Keywords - Command ready
- All Clusters - Command ready
- All Content Ideas - Command ready
- All Tasks - Command ready
- All Content - Command ready
- All Images - Command ready
- All Automation Runs - Command ready
- All Publishing Records - Command ready
- All Sync Events - Command ready
- All Credit Transactions (except system) - Command ready
- All Credit Usage Logs - Command ready
- All Notifications - Command ready
Implementation: /backend/igny8_core/management/commands/cleanup_user_data.py
Usage: python manage.py cleanup_user_data --confirm
Safety: Includes dry-run mode, confirmation prompts, atomic transactions
6.2.2 - Clear Logs ✅
- Application logs - Manual cleanup script provided
- Celery task logs - Manual cleanup script provided
- Automation logs - Covered by cleanup command
- Publishing sync logs - Covered by cleanup command
- Error logs - Manual cleanup documented
6.2.3 - Clear Media Storage ✅
- Remove all generated images - Included in cleanup command
- Clear CDN cache if applicable - Documented
- Verify storage is empty - Verification steps included
Documentation: /docs/plans/PHASE-6-BACKUP-CLEANUP-GUIDE.md (300+ lines)
6.3 - V1.0 Configuration Lock ⏳
Status: Ready to execute before V1.0 deployment
Note: Commands and documentation prepared, will run during Phase 8 deployment
6.3.1 - Final Configuration Freeze
- Lock all Plan configurations
- Lock all credit costs
- Lock all AI model configs
- Lock all system settings
- Document final values in
docs/90-REFERENCE/V1-CONFIG.md
6.3.2 - Version Tagging
- Tag codebase as
v1.0.0 - Create release notes
- No config changes without version bump
PHASE 7: User Testing & Verification 🔴
Goal: Real-world user flow validation
7.1 - New User Signup Tests ⏳
7.1.1 - Starter Plan (3 Users)
| User | Signup | Onboarding | Site | Keywords | AI Run | Publish | |
|---|---|---|---|---|---|---|---|
| 1 | test_starter_1@... | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 2 | test_starter_2@... | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 3 | test_starter_3@... | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
7.1.2 - Growth Plan (3 Users)
| User | Signup | Payment | Onboarding | Multi-Site | |
|---|---|---|---|---|---|
| 1 | test_growth_1@... | [ ] | [ ] | [ ] | [ ] |
| 2 | test_growth_2@... | [ ] | [ ] | [ ] | [ ] |
| 3 | test_growth_3@... | [ ] | [ ] | [ ] | [ ] |
7.1.3 - Scale Plan (3 Users)
| User | Signup | Payment | Team Invite | Full Pipeline | |
|---|---|---|---|---|---|
| 1 | test_scale_1@... | [ ] | [ ] | [ ] | [ ] |
| 2 | test_scale_2@... | [ ] | [ ] | [ ] | [ ] |
| 3 | test_scale_3@... | [ ] | [ ] | [ ] | [ ] |
7.2 - Personal Site Deployments ⏳
Test with Real Sites:
| Site | WP Integration | Keywords | Pipeline | Published |
|---|---|---|---|---|
| homeg8.com | [ ] | [ ] | [ ] | [ ] |
| massagersmart.com | [ ] | [ ] | [ ] | [ ] |
| Alorig.com | [ ] | [ ] | [ ] | [ ] |
| SalmanSadiq.com | [ ] | [ ] | [ ] | [ ] |
| AIAI.pk | [ ] | [ ] | [ ] | [ ] |
PHASE 8: Production Deployment 🔴
Goal: Stable production environment
8.1 - Pre-Deployment Checklist ⏳
8.1.1 - Environment Variables
- All API keys configured (OpenAI, Anthropic, Runware, Bria)
- Stripe/PayPal credentials set
- Email service credentials (Resend, Brevo)
- Database connection strings
- Redis connection
- CDN/Storage configuration
8.1.2 - Security Audit
- All debug modes disabled
- CORS properly configured
- SSL certificates valid
- Rate limiting enabled
- API authentication verified
8.1.3 - Performance Check
- Database indexes verified
- Static assets optimized
- CDN caching configured
- Celery workers scaled appropriately
8.2 - Go Live ⏳
- Deploy to production
- Run smoke tests
- Monitor error logs (30 min)
- Verify all integrations working
- Announce launch
PHASE 9: Documentation & Media 🟢 (Post-Launch)
Goal: Marketing and support materials
9.1 - Feature Screencasts ⏳
Per-Page Screenshots/Recordings
| Page | Screenshot | Screencast | Notes |
|---|---|---|---|
| Dashboard | [ ] | [ ] | Show populated widgets |
| Planner/Keywords | [ ] | [ ] | Show keyword management |
| Planner/Clusters | [ ] | [ ] | Show clustering flow |
| Writer/Tasks | [ ] | [ ] | Show content generation |
| Writer/Review | [ ] | [ ] | Show review workflow |
| Automation | [ ] | [ ] | Show pipeline running |
| Publisher/Calendar | [ ] | [ ] | Show scheduling |
Important: Use real/representative data, not empty states
9.2 - Explainer Videos ⏳
| Video | Topic | Duration | Status |
|---|---|---|---|
| 1 | Platform Overview | 3-5 min | [ ] |
| 2 | Keyword to Content Flow | 5-7 min | [ ] |
| 3 | Automation Setup | 3-5 min | [ ] |
| 4 | WordPress Integration | 3-5 min | [ ] |
| 5 | Credits & Billing | 2-3 min | [ ] |
9.3 - Tutorial Videos ⏳
| Tutorial | Workflow | Duration | Status |
|---|---|---|---|
| Getting Started | Signup → First Content | 5-7 min | [ ] |
| Bulk Keywords | Import → Cluster → Ideas | 5 min | [ ] |
| Content Generation | Task → Review → Publish | 5 min | [ ] |
| Team Management | Add Users → Roles | 3 min | [ ] |
PHASE 10: Future Products & Addons 🟢 (Post-Launch)
Goal: Revenue expansion options
10.1 - Service Packages ⏳
10.1.1 - Initial Setup Package
Price: $149 (One-time)
Includes:
- Site added to IGNY8 platform
- Complete WordPress integration setup
- 500 high-opportunity keywords researched
- Initial clustering configuration
- First automation run
10.1.2 - Managed Plan
Price: TBD (Monthly)
Includes:
- Initial Setup Package
- Monthly keyword research & updates
- Ongoing content pipeline management
- Performance monitoring
- Partner agency fulfillment
10.2 - Pricing Page Updates ⏳
Required Changes:
- Design clear product/addon presentation
- Separate subscription plans from addons
- Create smooth upsell journey
- Avoid confusing pricing tiers
- Mobile-responsive pricing tables
Quick Reference: Execution Checklist
Pre-Launch Critical Path
Week 1: Phase 1 (Cleanup) + Phase 2 (Templates)
Week 2: Phase 3 (Testing) + Phase 4 (Email)
Week 3: Phase 5 (UX) + Phase 6 (Backup/Cleanup)
Week 4: Phase 7 (User Testing) + Phase 8 (Deploy)
Daily Standup Questions
- What phase am I in?
- What's blocking progress?
- Any critical bugs found?
- Is timeline on track?
Document Owner: IGNY8 Team
Review Frequency: Daily during pre-launch
Escalation: Any blocking issue → immediate attention