AG REPAIR ASSISTANT - LOGIN ENABLED DEPLOYMENT INSTRUCTIONS
==========================================================

This package contains the AG Repair Assistant with a simple login page.

STEP 1: Configure Your AWS Settings
-----------------------------------
1. Open config.js in a text editor
2. Replace the placeholder values with your actual AWS details from CloudFormation outputs:
   - API_URL: Your API Gateway URL
   - REGION: Your AWS region

STEP 2: Test Login Credentials
------------------------------
Default demo credentials:
- Username: demo
- Password: demo123

To change credentials:
1. Edit config.js
2. Update DEMO_USERNAME and DEMO_PASSWORD values
3. Save the file

STEP 3: Create Deployment Package
---------------------------------
1. Select ALL files in this folder:
   - index.html (login-enabled version)
   - config.js (updated configuration)
   - asset-manifest.json
   - static/ folder
   - DEPLOYMENT_INSTRUCTIONS.txt
2. Right-click and create ZIP file
3. Name it "ag-repair-frontend-with-login.zip"

STEP 4: Deploy to AWS Amplify
-----------------------------
1. Go to AWS Amplify Console
2. Click "New app" > "Deploy without Git provider"
3. Upload your ZIP file
4. Click "Save and deploy"

STEP 5: Test the Application
---------------------------
1. Visit your Amplify app URL
2. You should see a login page with username/password fields
3. Use the demo credentials to log in
4. After login, you'll see the main AG Repair Assistant interface
5. A logout button will appear in the top-right corner

FEATURES INCLUDED:
- Simple username/password login
- Session persistence (stays logged in on refresh)
- Logout functionality
- Demo credentials for testing
- Clean, professional login interface
- Responsive design

CUSTOMIZATION:
- Change credentials in config.js
- Modify styling in index.html <style> section
- Add company branding/logo as needed
- Integrate with real authentication system if required

SECURITY NOTES:
- This is a simple demo authentication
- For production, integrate with AWS Cognito or other auth systems
- Current implementation stores auth token in localStorage
- Change default credentials before production deployment

TROUBLESHOOTING:
- If login page doesn't appear, check browser console for errors
- Ensure all files are included in the ZIP package
- Verify config.js has correct API URL and region
- Clear browser cache if experiencing issues
