Internal is not storefront
The handbook is for team and owner use. It is noindexed and must not become public promise copy.
operational handbook
OmenHall team handbook
An internal handbook for the future team: roles, day one, code, content, payment, support, privacy, emergency, and release ritual rules. Here OmenHall learns to hand over keys without chaos in the halls.
ownerteamsafetypaymentstechnicalcontentemergency
One owner per door
If everyone owns a task, no one guards it. Every operation needs an owner, done criteria, and escalation path.
Do not treat with fear
Support, content, and product tests must not amplify user anxiety for payment or retention.
Change requires rollback
Every payment, route, email, data, and SEO change needs a clear way back.
handbook doors
How to work on the site without dropping the chandelier
Roles and ownershipWho owns what: owner, support, editor, technical owner, privacy owner, and growth owner.Day-one handbookWhat a new helper must read and check on day one before touching the site.Operating checklistsUnified checklist rituals before deploy, publishing, payment, email, and customer replies.Code change rulesWhat cannot change without typecheck, route audit, security, and rollback notes.Content change rulesHow to change pages, promises, metadata, internal noindex sections, and tone.Payment change rulesRules for Stripe, prices, checkout, success/cancel pages, refunds, and test purchases.Support response rulesHow to reply to customers without future promises, fear, pressure, or extra data.Privacy and data rulesWhat can be stored, what must not be forwarded, and how to handle deletion/export/consent requests.Emergency playbookWhat to do during broken payments, data exposure, email incidents, downtime, or a bad deploy.Release ritualSmall pre-merge ritual: what was checked, how to rollback, who to notify, where to record the decision.