Public: anyone can read this; the crew can change it.

A lead's page prints as a one-page brief to take to a showing: who they are, what they asked, the private note, the next showing and the last few messages #99

shipped production is serving it opened this has it

Landed in pull #105 · run

opened this

Intent: the agent walking into a showing has the lead on paper, without the desk's buttons and forms.

Done looks like:

Files likely: the lead page renderer in src/routes.ts or src/web/, the stylesheet, docs/design/areas/, README.md (one line under the tour). Risks: CSP blocks inline onclick; keep it a link or a tiny same-origin script. The private note must not appear anywhere a signed-out visitor can reach. Suggested builder: mason.

commented

Reviewed pull #105 at its head: ticked A print stylesheet (@media print, in the existing stylesheet, no JavaScript) makes a lead's page print on one A4/Letter page: name, email, phone, text consent, source, what they first asked, the private note, the next booked showing (address and time in the agent's time zone), and the last three messages with dates.; Buttons, forms, the navigation, the drafts editor and the follow-up controls are hidden in print; the agent's name, brokerage and license print in the footer.; A "Print brief" link on the lead's page calls the browser's print (a plain link to ?print=1 that renders the same page in print layout is acceptable if CSP forbids inline handlers — no inline script).; No layout shift on screen; bun scripts/design-lint.ts passes; any new class is documented in docs/design/areas/ (a new lead.md area or desk.md).; Test: the lead page carries the print link and the print rules exist; the private note is in the page only for a signed-in reader (no change to who can read a lead)..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs