What should every restaurant keep written down?

Domains, hosting, CMS, booking, Quiteful, who can change allergens, and where form mail goes.

Is a password manager enough?

Necessary, not sufficient. You still need the map of what each login is for and what not to click.

where's README

processMar 31, 2026by LemonOctopus

If only one person knows where the menu is published, you do not have a website. You have a single point of failure.

People leave. Freelancers go quiet. The site should not go with them.

Write the boring map. DNS, hosting, analytics, booking, menu platform, the Instagram bio link that still points at the old PDF.

Record the diner path and the staff path. How to 86 a dish. How to close for a private hire. How to revert a bad publish.

Store it where the GM can find it, not only in a developer's head. Handover is cheaper than a vanished admin email.

Documentation is operations. Treat it like a recipe, not a novel.

What should every restaurant keep written down?: Domains, hosting, CMS, booking, Quiteful, who can change allergens, and where form mail goes.
Is a password manager enough?: Necessary, not sufficient. You still need the map of what each login is for and what not to click.