karen1554/gart-gallery

Purpose and entry points

This is a static artist/gallery website with a small Node-backed administration surface for managing gallery content and uploaded assets. Public entry points are index.html, galleries.html, works.html, and category-specific work pages such as works-dogs.html and works-landscape.html. The server entry point is server.js.

Public site layer

Public pages are conventional HTML documents styled and enhanced client-side:

• Shared presentation and general behavior: assets/css/style.css, assets/js/script.js

• Works/gallery-specific behavior: assets/js/works.js

• Public content pages: index.html, galleries.html, works.html

The public UI likely reads gallery metadata from a local data source rather than a database, creating a clear browser-to-static/HTTP-content boundary.

Gallery content store

Gallery records are centralized in data/gallery.json. This file is the material content boundary between administration and the public gallery renderer. Uploaded media is held under uploads, so gallery entries likely reference server-hosted image paths rather than embedding media in HTML.

Core paths:

• data/gallery.json

• uploads

• assets/js/works.js

Administration surface

admin-dashboard.html provides a separate management interface, with dedicated styling and JavaScript in assets/css/admin-dashboard.css and assets/js/admin-dashboard.js. Its architectural role is to create, update, or remove gallery metadata and coordinate media uploads through server endpoints exposed by server.js.

Core paths:

• admin-dashboard.html

• assets/js/admin-dashboard.js

• server.js

Server and persistence boundary

server.js is the runtime boundary for dynamic capabilities absent from static HTML: serving the site, exposing data-management APIs, handling uploads, and persisting changes to data/gallery.json and uploads. The application’s persistence model appears filesystem-based, with no database directory or migration layer present.

Core paths:

• server.js

• data/gallery.json

• uploads

Deployment and runtime

Node.js is the primary runtime, indicated by package.json and package-lock.json. render.yaml defines deployment configuration for Render, making Render the expected hosting/infrastructure target. Environment-dependent values are documented through .env.example; these likely support server configuration or administrative access and should remain outside committed source.

Core paths:

• package.json

• render.yaml

• .env.example