These docs are a work in progress and may not be fully up to date. Some pages may contain internal notes for our team.
Skip to Content
Internal

DropAFinder Engineering Documentation

This site is for engineers and contributors who have access to the three DropAFinder repositories. It assumes you can read code; it explains the why and the where, not the what a well-named function already conveys.

Start here

Codebases

RepoStackInternal docs
dropafinder-app-nextjsNext.js 16, TypeScript, Zustand, TanStack Querycodebases/nextjs/
dropafinder-app-externalSvelte 5, MapLibre, Vite, Cloudflare R2 CDNcodebases/external/
dropafinder-app-backendLaravel 11, PHP 8.2, JWT auth, Eloquentcodebases/backend/

Each codebase folder contains a directory-structure map, a routing/initialization page, and a conventions page that mirrors and expands the repo’s AGENTS.md.

Reference

How-to (developer task-oriented)

Architectural decisions

decisions/ is an ADR-style log capturing why the codebase looks the way it does. These are inferred from the code today; if you’re the author of a decision and disagree with the inference, please correct the relevant file.

Conventions

  • Code references use the form path/to/file.ext:LINE-LINE. Paths are relative to the repo they belong to (e.g. src/lib/api/core.ts is in dropafinder-app-nextjs/).
  • We do not paste source code as documentation. We explain what the code does and why, then show a clean illustrative snippet.
  • Markers:
    • > 🟡 [SCREENSHOT: …] — a UI capture is pending.
    • > 🔴 [NEEDS CLARIFICATION: …] — the author needs an answer from a code owner.
  • See _open-questions.md and _screenshots-needed.md for the consolidated marker backlogs.