How jumbojhon04/proyectomycs works
Project type and purpose
• This is not a multi-service or microservices system but a static, content-driven tourism website (“ProyectoMyCS”) designed to showcase destinations in Napo Province.
• It uses only frontend technologies (HTML/CSS/JS/Bootstrap) plus a simple PHP contact-form endpoint and a JSON data file.
File structure
• Top-level HTML pages: index.html, about.html, destinos/*.html, hoteles.html, etc.
• css/ – compiled CSS (style.css)
• scss/ – source SCSS/bootstrap overrides and custom styles
• js/ – application scripts (main.js reads hoteles-napo.json; hoteles-napo.json holds hotel data)
• lib/ – third-party JS/CSS libraries (OwlCarousel, Tempusdominus, easing)
• img/ and imgDestinos/ – static images and destination pictures
• mail/ – contact.js (front-end AJAX), contact.php (server-side mail handler)
• No database—data is static JSON or hard-coded in HTML.
README for additional insights
• Project is part of a GitFlow exercise: branches for features, releases, hotfixes.
• Build process: SCSS compilation (likely via a local tool) produces css/style.css.
• Deployment target: any PHP-enabled web server (to service the contact.php).
• Client Browser (UI)
• Static Web Server (hosting HTML/CSS/JS/images/JSON)
• Build Tool (SCSS → CSS compiler)
• Mail Handler (contact.php + SMTP or mail system)
• GitFlow Repository (version control with main, develop, feature branches)
b. Relationships & interactions:
• Browser → HTTP GET → Web Server → serves HTML/CSS/JS/images/JSON
• main.js in browser → reads hoteles-napo.json → renders listings
• contact.js → AJAX POST → contact.php on server → SMTP mail delivery
• Developer Machine → SCSS compiler → output style.css → committed to Git
• Developers ↔ GitHub using GitFlow → deploy stable main to Production Server
c. Architectural patterns & principles:
• Two-tier static architecture (Presentation + Static Data)
• Build-time preprocessing (SCSS) separated from run-time (no client bundler shown, but could be added)
• Single API endpoint pattern for contact form
d. Key technologies & libraries:
• Bootstrap (CSS framework)
• jQuery / easing.js / OwlCarousel / Tempusdominus (UI components)
• PHP mail script (contact.php)
• JSON as lightweight data store (hoteles-napo.json)
• GitFlow for source control
Diagramming recommendations
• Use clear, consistent labels: e.g., “Browser (Chrome/Firefox)”, “Web Server (Apache/Nginx + PHP)”, “SCSS Compiler”, “SMTP Server”.
• Browser → GET /index.html → Web Server
• Browser → GET /js/main.js → Web Server
• Browser (main.js) → fetch hoteles-napo.json → Web Server
• Browser (contact.js) → POST /mail/contact.php → Web Server → SMTP
• Developer → push/pull → GitHub (branches)
• Developer → compile → SCSS → CSS
• Rectangles for runtime components (Browser, Web Server)
• Parallelograms for code/artifacts (SCSS, CSS, JS)
• Clouds or envelopes for external SMTP service