Skip to main content
Every page here is one of three kinds, and the kind tells you what you will get before you read a word. A page never mixes kinds. If a how-to starts explaining history, that history belongs on the explanation page, with a link. This borrows from a framework called Diátaxis, which most of the good documentation you have read follows without saying so.

Three doors into the same building

The handbook is arranged three ways because you arrive with three different questions.
  • “How does X work?” → the Handbook tab. Chapters run in business order. Each chapter opens with its explanation page, then lists its how-tos.
  • “What does Zoho own?” → the Systems tab. One page per system, plus the map.
  • “What does this status mean?” → the Reference tab. Tables only.
The three tabs are cross-linked so that you can jump sideways. Every page ends with a Related section that points to the pages next to it in the other two tabs. Every process page also carries a line near the top that lists the systems it touches, and each of those is a link.

Names

The handbook uses the names people say, not the names the databases use. It says customer, not contact. It says work order, not the code name. When you need the code name, the Names page maps every human name to its Zoho and Supabase name in one table. A check stops code names from creeping into other pages.