About

About these docs

Scope, audience, and structure of the public Aerolync documentation.

Last updated 2026-03-28

Who this documentation is for

These pages are written for Aerolync users. Some pages are aimed at platform users, while others are aimed at Pilot App users.

Why the navigation is module-based

Users usually approach Aerolync by product area first and task second. The navigation reflects that. Platform content is grouped by module. Pilot App content is grouped by the screens users work in every day.

How platform and app documentation differ

  • Platform pages explain operational context and how modules influence each other.
  • Pilot App pages explain the app workflow itself and stay intentionally simple.
  • When the same process spans both products, the platform page is where the cross-product explanation lives.

What happens next

The structure is intentionally consistent:

  1. start with an overview page
  2. add focused pages for the workflows users perform most often
  3. keep the language practical and non-technical