How omiras/fototeca-uf1844-ironhack-2025 works
Project Type and Purpose
• Fototeca UF1844 is a small server-rendered full-stack web application built with Node.js, Express and EJS.
• It serves HTML views, supports an AJAX URL-check endpoint, and uses an in‐memory array as its “database.”
File Structure
• index.js – the Express server entrypoint, defines routes, middleware (morgan) and holds the in-memory image array.
• views/ – EJS templates (home, add-image form, 404) plus a shared navbar partial.
• No external “public” folder is shown, so static assets (PicoCSS) likely come from a CDN.
Key Architectural Patterns
• MVC-style separation:
– Model: in-memory JavaScript array
– View: EJS templates in views/
– Controller: route handlers in index.js
• Middleware pipeline (Express + morgan + body-parser + static assets from CDN)
• RESTful/ AJAX endpoint for URL uniqueness check
Main Components
1. Client Browser
– Requests HTML from endpoints /, /new-image.
– Sends AJAX GET to /check-url.
– Submits POST form to /new-image.
2. Express Application (Node.js)
– HTTP Server
– Middleware stack (morgan logger, express.json/urlencoded, static‐asset loader if any)
– Router with three main routes:
• GET / → renders home.ejs (gallery)
• GET /new-image → renders add-image.ejs
• POST /new-image → appends to in-memory array
• GET /check-url → searches array, returns JSON
– EJS View Engine (renders templates + partials)
3. In-Memory Data Store
– A simple JavaScript array of image objects { title, description, url } (resets on restart)
4. External Services
– PicoCSS CDN (delivers CSS)
– Optional: Browser’s DevTools/Network for AJAX logging
Relationships and Data Flows
• Express → EJS Engine → HTML → back to Client.
Essential Elements
• Component labels (Client, Express Server, EJS Engine, In-Memory Store, CDN)
• Middleware flow (morgan, body-parser)
• Routes and their responsibilities