What it is
Full-stack email client (Node.js + Google OAuth) — server + web UI.
What broke, and what I’d change
Not written yet. This is the part only I can write — what actually went wrong, and what I’d do differently. It lives in builds/reflections/cmail.md (see _TEMPLATE.md); as soon as that file has words in it, this section fills in on the next build.
Everything else on this page — the spec, the version history, the file counts — is generated from the project’s own build notes and files, so nothing here is guesswork.
Build spec
The project’s own build notes, rendered. Open the raw .md ↗
Show the spec
CMail
Category: Software & Apps · Status: In progress
Full-stack email client (Node.js + Google OAuth) — server + web UI.
Stack / Tools: Full-stack, Node.js, OAuth, Email
Location: ~/projects/cmail-app/
Folder-based project (open the folder to view source/files).
Where it lives
- Published copy on the site (working folder isn't on this Mac):
~/Desktop/portfolio-deploy/demos/cmail.html - Artefacts on the site: 1 files · 172 lines of text · 12 KB
Stack
- HTML ×1
- external tools invoked:
node,npm
What's in the code
cmail.html— 172 lines (HTML)
Verified in the page source
- page title: “CMail — Inbox”
- headings: ' + e.s + ' · New Message
- UI element ids:
c-Drafts,c-Inbox,c-Sent,c-Starred,c-Trash,cbody,csubj,f-Drafts,f-Inbox,f-Sent
_Spec generated from the project's own files on 2026-10-22 (gen-project-specs.py). Everything above was read from the listed files — file counts, line counts, names, routes, headings and script comments. No description was invented._