Proposal
Overview

Lucid Project × Corey Fader
Photography

This document outlines the proposed scope of work, and the information required to confirm feasibility and finalize pricing.

Lucid Project
Aug 2026
Proposed Approach

Scope of work.

Lucid Project is exploring the feasibility of expanding components of Corey's existing website and admin system. This is not a rebuild — Corey already has a login where he manages and organizes client galleries. The work is light front-end UX/UI updates to how the public portfolio displays, and new features added to the existing architecture to make client gallery management more capable and more efficient.

Planned deliverables
  • Light front-end updates to how the public portfolio displays — captions, categories, and ordering.
  • Branded client gallery management, with multiple clients able to log into a shared gallery.
  • Automatic link generation and email notification to clients when a gallery is ready.
  • Corey continues uploading and managing everything from the existing portal, made more efficient.
Tools under consideration
  • Where new components are built, Lucid Project plans to use Cloudflare R2 for image storage — a platform built to serve website images quickly, unlike general-purpose storage such as Google Drive, which isn't designed to handle live site traffic.
  • Automatic resizing on upload, so every photo gets a smaller, web-ready copy generated the moment it's added — this is what resolves the slow load times.
  • Final tooling depends on what the existing architecture supports, confirmed through the items below.
Requirements to Confirm Scope & Pricing

Information needed before we proceed.

To confirm what's feasible within the existing architecture and provide accurate pricing, we need the following from Corey's current developer and from Corey directly.

From the Developer
01
Full source code for the site, the client login, and the admin. The underlying files, not the deployed build.
02
Details on the authentication backend, including the database and the service handling password-reset emails.
03
A copy or export of the database.
04
Deployment and environment configuration notes.
From Corey
05
Confirmation of account ownership for hosting, domain, database, and email service — registered to Corey or to the developer.
06
Location and storage arrangement for the original full-resolution photos.
07
Current usage status of the client gallery — active or dormant.
Ownership Considerations

Why this matters, regardless of scope.

If hosting, domain, database, or email service accounts are registered under the developer's name rather than Corey's, Corey does not have full control of his own site. Changes, backups, and password resets would all require the developer's involvement. This is a common situation and straightforward to resolve, but should be confirmed and corrected as part of this work.