How codewithsadee/tourly works
Project type and purpose
• Tourly is a purely front-end, static, responsive travel website built with HTML, CSS, and JavaScript. It has no server-side runtime or database—just static assets served over HTTP (in this case via GitHub Pages).
File structure
• Top-level files:
• index.html – entry point
• index.txt – supplementary content (optional)
• README.md, style-guide.md – project documentation
• assets/ – holds all static resources:
• css/style.css – presentation
• js/script.js – client-side behavior
• readme-images/ – screenshots for documentation
README for additional insights
• Confirms use of HTML/CSS/JS only and deployment via GitHub Pages (“Live Demo” link).
• No backend, database, or build pipeline mentioned.
Detailed checklist for the principal software engineer
1. User Layer (Browser)
2. Delivery Layer (Static File Server / CDN)
3. Asset Layer (HTML, CSS, JS, images directories)
4. (Optional) Documentation layer (style-guide.md, README)
5. (Optional) CI/CD flow (Git → GitHub Pages)
• Sequence:
a. Browser requests index.html
b. index.html triggers CSS & JS requests
c. Assets flow back and render
• Optional external calls (e.g., social badges, analytics)
• Components from the file tree are represented or noted as part of the “Asset Layer”