Three Next.js templates just went live under WHH Treasures.
• ClientNest — agency client portal
• InspectStack — offline field inspections
• QuestCite — cited security questionnaires
Demos + licenses: https://t.co/OLeTXf0MUH
Source you host. Checkout on Lemon.
QuestCite distinction I keep writing down:
OCR confidence ≠ citation confidence.
The extractor can be 97% sure of the glyphs and still land on the wrong clause. Show both numbers — or don’t dress a fuzzy span as a hard cite.
InspectStack sync tip:
when the tower comes back, don’t FIFO the upload queue by accident.
A closed job’s photos can wait. An open defect with the client still on site should jump the line.
Oldest-first felt fair. Priority-by-job-status actually matches the field.
@Warkanum Same problem space as field inspections — the hard part is usually the sync story after capture, not the camera. Curious how you surface pending vs uploaded to the tech.
sson from another stuck thread:
“waiting on client” with no due date is just an open tab forever.
We used to mark threads Waiting and feel like progress. Eleven days later nobody had a clock to beat. The portal looked busy. Nothing moved.
So now every approval request gets a due date the day it’s sent. Miss it once → nudge. Miss it twice → escalate to the named owner, not the whole Slack channel.
Ugly deadline. Honest pipeline.
Starting today, I won’t use Meta models, review them, or talk about any of their models or tools until @alexandr_wang ends this disgrace and apologizes to everyone for the moral depravity of what he’s doing.
QuestCite footgun from today-ish:
citation points at “page 9.”
Mobile reflow turns page 9 into page 11. Same PDF bytes, different pagination.
If the cite can’t survive a viewport change, store a content hash + anchor — not a page number alone.