dast11lp/generation-e-connect

Purpose and Entry Points

This is a static, multi-page Spanish-language site with separate HTML/CSS/JS bundles per feature area. There is no documented backend, build system, or package runtime. The top-level entry is index.html; primary page entry points include home/home.html, learn/learn.html, login/login.html, register/register.html, and admin/admin.html.

Page-Oriented Frontend Architecture

Each major feature owns its markup, styling, and browser-side behavior, suggesting direct navigation between standalone HTML documents rather than a client-side router. Core page modules are:

• Landing/home: home/home.html, home/home.js, home/home.css

• Learning experience: learn/learn.html, learn/learn.js, learn/learn.css

• Authentication screens: login/login.html, login/login.js, register/register.html

• Administrative area: admin/admin.html, admin/admin.js, admin/admin.css

Shared Layout Components

Navigation and footer are independently packaged HTML fragments with paired JS and CSS, likely loaded or injected by page scripts rather than compiled into a shared layout.

• Navbar: navbar/navbar.html, navbar/navbar.js, navbar/navbar.css

• Footer: footer/footer.html, footer/footer.js, footer/footer.css

• Cross-page styling: global.css

The boundary is browser DOM composition: pages consume shared markup/assets and apply their own behavior.

Learning Domain and State

The learning section is the most structured subsystem. It contains a main coordinator, seed data, browser storage handling, and reusable progress/program components:

• Orchestration and local content: learn/learn.js, learn/seed.js, learn/storage.js

• Program-form component: learn/components/program-form/program-form.html, learn/components/program-form/program-form.js

• Progress display component: learn/components/progress-bar.html, learn/components/progress-bar.js

Likely flow: seed data initializes or supplements client state; storage.js persists it in browser storage; learn.js renders and updates learning UI; form and progress components collect program data and reflect completion state. No server persistence is evidenced.

Content and Engagement Pages

Several independent static/content workflows provide informational or conversion-oriented surfaces:

• About: about/about.html, about/script.js

• Contact: contact/contact.html, contact/script.js

• Resources: resources/resources.html, resources/resources.js

• Stories: stories/stories.html, stories/stories.js

• Employment portals: portales_empleo/empleo.html, portales_empleo/styles.css

These pages follow the same page-local JS/CSS boundary and may share global navigation/footer assets.

Runtime, Infrastructure, and External Boundaries

The material runtime is the browser: HTML, CSS, and vanilla JavaScript. Deployment can be static-file hosting because no server code, dependency manifest, API client layer, or build configuration is present. Persistent state, where implemented, is likely browser-local through learn/storage.js. Static visual assets are served from assets/images/logos/header.jfif; no external service integration is identifiable from the repository tree.