G&M Maintenance Portal — Project Notes Index
Per-project notes hub for the G&M Maintenance Portal. The portal is a Next.js + Prisma + Vercel app that gives every G&M maintenance client a private URL where their entire quarterly maintenance history lives.
Quick links
| What | Where |
|---|---|
| Codebase | ~/Projects/gm-maintenance/ |
| Codebase docs | ~/Projects/gm-maintenance/CLAUDE.md (stack, routes, env vars, multi-site, fiscal calendars, traffic JSON) |
| Portal ops skill (deploys, client setup, plugin pulls, report lifecycle) | ~/.claude/skills/gm-portal/SKILL.md |
| Maintenance ops skill (the quarterly workflow that writes data to this portal) | ~/.claude/skills/maintenance/SKILL.md |
| Maintenance value/sales doc (how to talk about the portal in client pitches) | ~/.claude/skills/maintenance/VALUE-AND-SALES.md |
| Production admin | https://maintenance.grainandmortar.com/admin |
| Per-client portal URL pattern | https://maintenance.grainandmortar.com/portal/[token] |
| GitHub repo | https://github.com/ericdowns/gm-maintenance |
| Vercel project | frontend (NOT gm-maintenance — see CLAUDE.md for the deploy gotcha) |
What the portal is, in one paragraph
Every G&M maintenance client gets a private token-based URL where every quarterly report we deliver for them lives. Reports include plugin update history with green-highlighted changes, WP core version, security findings, backup verification, theme updates, recommendations, broken links, and a structured analytics summary. Per-client logo and brand color, custom fiscal calendars, multi-site support, PDF download via browser print. This is a real differentiator versus generic WordPress maintenance providers and should be talked about in client-facing pitches as "one place where everything lives," not as "we built a portal."
Session notes
| File | Date | Topic |
|---|---|---|
| session-2026-02-05.md | 2026-02-05 | Other Updates tab, autosave after plugin pulls, dirty state indicator |
| session-2026-02-05-2.md | 2026-02-05 | (continuation) |
| session-2026-02-05-3.md | 2026-02-05 | (continuation) |
When to add notes here
- Major portal feature work (new tabs, new fields, new admin screens)
- Architectural decisions (data model changes, fiscal calendar shifts, auth changes)
- Deploy gotchas worth remembering across sessions
- New client-facing capabilities that affect how we pitch maintenance
For the actual quarterly maintenance work on a client site (running /maintenance, populating reports), session notes belong in the relevant client's project-notes folder, not here. This folder is for portal-app development specifically.