How kothakula-sagar/abra-zylo-seo-generator works
Purpose and principal workflow
Abra Zylo is a browser-based eCommerce SEO portal. A user opens the public landing page or the application directly; the landing page’s calls to action lead to the authenticated portal. After signing in, the user can enter product information and an image, generate and validate SEO content, and manage product records and generation history. Separate portal workflows support page and performance audits, campaign preparation, and catalog organization. A standalone storefront demo is also present, but its relationship to the portal is not established.
Components
Entry points and portal orchestration
• Public landing page — index.html: Public marketing entry point; the README says its calls to action open the application and that it does not load Firebase or the protected app.
• SEO Generator portal — main.html: Application entry point documented as containing authentication and the portal’s feature areas.
• Portal controller — js/app.js: Coordinates authentication-dependent entry, maintenance-state watching, tab selection, and lazy loading of portal modules; its excerpt shows it dispatching to dashboard, generator, audits, history, marketing, and other areas.
Identity, persistence, and shared assets
• Authentication and user profile — js/auth.js: Handles login, registration, password reset, logout, session callbacks, and retrieval of provider API keys; the excerpt shows it using Firebase and UI helpers.
• Firebase access layer — js/firebase.js: Initializes Firebase Authentication, Firestore, and Firebase Storage, then exposes a shared API for those services.
• Maintenance controls — js/maintenance.js: Watches portal maintenance state; the app controller uses that watch to respond to state changes.
• Product model helpers — js/product-model.js: Provides product normalization and model-number checks used by the generator and marketing module, as indicated by their imports.
• Image upload and transformation — js/cloudinary.js: Implements the shared Cloudinary image service; generator and marketing excerpts show them calling its upload function.
Product SEO workflow
• SEO generation and product workflow — js/seo-generator.js: Builds a product-context prompt, prepares product images, calls AI, checks model-number uniqueness, and supports restoring saved SEO records; imports also show its use of quality, storage, UI, and helper modules.
• AI provider requests — js/ai.js: Implements the AI-call module imported by the generator; the README documents Groq, Gemini, and OpenRouter as supported providers.
• SEO quality and factual checks — js/seo-quality.js: Contains deterministic SEO evaluation and fact-prompt logic; the README distinguishes source confirmation and human review from checklist scoring.
• SEO record handling — js/seo-store.js: Implements SEO storage logic and imports the quality module; the sampled inputs do not show its callers.
• Generation history and restoration — js/history.js: Displays product generation status and versions and invokes the generator’s restore function for a selected record.
Product operations and portal surfaces
• Products, campaigns, and Meta catalog — js/marketing.js: Implements product management and campaign/catalog workflows; excerpts show product image uploads and product-model normalization.
• Customer management — js/customers.js: Implements customer-facing portal management operations; the app controller dispatches to its customer view.
• Dashboard — js/dashboard.js: Loads portal statistics and is invoked by the controller when the dashboard tab is selected.
• Accounts administration — js/accounts.js: Implements account-management functionality; the app controller dispatches to its view.
• Settings — js/settings.js: Implements settings, imports Firebase/auth/AI helpers, and is rendered by the controller for the settings tab.
Audits and shared interface
• SEO and performance audits — js/audit.js: Implements audit workflows, including a PageSpeed/Lighthouse run, report display, and audit-history actions.
• PageSpeed analysis — js/pagespeed.js: Provides the PageSpeed audit function called by the audit module.
• Performance AI analysis — js/performance-ai.js: A separate performance-analysis module; the excerpt index shows an authentication dependency, but not its caller.
• Performance audit history — js/audit-history.js: Saves, renders, compares, exports, and deletes performance audit reports using Firebase.
• Shared UI helpers — js/ui.js: Provides DOM-facing UI functions such as alerts, loading progress, modals, and tab switching.
Separate storefront demo
• Storefront state and commerce rules — storefront-demo/store.js: Holds demo product data and state operations including cart, delivery, checkout validation, stock, and orders.
• Storefront interface — storefront-demo/app.js: Implements the demo storefront application and imports its state module; the README and sampled inputs do not establish integration with the SEO portal.
Relationships
• External portal user *(external; null repository path)* -> Public landing page: opens the public site; evidence: README.md.
• Public landing page -> SEO Generator portal: its calls to action open the application; evidence: README.md.
• External portal user *(external; null repository path)* -> SEO Generator portal: can open the application directly; evidence: README.md.
• SEO Generator portal -> Portal controller: the README identifies the HTML page as the application entry point and js/app.js as its main controller; evidence: none (inferred).
• Portal controller -> Authentication and user profile: responds to authentication state and routes unauthenticated users to the auth view; evidence: js/app.js.
• Portal controller -> Maintenance controls: starts a maintenance-state watch and responds to state changes; evidence: js/app.js.
• Authentication and user profile -> Firebase access layer: performs authentication operations through Firebase helpers; evidence: js/auth.js.
• Portal controller -> Dashboard: calls Dashboard.loadStats() when the dashboard tab is selected; evidence: js/app.js.
• Portal controller -> Products, campaigns, and Meta catalog: dispatches to marketing render functions for those tabs; evidence: js/app.js.
• Portal controller -> Customer management: calls its customer renderer; evidence: js/app.js.
• Portal controller -> Accounts administration: calls its renderer; evidence: js/app.js.
• Portal controller -> Settings: calls its renderer; evidence: js/app.js.
• Portal controller -> SEO generation and product workflow: initializes the generator when the generate tab is selected; evidence: js/app.js.
• SEO generation and product workflow -> AI provider requests: calls the AI module with a product prompt, user key, and provider; evidence: js/seo-generator.js.
• AI provider requests -> External AI providers *(external; null repository path)*: provider choices are documented as Groq, Gemini, and OpenRouter; evidence: README.md.
• SEO generation and product workflow -> Image upload and transformation: uploads product images through the Cloudinary module; evidence: js/seo-generator.js.
• Image upload and transformation -> Cloudinary *(external; null repository path)*: the module implements the Cloudinary service; evidence: js/cloudinary.js.
• SEO generation and product workflow -> Product model helpers: checks model-number uniqueness; evidence: js/seo-generator.js.
• SEO generation and product workflow -> SEO quality and factual checks: imports and uses the factual prompt helper; evidence: js/seo-generator.js.
• Generation history and restoration -> SEO generation and product workflow: invokes the generator’s restore function for a selected record; evidence: js/history.js.
• SEO and performance audits -> PageSpeed analysis: calls the PageSpeed audit function; evidence: js/audit.js.
• PageSpeed analysis -> Google PageSpeed Insights *(external; null repository path)*: PageSpeed/Lighthouse analysis is documented; evidence: README.md.
• SEO and performance audits -> Performance audit history: imports and uses history operations; evidence: js/audit.js.
• Performance audit history -> Firebase access layer: saves and manages report records through Firebase; evidence: js/audit-history.js.
• Storefront interface -> Storefront state and commerce rules: imports the state module; evidence: storefront-demo/app.js.
Coverage limits
Several modules are represented by the source index or README rather than full excerpts. In particular, the exact generator-to-SEO-storage call path, the callers of performance AI analysis, and the storefront demo’s launch path were not established. No portal-to-storefront integration is shown.
Main entry points: app.js Portal controller · seo-generator.js SEO generation workflow · main.html SEO Generator portal · audit.js SEO & performance audits
Components 27
Portal Entry & Runtime
- Public landing page
index.html - SEO Generator portal
main.html - Portal controller
js/app.js
Identity & Shared Services
- Authentication & profile
js/auth.js - Firebase access layer
js/firebase.js - Maintenance controls
js/maintenance.js - Product model helpers
js/product-model.js - Image upload service
js/cloudinary.js
SEO Product Workflow
- SEO generation workflow
js/seo-generator.js - AI provider requests
js/ai.js - SEO quality checks
js/seo-quality.js - SEO record handling · Sampled inputs do not show its callers.
js/seo-store.js - Generation history
js/history.js
Portal Operations
- Products & campaigns
js/marketing.js - Customer management
js/customers.js - Dashboard
js/dashboard.js - Accounts administration
js/accounts.js - Settings
js/settings.js
Audits
- SEO & performance audits
js/audit.js - PageSpeed analysis
js/pagespeed.js - Performance audit history
js/audit-history.js
Storefront Demo
- Storefront interface
storefront-demo/app.js - Storefront commerce rules
storefront-demo/store.js
Other components
- Portal user
- AI providers
- Google PageSpeed Insights
- Cloudinary
Connections 25
- Portal user → Public landing page: opens
README.md - Public landing page → SEO Generator portal: opens via CTA
README.md - Portal user → SEO Generator portal: opens directly
README.md - SEO Generator portal → Portal controller: hands off to · Inferred; not shown in the code that was read.
- Portal controller → Authentication & profile: routes auth
js/app.js - Portal controller → Maintenance controls: watches state
js/app.js - Authentication & profile → Firebase access layer: uses
js/auth.js - Portal controller → Dashboard: loads stats
js/app.js - Portal controller → Products & campaigns: dispatches tabs
js/app.js - Portal controller → Customer management: renders view
js/app.js - Portal controller → Accounts administration: renders view
js/app.js - Portal controller → Settings: renders view
js/app.js - Portal controller → SEO generation workflow: initializes
js/app.js - SEO generation workflow → AI provider requests: calls
js/seo-generator.js - AI provider requests → AI providers: requests generation
README.md - SEO generation workflow → Image upload service: uploads images
js/seo-generator.js - Image upload service → Cloudinary: uses service
js/cloudinary.js - SEO generation workflow → Product model helpers: checks uniqueness
js/seo-generator.js - SEO generation workflow → SEO quality checks: uses fact prompts
js/seo-generator.js - Generation history → SEO generation workflow: restores record
js/history.js - SEO & performance audits → PageSpeed analysis: runs analysis
js/audit.js - PageSpeed analysis → Google PageSpeed Insights: analyzes pages
README.md - SEO & performance audits → Performance audit history: uses history
js/audit.js - Performance audit history → Firebase access layer: manages reports
js/audit-history.js - Storefront interface → Storefront commerce rules: imports
storefront-demo/app.js