How 06samuel/simulation_app works
Project type and purpose
• This is a static, multi-page front-end web application (“Rent Apart” simulation) composed entirely of HTML, CSS, and JavaScript prototypes.
• It uses GitHub Actions and Jekyll to deploy to GitHub Pages as a static site.
a. Developer’s GitHub Repository
– Contains all source files: HTML pages (index.html, apartments.html, etc.), CSS (styles.css), JS (main.js), and configuration (.github/workflows/jekyll-gh-pages.yml).
b. Continuous Integration / Continuous Deployment (CI/CD) Pipeline
– GitHub Actions workflow triggered on pushes to the repo.
– Jekyll build step (optional, if markdown or templating is used), then deploy to GitHub Pages.
c. Static Hosting / Content Delivery Network
– GitHub Pages serves the built site via a global CDN.
d. End-User’s Web Browser
– Fetches HTML, CSS, JS assets from the CDN.
– Renders the various pages (dashboard, galeri, kalender, landing pages, profile, etc.).
e. (Optional) External API Integration
– For example, kalender_google.html hints at Google Calendar integration via client-side API calls.
Architectural patterns and design principles
• Static site architecture: separation of build/deploy pipeline and runtime delivery
• Client-side rendering: HTML templates + JS for interactivity (main.js)
• Folder structure reflects multiple UI prototypes, each page is standalone
• Single Responsibility: each component (repo, CI/CD, hosting, client) has a clear role
Key technologies and frameworks
• HTML5 – page layout, multiple prototypes (apartments, details, reports, etc.)
• CSS – styles.css for theming across pages
• JavaScript – main.js for UI behavior
• GitHub Actions – .github/workflows/jekyll-gh-pages.yml for CI/CD
• Jekyll (via GitHub Pages) – optional static generator
• GitHub Pages / CDN – global static asset hosting
• Potential External APIs – e.g., Google Calendar