How agatocherry/digital-garden-challenge works
Project Type and Purpose
• This is a lightweight, static “digital garden” front-end project. It consists solely of client-side HTML, CSS, and image assets, without any back-end or database layers. The purpose is to let users navigate between ASCII art plant pages (cherry blossom, tulip, sunflower, rose).
File Structure Analysis
• Top-level files:
• README.md – project description
• index.html – entry point
• style.css – global styles
• Directories:
• assets/ – screenshot images for README
• css/ – theme-specific CSS files (rose.css, sunflower.css, tulip.css)
• pages/ – individual plant pages (rose.html, sunflower.html, tulip.html)
• No build scripts, no server code, no dynamic data layers.
Key Architectural Insights from README
• Static site deployed on Vercel (implied by the live demo URL).
• Simple navigation model: index.html links to each plant page.
• Themes are separated into dedicated CSS files for each plant.
Main Components and Their Relationships
a. Browser (Client)
– Renders HTML pages and applies CSS.
b. Static Web Server/CDN
– Hosts and delivers index.html, pages/*.html, style.css, css/*.css, assets/* over HTTP(S).
c. Assets
– ASCII art and image files stored under assets/ and referenced by pages.
d. Navigation Layer
– index.html provides links; each page includes global style.css plus a theme CSS file from css/.
Data Flow:
User’s browser → DNS → Static CDN → GET HTML → GET CSS → GET Images → render pages.
Architectural Patterns and Design Principles
• Single‐page entrypoint with multi-page navigation (traditional static site).
• Separation of concerns:
• Global styles in style.css
• Theme variations in css/*.css
• Content in individual HTML files under pages/
• Cacheability: static assets can be aggressively cached via CDN headers.
Essentials to Capture
– Clear labeling of each component and artifact.
– Note caching at the CDN layer for performance.