You will never touch a server. You build a page, you publish it to your playground, YT reads it and marks it up on the page itself, and YT ships it. This walks you through the three places your work can live, the one tool you will learn, and a short check at the end.
Every page you make lives in one of three places. Only the first one is yours to publish to.
A private space on Vercel. You publish drafts here yourself, as many as you like, all hidden from Google. Every quiz, calculator, and page starts its life here for review.
A private copy of the real site, so YT can see a page exactly as it will look once it is live. It runs on our own server, which you cannot reach.
The real website the whole world sees. Putting a page here is the last step, and it is always YT's hand on the button.
Staging and live both run on our own server, and you do not have a key to it. That is on purpose, not a slight. The playground on Vercel needs no key. You publish to it straight from your work, it costs nothing, and every page is hidden from search.
So the playground is where you make and test things. YT carries the approved page across to the real site. You focus on the making, she handles the shipping.
Hypothesis is a comment layer that sits on top of a live page. Instead of describing a change in Slack, like "make the third line shorter", YT highlights the exact words on the page and leaves a note right there. You open the same page, see her note beside the line she means, and fix it. No guessing which line.
Everyone reviewing works in one shared group, so you both see the same notes and the same replies on the page. That is the point: a reply you leave is a reply YT sees, right under her comment, not something lost in a separate view. You join the group once, from an invite link YT sends you, and stay logged in to Hypothesis while you review.
The shared group only helps if the replies come back. So the rule is simple: every comment YT leaves gets a visible reply from you, so she always knows where each one stands. Two kinds of reply, and both take seconds.
Hypothesis has no "resolved" button, so the reply is the signal. This is what saves the back-and-forth in Slack: YT reads your reply under her own comment and knows it is either done or being talked about. Nothing sits unanswered.
Before you say a review round is done, every comment on the page has a reply under it. A done mark when you fixed it, a real answer when it needs discussion or is staying. Never leave one on read.
Only YT publishes to reviewmyemails.com. Not you, not anyone else. If a page is going live, it goes through her.
One ticket, one owner at a time. The claim comes before the work, not after it.
Here is why this rule is here. One night, two of us built the very same holiday banners at the same time, neither knowing the other was on them. Both of us finished. One finished set went straight in the bin. Hours of good work gone, only because nobody knew it was already taken.
A claim is what stops that. The moment a ticket says doing with a name against it, everyone else can see it is spoken for and leaves it alone.
Before you start a ticket, check that its row says doing with your name on it. If it is already claimed by someone else, do not build it alongside them, check with them first.
The same discipline closes the loop at the other end. When your ticket's PR is merged and the work is done, your runner nudges this chat to wrap up, capture anything worth keeping, hand the board update to the Tickets chat, then archive the chat so a finished task never lingers open. Claim it to start, archive it to finish.
Seven questions. Tap an answer to see if it is right and why. Nothing is saved, this is just for you.