Make new docs live

Update README and change URLs for handoff to inavflight.github.io

Author: sensei-hacker

README.md

@@ -17,16 +17,27 @@ To build and run the docs locally, install npm on your system and follow the Doc
 - Make sure all packages are installed with `npm install`.
 - Run the dev server with `npm run start`.
 
-The temporary documentation can be accessed at this URL: https://www.spiffygoose.com/inavdocs/
+Documentation can be accessed at this URL: https://inavflight.github.io/
 
-## Versioning Scheme
+## For Contributors
+
+### Versioning Scheme
 
 The website utilizes Docusaurus's versioning feature to keep track of major changes to the firmware.
-The current version is the active stable release in the main `./docs` directory that is intended to be continually updated with minor updates until the next version. 
-Upon the release of the next stable version, the current version will be archived (versioned) into its own directory using `npm run docusaurus docs:version x.y.z`
-Lastly, the next current version's label will updated in `docusaurus.config.ts`.
+The current version is the active stable release in `/versioned_docs/version-x.x.x` directory that has been frozen with no further updates. 
+Upon the release of the next stable version, it will be created into its own, new directory using `npm run docusaurus docs:version x.y.z`
+
+### Image and Media References
+As per the latest Docusaurus file structure, please place new static images in the `/static/img/` directory in an organized fashion. 
+When referring to an image in a markdown file, please use absolute paths according to the following markdown syntax: `![Image Info](/img/FolderName/NameOfImage.jpg)`
+
+### Linking to Pages
+When linking to local pages, please do not use http urls or relative paths to link to other markdown documents that are part of the docusaurus site.
+For easier maintenance and organization, use relative paths starting from the root directory eg: `../quickstart/Name_of_markdown.md` if not in the `quickstart` directory, which exists one level above.
+Autocomplete on VS Code should find the directories automatically. 
+Linking to headings within the document work as well by using `#` following the filename.
 
 ## Plugins Used
 
-* The search plugin used is docusaurus-lunr-search: https://github.com/praveenn77/docusaurus-lunr-search
+* Search plugin: https://github.com/easyops-cn/docusaurus-search-local
 * Image zoom plugin: https://github.com/gabrielcsapo/docusaurus-plugin-image-zoom

docs/advanced/AAT-Automatic-Antenna-Tracker.md

@@ -0,0 +1,55 @@
+---
+title: Automatic Antenna Tracker
+---
+
+## Introduction
+
+Since release 3.0, INAV directly supports embedded video telemetry data to drive the VirtualPilot Sentinel antenna tracker.
+
+This enables the use of directional higher gain antennas to maintain higher quality video in all directions, provide the ability to use lower video transmission power or increase the maximum reception distance over traditional omnidirectional antennas. The AAT provides the benefit of maintaining a more accurate direction over manually mounted antennas without the concern of the aircraft moving outside of the antenna’s dominant reception area.
+
+***
+## Configuring - iNAV 3.0 onwards (embedded support) 
+* Requires minimum of INAV 3.0 and fonts installed
+* Enable AAT telemetry in the cli: set osd_telemetry = ON
+
+## Configuring - iNAV earlier versions
+* Check content at the link here: [INAV AAT for earlier versions](https://github.com/aat-sentinel/Documentation/blob/main/Sentinel%20AAT%20lite%20User%20Guide.pdf)
+
+## Testing 
+As telemetry data is not normally visible, the telemetry data can be viewed on the OSD using a cli command:
+* Enable AAT telemetry with second test line in the cli: set osd_telemetry = TEST
+* Remember to change it back when finished: set osd_telemetry = ON (FC restart required)
+
+***
+## Description of operation 
+* iNAV knows its home launch position, current position and altitude
+* iNAV can calculate the pan and tilt information required by the antenna tracker
+* The data is sent using video telemetry over an analogue signal
+* The video telemetry is sent on OSD row 0 with only pixel line 0 used
+* 30 bits of information are sent in each video frame which includes tilt angle, pan angle and error validation check
+* Two font characters are used to represent a binary 0 or 1
+
+Positives of using this telemetry method:
+* Simple and reliable
+* No hardware modules or extra wiring on aircraft
+* Supports all RC TX - not limited to TX with telemetry
+* Does not require unreliable bluetooth / wifi connections to tracker
+* Not impacted by 2.4G RC /Video 
+* Ultra-fast position updating – up to 30 hz
+* Low size packet means higher tracking success rate in poor signal conditions
+
+Negatives of using this telemetry method:
+* Tracking data may be recorded by some DVR. Not usually visible in goggles / monitor
+* The first row of OSD display becomes unavailable for OSD. However, this row is not usually fully visible
+* This does not use tracker GPS location – so cannot be used in a moving vehicle
+
+In the visualisation video below, you can see how the telemetry data is sent. This is a test mode as it is not usually visible in FPV goggles / recordings, however notice how the real telemetry line on pixel row zero is not visible.
+
+[![Telemetry visualisation capture](https://img.youtube.com/vi/FMLUvc-tX4E/0.jpg)](https://youtu.be/FMLUvc-tX4E?t=20)
+
+***
+## Sentinel AAT for use with iNAV 
+Further information on the Sentinel AAT is available by clicking on the image:
+
+[![Sentinel AAT](https://static.rcgroups.net/forums/attachments/2/6/9/6/2/5/a14859253-253-TrackersRCG.png)](https://www.rcgroups.com/forums/showthread.php?3815901-New-product-low-cost-antenna-tracker-for-iNav-Betaflight-Ardupilot-KISS-etc)