- Check multiple storage sources for website URL (props, localStorage, sessionStorage)
- Add validation to prevent API calls without website URL
- Improve debugging logs to track data flow
- Make CompetitorAnalysisStep more resilient to production edge cases
- No breaking changes, just defensive improvements
- Move Step 3 router from optional to core routers in router_manager.py
- Add direct import of step3_routes in app.py for visibility
- Make ExaService initialization optional to prevent deployment failures
- Fix 404 error on /api/onboarding/step3/discover-competitors endpoint
- Created ALwrity introduction page with vision summary
- Added detailed installation guide with step-by-step instructions
- Created comprehensive configuration guide for API keys and settings
- Added first steps guide with complete user onboarding flow
- Updated navigation structure to include all new pages
- Preserved existing documentation while organizing it logically
- Optimized for SEO with proper structure and metadata
- Fixed build directory path in GitHub Actions workflow
- Updated artifact upload path to match build output
- This should resolve the GitHub Pages deployment issue
- Created comprehensive MkDocs configuration with Material theme
- Set up organized documentation structure for ALwrity features
- Added GitHub Pages deployment workflow
- Created initial documentation pages:
- Homepage with feature overview
- Quick Start guide
- Blog Writer and SEO Dashboard feature docs
- Comprehensive troubleshooting guide
- Configured responsive design with dark/light mode toggle
- Added search functionality and navigation
- Set up automatic deployment to GitHub Pages
The documentation site will be available at https://alwrity.github.io/ALwrity
- Improve CONTRIBUTING.md with detailed setup instructions and ALwrity-specific guidelines
- Enhance SUPPORT.md with comprehensive troubleshooting for AI services and GSC integration
- Update SECURITY.md with ALwrity-specific security features and considerations
- Add issue template configuration and question form for better issue management
- Enhance PR template with ALwrity-specific checklist items
- Add comprehensive .github/README.md explaining all community health files
These improvements provide better contributor experience and project visibility.
- Include route protection implementation
- Include Google Search API warning removal
- Include Stability AI import fixes
- Include updated README and removed SETUP_GUIDE
- Ensure feature branch has all latest improvements
- Add No Website button to Step 2 with business description form
- Implement onboarding cache service for browser-side data storage
- Add business info database models and API endpoints
- Update API key manager to save keys to .env file immediately
- Add database migration scripts for business info table
- Create reset onboarding script for fresh starts
- Implement hybrid data storage (API keys to backend, other data to cache)
- Add comprehensive business info CRUD operations
- Include database table creation and migration tools
- Replace actual API keys with placeholder values in frontend/env_template.txt
- Ensure template files only contain example values, not real secrets
- Fix GitGuardian security scan issues
- Add GSC API service with OAuth2 authentication
- Implement Clerk authentication for frontend and backend
- Add GSC login button and OAuth callback handling
- Create comprehensive GSC data fetching and caching
- Add authentication middleware for backend API protection
- Implement real-time GSC data integration in SEO dashboard
- Add user-specific GSC site management
- Include comprehensive logging and error handling
- Add TypeScript support and proper type definitions
- Create environment templates and setup documentation
- Update gitignore to exclude sensitive credential files
Features added:
- GSC OAuth2 authentication flow
- Real-time search analytics data
- Site list management
- Sitemap analysis
- User-specific data isolation
- Comprehensive error handling
- Authentication token management
- Popup-based OAuth flow
- Data caching and refresh mechanisms
Note: gsc_credentials.json should be created locally with your Google OAuth credentials
- Add No Website button to Step 2 with business description form
- Implement onboarding cache service for browser-side data storage
- Add business info database models and API endpoints
- Update API key manager to save keys to .env file immediately
- Add database migration scripts for business info table
- Create reset onboarding script for fresh starts
- Implement hybrid data storage (API keys to backend, other data to cache)
- Add comprehensive business info CRUD operations
- Include database table creation and migration tools
- Create ProtectedRoute component to guard routes based on onboarding status
- Protect all non-onboarding routes (dashboard, blog-writer, seo, etc.)
- Users must complete onboarding before accessing any features
- Prevents confusion and broken functionality for new users
- Improves user experience by guiding users through proper setup
- Add .onboarding_progress.json to .gitignore to prevent tracking
- Remove existing .onboarding_progress.json from Git tracking
- Ensures new users always go through onboarding process
- Fixes issue where users were not presented with onboarding after cloning
- Remove 25+ .pyc files from backend/api/__pycache__/
- Remove .pyc files from backend/api/facebook_writer/
- Remove .pyc files from backend/models/__pycache__/
- Remove .pyc files from backend/services/__pycache__/
- Remove .pyc files from backend/services/llm_providers/__pycache__/
- These files are automatically generated and should not be tracked
- Repository is now clean of Python cache files
- Future .pyc files will be ignored by .gitignore
- Remove backend/api/__pycache__/onboarding.cpython-313.pyc
- Remove backend/api/facebook_writer/services/__pycache__/ files
- Remove backend/services/llm_providers/__pycache__/gemini_provider.cpython-313.pyc
- These files should not be tracked in Git as they are generated automatically
- .gitignore will now prevent future .pyc files from being tracked
