How soydetemporada/website works
Data Ingestion and Processing Layer
• A set of scripts (in the _scripts folder and various PHP, Python, and notebook files) whose purpose is to clean, import, transform, and generate the necessary data (from CSV, Excel, JSON files under _data, data, and _products).
Static Site Generation (Build) Layer
• Build pipeline using Ruby gems (Gemfile) and configuration files (_config.yml, _config-devel.yml) to run the static site generator (Jekyll).
• That it takes as input:
– Layouts (_layouts), includes (_includes), Sass/CSS (_sass, css), and multi-language content (_i18n)
– Data files from _data and content pages (markdown files in _products, etc.)
Client-Facing Frontend
• Browser/client that downloads the static HTML, CSS, and JavaScript resources (js folder, manifest.json for offline support).
• Interactive components such as the seasonal “Buscador” (search), “Investigación”, “Petición” and upcoming “Recetas” sections.
• Mention that geolocation and offline capabilities are achieved via JavaScript (e.g., the use of service workers implied by manifest.json) and that the front-end uses i18n support (from _i18n) to display multilingual content.
Data and Content Storage
– The raw/auxiliary data files (data, _data directories)
– Product listings and details (from both _products and _data/products)
– Configuration files used by the build process
• That these are consumed by both the ETL scripts and by the static-site generator.
Integration & Deployment
• Although this is not a full backend system, illustrate how the “Build Pipeline” is triggered (by a developer commit to the Git repository, continuous integration scripts, or manual build using the provided shell scripts such as generate-beta.sh and install_missing.sh).
• That the final website is then deployed on a static hosting platform (e.g., GitHub Pages or another similar service).
Architectural Patterns and Design Principles
• Separation of concerns: the data ingestion/processing layer is separated from the static site build and the client rendering.
• Reuse/integration of multiple languages (Ruby, PHP, Python) in the ETL layer.
• Internationalization support (i18n) as a cross-cutting concern offered in the content files.