How var3la/somosgrupohotusa works
Project type and purpose
• This is a static, front-end website: a collection of HTML templates, CSS, JS and image assets, built to showcase “Grupo Hotusa” content per the Adobe XD design spec.
• No server-side application code or database lives here—everything is served as static files (HTML/CSS/JS).
File structure
• Top-level HTML:
• index.html, diseño.html, slides.html, swiperDoble.html
• menu99_tpl-slideGrupos.html, tpl-header-gh.html
• Asset folders:
• css/ (style.css, critical.css, imgs/)
• js/ (scripts.js)
• imgs/
• diseño_files/ (downloaded assets & scripts e.g. new-relic, utilitynav.js)
• “modules/tpl-slideGrupos.html” holds partial templates for reuse.
• No build scripts—flat structure suggests direct deployment of these files.
README for additional insights
• Points to an Adobe XD URL with design specs—indicates the goal: pixel-perfect front end.
Main components
a. User’s Web Browser
b. CDN or Web Server (e.g. NGINX, Apache, S3+CloudFront)
c. Static Asset Store (your repository of HTML, CSS, JS, images, modules)
d. External Services
• New Relic (analytics delivered via diseño_files/new-relic…js)
• Any other third-party scripts (share.js, privacy-standalone.js)
e. Design Source (Adobe XD) – optional, to show input into dev process
Relationships & data flow
• User → HTTP GET → CDN/Web Server → returns HTML
• HTML → loads CSS and JS assets from “/css/”, “/js/”, “/diseño_files/”
• JS widgets call out to third-party services (New Relic, sharing, privacy)
• Module templates included by HTML via static includes (no dynamic server templating)
Architectural patterns & design principles
• Static-site architecture: “presentation-only” architecture with no backend
• Use of partial templates (modules/) to DRY up markup
• Separation of concerns: CSS in css/, JS in js/, images in imgs/
• Critical CSS inlined (critical.css) for performance
• Deferred or async external scripts (new-relic, privacy) for load-time optimization
Essential elements
• Browser: entry point for a user
• CDN/Web Server: hosting layer
• Asset Store: show directories (css/, js/, imgs/, diseño_files/, modules/)
• External services: New Relic, sharing, privacy
• Data flow: asset requests, script calls
• Optional: design-to-code process (Adobe XD → developer → commits)