backend-docs
Shipped: The data model, explained
I built the documentation for mern-auth-api, an Express/MongoDB auth API with one users collection. README.md covers every endpoint with its real status codes (including the handlers that hang), local setup with env vars and a seed script, and eight decisions I'd revisit at ten times the traffic. DATA MODEL.md describes the collection field by field and the implicit links between documents, and has a constraints table with what each rule prevents. It lists the queries that carry the load with the index each uses, names the unindexed reset-token lookup as the one that breaks first at 10x, and includes the commands and seed script to capture the explain() plans. Repository: https://github.com/abbasg-dev/mern-auth-api Built for the Verified Backend Internship · Documentation
Shipped: A README a reviewer can follow
I built Task Desk, a deployable task-management application with a responsive web interface and JSON API. A reviewer can visit https://task-desk-api.vercel.app to see the working UI, add tasks, search and filter them, mark them complete, delete them, and confirm the service status. The API can be verified at /api/health and /api/tasks, while the README documents the data model, environment variables, local setup, Vercel deployment, endpoint inputs and outputs, success and failure status codes, Mermaid request flow, known limitations, and scaling decisions. The repository also includes an MIT license, concrete Node.js prerequisites, and the DevConnect badge, allowing the reviewer to clone, run, inspect, and test the project without additional guidance. Repository: https://github.com/azizulabedinazmi/Task-Desk-API Live: https://task-desk-api.vercel.app/ Built for the Verified Backend Internship · Documentation
Shipped: A README a reviewer can follow
Rewrote the README for the habit-tracker final project so a stranger can clone, run, and call one endpoint using only the README — verified with the exact quickstart commands (clone, node server.js, one curl call to /signup, expecting a 201 with id/email/token). Every environment variable (PASSWORD PEPPER, PORT, DB PATH, NODE ENV) is listed with whether it's required, its default if unset, and where it's used — none are required to start, which is documented explicitly. Every endpoint (/signup, /login, /habits, /habits/:id/checkins) has a full status-code table covering all failure cases (400s with field names, 401, 404, 409), not just the success path. Prerequisites name Node.js v22.x specifically (required for node:sqlite), not "a recent runtime." A dedicated "Known limitations" section lists what the service doesn't do: no pagination, no token expiry/revocation, no rate limiting, open CORS, single-file SQLite, Render free-tier cold starts, no migrations. Repository: https://github.com/mohammedoomatia-max/habit-tracker Built for the Verified Backend Internship · Documentation
Shipped: A README a reviewer can follow
Repository: https://github.com/saikatdas47/expense-tracker Built for the Verified Backend Internship · Documentation
Shipped: The data model, explained
Repository: https://github.com/Ramsha-Anwar/context-query-ai/blob/master/DATA MODEL.md Built for the Verified Backend Internship · Documentation
Shipped: A README a reviewer can follow
I built a full-stack Habit Tracker application using Node.js, Express, and SQLite for the backend, paired with a clean HTML/JS frontend. A reviewer can easily check that all criteria are met directly in the repository's README, where I've provided simple, step-by-step local setup instructions to get everything running and test an endpoint within twenty minutes. The documentation also clearly lists all environment variables with their sources and fallback values, details every API endpoint along with its input, output, and full status code coverage including errors and idempotency handling, and wraps up with a transparent section detailing the project's limits and what it does not do. Repository: https://github.com/oliviamol/Habittracker/blob/main/habit-tracker-README.md Built for the Verified Backend Internship · Documentation
Shipped: The data model, explained
Repository: https://github.com/garima-2006/ticket-sales-api Built for the Verified Backend Internship · Documentation