Create .env (or .env.local) at project root with your Firebase web-app config:

VITE_FIREBASE_API_KEY=your_api_key
VITE_FIREBASE_AUTH_DOMAIN=your_app.firebaseapp.com
VITE_FIREBASE_PROJECT_ID=your_project_id
VITE_FIREBASE_STORAGE_BUCKET=your_app.appspot.com
VITE_FIREBASE_MESSAGING_SENDER_ID=000000000000
VITE_FIREBASE_APP_ID=1:000000000000:web:xxxxxxxxxxxxxxx

In your Firebase project:

1. Enable Firestore (start in test mode, or use the rules in firestore.rules.example if provided).
2. Enable Authentication → Email/Password (or any provider you prefer).
3. Add your first user, then set their custom claim or a profiles/{uid} doc with role: 'admin' to unlock the CMS panel.

Editing Content

1. Visit /admin (or click the floating admin toggle if present) and sign in with an admin account.
2. Use the tabbed panel to edit any section. Changes save to Firestore immediately and reflect on the public site live.
3. Until you sign in, the site renders the seeded staticData so design previews work out of the box.

Project Structure

src/
  components/
    cms/          # Admin panel + editable wrappers
    layout/       # Navbar, preloader, smooth scroll, particle cursor
    motion/       # Reusable motion primitives (split text, magnetic, parallax, tilt)
    sections/     # Hero, About, Projects, Skills, Experience, Testimonials, Contact, Footer
    ui/           # Skeleton loaders
  lib/
    firebase.ts            # Firebase init
    firestoreService.ts    # CRUD helpers per collection
    repository.ts          # In-memory cache + Firestore wiring
    ContentContext.tsx     # React context for content + loading state
    AdminContext.tsx       # Auth/role gating
    staticData.ts          # Default seed content
    types.ts               # GlobalContent, Project, Skill, ExperienceEntry, Testimonial, UserProfile
  pages/
    Index.tsx              # Single-page portfolio
    NotFound.tsx

License

MIT

This React web app completed archive review with strong static results. Structure, dependency manifests, documentation, functional source, and common risk patterns were checked by the Tetrees verification pipeline; runtime phases are stated separately. Final verified scores after isolated runtime evidence: overall 8.3 and security 9.