How jamesalday/ladybug works
Project type and purpose
• This is a static front-end website whose sole function is to display a countdown timer (using the FlipClock.js library) and a few content pages (about, book, sermons).
• There is no server-side application logic beyond serving static files; customization is handled entirely in the browser via URL hash parsing.
File structure
• Top level:
• README.md – project description and usage instructions
• HTML files – index.html (home/countdown), about.html, book.html, sermons.html
• css/ – global stylesheets (flipclock.css, style.css)
• fonts/ – custom Novecento font files + CSS to load them
• images/ – any site images (not shown but implied by folder)
• js/ – JavaScript code (app.js, snow.js) and IE‐support shims (html5.js, pie.htc, respond.js)
• No “backend” or server-side code: this is a purely client-side application.
README for additional insights
• The homepage (index.html) initializes the FlipClock countdown, defaulting to 5 days in the future or a custom number of days if the visitor appends #<n> to the URL.
• FlipClock.js is loaded via the css/flipclock.css and likely via a script tag in index.html (not shown but implied).
Main components and relationships
a. Client (web browser)
b. Hosting environment / Static File Server or CDN
c. Static assets grouped by type:
• HTML pages (index.html, about.html, etc)
• CSS (style.css, flipclock.css)
• JS (app.js, snow.js, IE-support scripts)
• Fonts (Novecento webfont files + novecento-font.css)
• Images
d. External library: FlipClock.js (bundled in css/js directories or loaded via CDN)
e. Optional: URL hash parameter parsing logic in app.js
→ Relationships / Data Flow:
• Browser sends HTTP GET → Static Server/CDN → returns requested asset (HTML/CSS/JS/fonts/images)
• index.html and app.js run in the browser → initialize FlipClock with default or hash-derived value → render countdown.
Architectural patterns and design principles
• Static-site architecture: separation of concerns by asset type, no dynamic pages, high cacheability.
• Progressive enhancement / graceful degradation: IE-support scripts ensure HTML5 and CSS features work in older browsers.
• Modularity: styles, scripts, fonts, and images are organized in separate folders.