How air-zy/journal-app-programming-club works
Project type and purpose
• Purpose: Allow users to create and view journal entries in the browser (hosted on Glitch).
File structure
• Top-level files only:
• journal.html – the markup and entry point
• journal.css – styling (presentation layer)
• journal.js – application logic (behavior, interactions, data persistence)
• Project 2.docx – assignment spec (not part of runtime)
• There are no server or database folders; persistence likely uses browser storage (localStorage).
README for additional insights
• Confirms it’s a front-end demo deployed on Glitch.
• No mention of external APIs or microservices—pure client logic.
Elements
• Clear labels for each component (e.g., “journal.js – App Logic”)
• HTTP GET of assets from Glitch → Browser
• Event flows: User → journal.js → DOM/localStorage
• Data retrieval: journal.js → localStorage → UI
• Rectangles for code artifacts (HTML/CSS/JS)