How sashenjayathilaka/photo-sharing-application works
Project Type and Purpose
• This is a full-stack, client-centric photo-sharing app (Pinterest-like).
• Frontend: React.js + TailwindCSS SPA (in /src).
• Backend: Sanity headless CMS (in /sanity) for storing “pins,” comments, users.
• Auth & supporting services: Firebase Authentication (Google sign-in) and (optionally) Firebase Storage.
File Structure
• Top-level:
• package.json, postcss.config.js, tailwind.config.js → build/config.
• public/ → static assets, index.html.
• src/ → React application source.
• sanity/ → custom Sanity Studio configuration and schema.
• src/client.js → initializes Sanity client for querying/mutations.
• src/firebase.js → configures Firebase Auth (and possibly Storage).
• src/components & src/container → React UI and container components.
• Environment variables under README → Sanity dataset & token, Firebase API keys, base URL.
Main Components
a. React SPA (Browser)
• UI Layer: Components (Feed, PinDetail, CreatePin, Navbar…)
• Data Layer: client.js (Sanity queries), firebase.js (Auth calls)
b. Sanity Headless CMS
• Sanity API (GROQ/GraphQL endpoints)
• Dataset (pins, users, comments, images)
c. Firebase Services
• Authentication (Google OAuth)
• (Optional) Storage (for image uploads if used)
d. Hosting/CDN
• Netlify (or similar) serving the SPA via CDN
e. External Dependencies
• TailwindCSS for styling
• PostCSS for processing
Relationships & Data Flows
• User (Browser) → (1) Firebase Auth → Google OAuth Provider → returns JWT
• React SPA uses JWT to guard routes and to attach to API calls as needed.
• React SPA → (2) Sanity Client API → CRUD on pins, comments, users, image assets.
• (Optional) React SPA → (3) Firebase Storage → upload/download raw images.
• Sanity Studio (Admin) → Sanity API → manage content outside of SPA.
Architectural Patterns & Principles
• Single Page Application (SPA) with clear UI/Data separation.
• Headless CMS pattern: decoupled content API (Sanity) from presentation.
• Externalizing secrets & config via environment variables.
• Container/Presentational pattern in React.
• Component-based UI with a central “client” abstraction for data fetching.
• Browser → React SPA (UI & Data Layer)
• Sanity Studio
• Firebase Auth (and Storage if used)
• Hosting/CDN
• User → Firebase Auth → React SPA (login flow)
• React SPA → Sanity API (data flow)
• React SPA → Firebase Storage (if applicable)
• Sanity Studio → Sanity API (admin flow)
• Rectangles for services/code.