218 lines
3.6 KiB
Markdown
218 lines
3.6 KiB
Markdown
Expert-Level Product / Development Prompt
|
||
# 🔐 1. Modern Google Authentication UI
|
||
|
||
The current Google Sign-In button looks outdated and is not user-friendly.
|
||
|
||
Requirements:
|
||
|
||
Replace default Google Sign-In/Github/Facebook/instagram button with a modern, branded, accessible UI
|
||
|
||
Use:
|
||
Rounded corners
|
||
Subtle hover + loading state
|
||
Google logo aligned with Google branding guidelines
|
||
Button should clearly indicate:
|
||
“Continue with Google”
|
||
Support dark & light themes
|
||
|
||
Ensure WCAG accessibility compliance
|
||
|
||
⚙️ 2. Admin Setup – Social Media Configuration
|
||
|
||
Admin should be able to manage all social media links from a single setup page.
|
||
|
||
Admin Setup Page – Social Media Section:
|
||
For each social media platform:
|
||
Facebook
|
||
Instagram
|
||
Twitter / X
|
||
LinkedIn
|
||
YouTube
|
||
WhatsApp
|
||
|
||
Any future platform (extensible)
|
||
|
||
Fields per platform:
|
||
|
||
Social media URL / ID
|
||
Checkbox: “Display on Landing Page”
|
||
Checkbox: “Active / Inactive”
|
||
|
||
Frontend Behavior:
|
||
Only platforms that are:Active AND marked “Display on Landing Page” should appear on the landing page footer / header.
|
||
|
||
✉️ 3. Email System – SMTP Configuration (Admin)
|
||
|
||
Admin should fully control email delivery via SMTP.
|
||
Admin App Setup Page – Email Configuration:
|
||
SMTP Host
|
||
SMTP Port
|
||
Username
|
||
Password (encrypted at rest)
|
||
From Email Address
|
||
|
||
From Display Name
|
||
|
||
TLS / SSL toggle
|
||
|
||
Test Email button
|
||
|
||
📩 4. Email Features & Business Logic
|
||
✅ 4.1 User Registration – Activation Email
|
||
|
||
When a user registers:
|
||
|
||
Send account activation email
|
||
|
||
Include:
|
||
|
||
User name
|
||
|
||
Secure activation link
|
||
|
||
Expiry time for activation link
|
||
|
||
Template Requirements:
|
||
|
||
HTML + Plain text version
|
||
|
||
Branded header & footer
|
||
|
||
Mobile responsive
|
||
|
||
Clear CTA button: “Activate Account”
|
||
|
||
🎓 4.2 Webinar Registration Emails
|
||
|
||
When a user opts for a webinar (free or paid):
|
||
|
||
🆓 Free Webinar Email
|
||
|
||
Confirmation email immediately after successful registration
|
||
|
||
Include:
|
||
|
||
Webinar title
|
||
|
||
Date & time
|
||
|
||
Access link (if applicable)
|
||
|
||
“Add to Calendar” link
|
||
|
||
💳 Paid Webinar Email
|
||
|
||
Confirmation email after successful payment
|
||
|
||
Include:
|
||
|
||
Payment confirmation
|
||
|
||
Invoice / transaction ID
|
||
|
||
Webinar details
|
||
|
||
Access link
|
||
|
||
Support contact info
|
||
|
||
Templates must be different for:
|
||
|
||
Free Webinar
|
||
|
||
Paid Webinar
|
||
|
||
🗂️ 5. Email Audit & Logging (Admin Feature)
|
||
|
||
All outgoing emails must be logged.
|
||
|
||
Email Log Requirements:
|
||
|
||
User ID
|
||
|
||
User Email
|
||
|
||
Email Type (Activation, Free Webinar, Paid Webinar, etc.)
|
||
|
||
Subject
|
||
|
||
Timestamp
|
||
|
||
Delivery status (Sent / Failed)
|
||
|
||
Error message (if failed)
|
||
|
||
Admin Capabilities:
|
||
|
||
View all sent emails
|
||
|
||
Filter by:
|
||
|
||
User ID
|
||
|
||
Email type
|
||
|
||
Date range
|
||
|
||
Search by email address
|
||
|
||
🧹 6. Email Retention & Cleanup Policy
|
||
|
||
To comply with best practices and reduce storage usage:
|
||
|
||
Requirements:
|
||
|
||
Admin-configurable retention period (default: 60 days)
|
||
|
||
Retention period configurable from Admin App Setup Page
|
||
|
||
Automatic cleanup via:
|
||
|
||
Cron job / background worker
|
||
|
||
Deleted data:
|
||
|
||
Email content
|
||
|
||
Logs (except minimal audit metadata if required)
|
||
|
||
🛠️ 7. Technical & Architecture Expectations
|
||
|
||
Modular & scalable implementation
|
||
|
||
Email templates reusable & versioned
|
||
|
||
Secure handling of credentials
|
||
|
||
Environment-agnostic (Dev / QA / Prod)
|
||
|
||
Clean separation:
|
||
|
||
UI
|
||
|
||
API
|
||
|
||
Business logic
|
||
|
||
Background jobs
|
||
|
||
🚀 Bonus (Optional but Recommended)
|
||
|
||
Email preview in admin panel
|
||
|
||
Resend failed emails
|
||
|
||
Soft delete before permanent cleanup
|
||
|
||
Webhook for email delivery status (future)
|
||
|
||
If you want, next I can:
|
||
|
||
Convert this into Jira epics + user stories
|
||
|
||
Provide DB schema (SMTP config, email logs, retention)
|
||
|
||
Generate HTML email templates
|
||
|
||
|
||
Write a perfect AI prompt for Cursor / Copilot |