A user guide for every page

A route you cannot explain is one you cannot trust: a guide now tells what every page does, where the data come from and where the limits lie.

Saily WR does a lot behind a few buttons, and a sailor deserves to know what a route rests on before following it. Why does a model stop short of the destination? What does the minimum depth really protect from? Where does the wind come from?

The Documentation page explains it all, page by page: a quick start in three steps, then the boat and routing pages, how to read the result, the data the routes rest on and how a route is computed. From the routing and boat pages, the help leads straight to the right chapter.

The user guide's first page: its table of contents beside the overview. — The guide, a chapter per page, and one for questions, from the quick start to how a route is computed.

It reaches as far as the app does: every setting and what it changes, the sources of the wind, the current and the depths with how fine each one is and how far ahead it sees, the answers to the questions a route raises, and a glossary of the words of routing, from isochrone to TWA.

Say a route to an anchorage at the head of a bay stops short on every model. The guide's questions tell why that happens: the minimum depth or the coastal margin closes the bay off. Bring the depth down to your draught and its margin, compute again, and the route can get in: the answer is a page away, not a guess.

Above all, it tells the limits plainly: the route follows the coastline and the depths, not the buoys, the restricted areas, the traffic separation schemes or the height of the tide, and it replaces neither official charts nor keeping watch. A decision aid, not an autopilot.