Write the build commands as the form that works without a second install Every task on the wiki was written as `task <name>`, which only runs for someone who installed Task separately. The Wails CLI is already a hard prerequisite and has Task built in, so `wails3 task <name>` works the moment `wails3` does - the project's own preconditions print it that way too. Task drops to an optional prerequisite that just lets you shorten the prefix, and the two pages say so once each rather than qualifying every command.
Document the Linux build, and cross-compiling both Unix targets from Windows Building from source covered the Windows path; Linux needed its own page for the parts that differ. The one that costs the most time is the GTK version: Wails v3 links gtk4 and webkitgtk-6.0, and the scaffolding's gtk3/webkit2gtk-4.1 package lists send people to install development headers the build never reads. Also written down: that DevTools exist only outside -tags production, that the desktop entry is maintained rather than generated because the generated one carries no StartupWMClass, that pkill needs the 15-character truncation of the process name, and where the data root and logs actually land. Cross-compilation is one section at the end rather than its own page, because from Windows both Unix targets are the same wails-cross image with a different argument, and both come with the same caveat - a cross-built macOS binary is not a bundle and cannot be signed off-platform.