docs: update references to old a32nx repo

pluce · Valastiri · web-flow · commit 4aa945283b43 · 2023-08-03T18:13:00.000Z
* docs: update references to old a32nx repo

* Update docs/dev-corner/dev-guide/setup-environment.md

Co-authored-by: Val &lt;reyes.nico@gmail.com&gt;

* Update docs/dev-corner/development-projects/index.md

Co-authored-by: Val &lt;reyes.nico@gmail.com&gt;

* Update docs/dev-corner/dev-guide/specific/flypad-translations.md

Co-authored-by: Val &lt;reyes.nico@gmail.com&gt;

---------

Co-authored-by: Val &lt;reyes.nico@gmail.com&gt;
diff --git a/README.md b/README.md
@@ -23,7 +23,7 @@ Note: Please be aware that sub-directories are present in the parent directories
 
 ## A32NX Project
 
-[FlyByWire Simulations A32NX Repo](https://github.com/flybywiresim/a32nx)
+[FlyByWire Simulations Aircraft Repo](https://github.com/flybywiresim/aircraft)
 
 [https://flybywiresim.com/](https://flybywiresim.com/)
 
diff --git a/archive/exp.md b/archive/exp.md
@@ -19,7 +19,7 @@ Currently, experimental is geared toward testing the initial version of VNAV wit
 
 We are testing the new FWS (Flight Warning System) which replaces the previous provisional system. 
 See technical details in the respective 
-[GitHub Pull Request #4872](https://github.com/flybywiresim/a32nx/pull/4872){target=new}.
+[GitHub Pull Request #4872](https://github.com/flybywiresim/aircraft/pull/4872){target=new}.
 
 ![fws-init-ecam](../docs/pilots-corner/assets/beginner-guide/starting-aircraft/fws-init-ecam.png){loading=lazy width=50%}
 
diff --git a/docs/dev-corner/dev-guide/contribute.md b/docs/dev-corner/dev-guide/contribute.md
@@ -18,13 +18,13 @@ As contributors and maintainers of this project, we pledge to respect all people
 
 Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues and other contributions that are not aligned to this Code of Conduct.
 
-Make sure to read our [Code of Conduct](https://github.com/flybywiresim/a32nx/blob/master/CODE_OF_CONDUCT.md)
+Make sure to read our [Code of Conduct](https://github.com/flybywiresim/aircraft/blob/master/CODE_OF_CONDUCT.md)
 
 ## Pull Requests
 
 We welcome pull requests with fixes and improvements to the project.
 
-If you wish to add a new feature or you spot a bug that you wish to fix, **please open an issue for it first** on the [A32NX issue tracker](https://github.com/flybywiresim/a32nx/issues).
+If you wish to add a new feature or you spot a bug that you wish to fix, **please open an issue for it first** on the [FBW Aircraft issue tracker](https://github.com/flybywiresim/aircraft/issues).
 
 The work-flow for submitting a new pull request is designed to be simple, but also to ensure consistency from **all** contributors:
 
@@ -49,7 +49,7 @@ Please help other contributors to the project wherever you can, as people all st
 
 ## Finding tasks
 
-The best place to look for possible things where you could contribute is the A32NX GitHub repository's [Issues List](https://github.com/flybywiresim/a32nx/issues){target=new}.
+The best place to look for possible things where you could contribute is the FBW Aircraft GitHub repository's [Issues List](https://github.com/flybywiresim/aircraft/issues){target=new}.
 There you can find open bug reports or feature requests from users or other developers.
 
 ## Issues
diff --git a/docs/dev-corner/dev-guide/resources.md b/docs/dev-corner/dev-guide/resources.md
@@ -6,13 +6,13 @@ On this page, you will find all the necessary resources, links, and documentatio
 
 The main GitHub repository for the A32NX aircraft is:
 
-**[https://github.com/flybywiresim/a32nx](https://github.com/flybywiresim/a32nx){target=new}**
+**[https://github.com/flybywiresim/aircraft](https://github.com/flybywiresim/aircraft){target=new}**
 
 The Development version of the FlyByWire A32NX is done in the master branch. Whenever something is merged into the master branch, an automatic build process builds the newest 
 Development version and uploads it to our CDN, so users can download the latest Development version via the FlyByWire Installer. We have a very strict development, review and 
 QA process for for this version.
 
-The Stable version is a snapshot (in git terms, a [Tag](https://github.com/flybywiresim/a32nx/tags){target=new}) of the development branch.
+The Stable version is a snapshot (in git terms, a [Tag](https://github.com/flybywiresim/aircraft/tags){target=new}) of the development branch.
 
 The FlyByWire project has other repositories for subprojects like api, msfs-rs, installer, website, docs, etc. Find them [here](https://github.com/orgs/flybywiresim/repositories){target=new}.
 
diff --git a/docs/dev-corner/dev-guide/setup-environment.md b/docs/dev-corner/dev-guide/setup-environment.md
@@ -26,29 +26,29 @@ Most of our team works with either Visual Studio Code or IntelliJ IDEA-based IDE
 
 ## Getting the source code
 
-To work on the A32NX project, you need to create a fork ( [GitHub fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo){target=new)}) of the [a32nx repository](https://github.com/flybywiresim/a32nx).
+To work on the A32NX project, you need to create a fork ( [GitHub fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo){target=new)}) of the [aircraft repository](https://github.com/flybywiresim/aircraft).
 
 Clone this fork to your local environment. You can use the command line git or a UI-based git to do this. On the command line, go to your projects folder and clone it into that folder.
 
 ```
-git clone https://github.com/flybywiresim/a32nx.git
+git clone https://github.com/flybywiresim/aircraft.git
 ```
 
-You now have a copy of the a32nx repository on your local machine to review and change the source code.
+You now have a copy of the aircraft repository on your local machine to review and change the source code. The subfolder `./fbw-a320nx` contains the A32NX source code.
 
 ## Compiling the source
 
 To compile the source code into a package you can install into the Microsoft Flight Simulator Community folder, we have prepared a few scripts you need to run, which in turn use the Docker container mentioned above to compile the aircraft add-on.
 
 
 ```powershell title="PowerShell or Cmd Prompt"
-cd a32nx
+cd aircraft
 .\scripts\dev-env\run.cmd ./scripts/setup.sh
 .\scripts\dev-env\run.cmd ./scripts/build.sh
 ```
 
 ```bash title="git bash or other *nix shells on Windows"
-cd a32nx
+cd aircraft
 ./scripts/dev-env/run.cmd ./scripts/setup.sh
 ./scripts/dev-env/run.cmd ./scripts/build.sh
 ```
@@ -85,7 +85,7 @@ mklink /J [MSFS Community folder\flybywire-aircraft-a320-neo] [Project folder pa
 
 Example:
 ```
-mklink /J C:\Users\USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Community\flybywire-aircraft-a320-neo C:\Users\USERNAME\IdeaProjects\a32nx\fbw-a32nx\out\flybywire-aircraft-a320-neo
+mklink /J C:\Users\USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Community\flybywire-aircraft-a320-neo C:\Users\USERNAME\IdeaProjects\aircraft\fbw-a32nx\out\flybywire-aircraft-a320-neo
 ```
 
 If this works, you'll receive the response:
diff --git a/docs/dev-corner/dev-guide/specific/flypad-dev.md b/docs/dev-corner/dev-guide/specific/flypad-dev.md
@@ -33,7 +33,7 @@ VCockpit16 - EFB_TEMPLATE [coui://html_UI/Pages/VCockpit/Core/VCockpit.html]
 Now you're set up with your own fork, which you can reload instantly and test in MSFS, you're ready to get started making changes. When getting started, it's a good idea to spend some time looking around the project and wrapping your head around the structure.
 
 - You'll find the main EFB content under ` src/instruments/src/EFB ` of your GitHub fork, try making small changes at first to test, such as changing the color of an icon, or changing a few words to make sure the reloading is working.
-- Take a look at previous commits made to the flyPad on the [A32NX GitHub Repository](https://github.com/flybywiresim/a32nx/commits/master){target=new} and see what changes were made to get the desired result.
+- Take a look at previous commits made to the flyPad on the [FBW Aircraft GitHub Repository](https://github.com/flybywiresim/aircraft/commits/master){target=new} and see what changes were made to get the desired result.
 
 !!!info "Top tip!"
     When working on your project, make sure to reload the flyPad and test regularly to catch issues as soon as they happen.
diff --git a/docs/dev-corner/dev-guide/specific/flypad-translations.md b/docs/dev-corner/dev-guide/specific/flypad-translations.md
@@ -1,6 +1,6 @@
 # flyPadOS 3 Localization Process
 
-This page is pulled externally from the A32NX repository and describes the processes involved with adding features to the EFB and sourcing translations.
+This page is pulled externally from the FBW Aircraft repository and describes the processes involved with adding features to the EFB and sourcing translations.
 
 We have partnered with Localazy, who offer top-notch software localization services, bringing multi-language support to our EFB, enhancing the user experience.
 
@@ -11,4 +11,4 @@ com&utm_medium=sponsored-referral&utm_campaign=partnerships&utm_content=footer-l
 
 ---
 
-{{ external_markdown('https://raw.githubusercontent.com/flybywiresim/a32nx/master/fbw-a32nx/src/localization/README.md', '') }}
+{{ external_markdown('https://raw.githubusercontent.com/flybywiresim/aircraft/master/fbw-a32nx/src/localization/README.md', '') }}
diff --git a/docs/dev-corner/development-projects/ace.md b/docs/dev-corner/development-projects/ace.md
@@ -35,7 +35,7 @@ The MSFS CoherentGT engine API is emulated in `ace`, including the `call`, `trig
 3. Run ace with `npm start`
 4. After running the program, select New Project and choose the locations of all your folders. (see [below] (#example-config))
 5. Add a Web Instrument to localhost:9696 (right-click on the project canvas)
-6. Open a new terminal and go to your a32nx clone folder and run: `npm run serve:efb`
+6. Open a new terminal and go to your `aircaft` clone folder and run: `npm run serve:efb`
      This allows to see any changes to the instrument's code nearly instantaneously. 
 
 To interact with the EFB via mouse, you need to click enter to turn on interactive mode.
diff --git a/docs/dev-corner/development-projects/index.md b/docs/dev-corner/development-projects/index.md
@@ -11,7 +11,7 @@ FlyByWire Simulations consists of several projects to allow efficient and quick
 
 | Projects                                                                           | Description                                                                                                                                                                                               |
 |:-----------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [A32NX](https://github.com/flybywiresim/a32nx){target=new}                         | Main project where the actual FlyByWire A32NX is developed                                                                                                                                                |
+| [Aircraft](https://github.com/flybywiresim/aircraft){target=new}                         | Main project where the FlyByWire A32NX and A380X are developed                                                                                                                                                |
 | [Installer](https://github.com/flybywiresim/installer){target=new}                 | Project for developing and improving the FlyByWire Installer.                                                                                                                                             |
 | [Docs](documentation.md)                                                           | Documentation project to manage and improve documentation for our users. This includes documentation about the A32NX, general sim-pilot documentation, and documentation about development for the A32NX. |
 | [Discord Bot](discord-bot.md)                                                      | FlyByWire Simulations custom bot commands list and changelog. Provides a quick overview of available support commands and changes to bot development.                                                     |
diff --git a/docs/dev-corner/index.md b/docs/dev-corner/index.md
@@ -9,7 +9,7 @@ description: The Development Corner is dedicated to providing information about
 
 This section of the FlyByWire Documentation is dedicated to the development aspects of the A32NX add-on. It is aimed at developers, contributors, or anyone who would like to start contributing to the project.
 
-[:fontawesome-brands-github:{: .github } **GitHub Contributing.md**](https://github.com/flybywiresim/a32nx/blob/master/.github/Contributing.md){ .md-button target=new}
+[:fontawesome-brands-github:{: .github } **GitHub Contributing.md**](https://github.com/flybywiresim/aircraft/blob/master/.github/Contributing.md){ .md-button target=new}
 
 ## Quick Links
 
diff --git a/docs/dev-corner/qa-process.md b/docs/dev-corner/qa-process.md
@@ -16,7 +16,7 @@ To QA test for FlyByWire, you need the following prerequisites:
 
 - Having read and understood this page!
 - Microsoft Flight Simulator (PC)
-- GitHub Account and access to our [Pull Requests](https://github.com/flybywiresim/a32nx/pulls){target=new}
+- GitHub Account and access to our [Pull Requests](https://github.com/flybywiresim/aircraft/pulls){target=new}
 - Discord Account and joined our server [FlyByWire Simulations](https://discord.gg/flybywire)
 - A QA Trainee or QA Tester Discord role
 
@@ -40,7 +40,7 @@ To manage this process, we use the GitHub Project feature.
 
 This is a simple Kanban board where items move from the left to the right. For QA tests, the third column is relevant ("QA Team Review: Ready to Test")
 
-![QA Project Board on GitHub](assets/qa-process/qa-board.png "QA Project Board on GitHub"){loading=lazy}<br/>[QA Project Board on GitHub](https://github.com/flybywiresim/a32nx/projects/4){target=new}
+![QA Project Board on GitHub](assets/qa-process/qa-board.png "QA Project Board on GitHub"){loading=lazy}<br/>[QA Project Board on GitHub](https://github.com/flybywiresim/aircraft/projects/4){target=new}
 
 If you have gotten a grasp on the above instructions, pick a PR to test from the list.
 
@@ -109,7 +109,7 @@ Typically, it is ok to keep your Navigraph data installed.
 
 Read the test instructions of the PR carefully. Focus only on what is requested and part of this PR. Do not bloat your reports with many additional observations.
 
-If you find additional issues which are not part of the PR, reproduce and test them with the latest Development version and then create a [GitHub Issue](https://github.com/flybywiresim/a32nx/issues) for them.
+If you find additional issues which are not part of the PR, reproduce and test them with the latest Development version and then create a [GitHub Issue](https://github.com/flybywiresim/aircraft/issues) for them.
 
 ### Ask on Discord
 
@@ -164,7 +164,7 @@ Media:
 !!! tip "Tip: Look at closed PRs"
     To better understand what a report should look like, you can look at closed PRs on GitHub to see how others approach this.
 
-    Link to Closed PR list: [Closed PRs](https://github.com/flybywiresim/a32nx/pulls?q=is%3Apr+is%3Aclosed){target=new}
+    Link to Closed PR list: [Closed PRs](https://github.com/flybywiresim/aircraft/pulls?q=is%3Apr+is%3Aclosed){target=new}
 
 !!! tip "Tip: Using GitHub Save for Template"
     We suggest using the "Saved Replies" feature of GitHub for the QA Template. You can set them up as follows:
diff --git a/docs/dev-corner/texture-changes.md b/docs/dev-corner/texture-changes.md
@@ -14,7 +14,7 @@ If you are the author of an affected livery, please reference the following:
 - For convenience, here is a copy of the [new sharklet UV map](assets/a32nx-dev/sharklet_uv_4k.png){target=new} that can be added as a layer in your workflow. The decals should be painted un-mirrored.
 
 !!! warning ""
-    For further context, you can review [pull request #5490](https://github.com/flybywiresim/a32nx/pull/5490){target=new} on our GitHub if necessary.
+    For further context, you can review [pull request #5490](https://github.com/flybywiresim/aircraft/pull/5490){target=new} on our GitHub if necessary.
 
 ## Registration Decal
 
@@ -34,7 +34,7 @@ If you are the author of a livery that has textured wheels, with text or anythin
 - No action is required. The current wheel texture will appear correct on the right main gear wheel.
 
 !!! warning ""
-    For further context, you can review [pull request #6931](https://github.com/flybywiresim/a32nx/pull/6931) on our GitHub if necessary.
+    For further context, you can review [pull request #6931](https://github.com/flybywiresim/aircraft/pull/6931) on our GitHub if necessary.
 
 ## Cargo Hinges
 
diff --git a/docs/fbw-a32nx/a32nx-api/a32nx-flightdeck-api.md b/docs/fbw-a32nx/a32nx-api/a32nx-flightdeck-api.md
@@ -15,8 +15,8 @@ hide:
 
 Find the complete list of Custom Event and Custom LVARS of the A32NX:
 
-- [Custom LVARs](https://github.com/flybywiresim/a32nx/blob/master/fbw-a32nx/docs/a320-simvars.md){target=new}
-- [Custom Events](https://github.com/flybywiresim/a32nx/blob/master/fbw-a32nx/docs/a320-events.md){target=new}
+- [Custom LVARs](https://github.com/flybywiresim/aircraft/blob/master/fbw-a32nx/docs/a320-simvars.md){target=new}
+- [Custom Events](https://github.com/flybywiresim/aircraft/blob/master/fbw-a32nx/docs/a320-events.md){target=new}
 
 !!! note "The order of the panels below is roughly done after the standard cold & dark setup procedure."
 
@@ -212,7 +212,7 @@ Flight Deck: [APU Panel](../../pilots-corner/a32nx-briefing/flight-deck/ovhd/apu
 | START     | A32NX_OVHD_APU_START_PB_IS_ON         | 0&#124;1 | R/W        | Custom LVAR |        |
 |           | A32NX_OVHD_APU_START_PB_IS_AVAILABLE  | 0&#124;1 | R          | Custom LVAR |        |
 
-!!! note "Search for APU in our [list for all Custom LVARS](https://github.com/flybywiresim/a32nx/blob/master/fbw-a32nx/docs/a320-simvars.md){target=new} for further variables."
+!!! note "Search for APU in our [list for all Custom LVARS](https://github.com/flybywiresim/aircraft/blob/master/fbw-a32nx/docs/a320-simvars.md){target=new} for further variables."
 
 ### RCDR Panel
 
diff --git a/docs/fbw-a32nx/a32nx-api/lvars-events.md b/docs/fbw-a32nx/a32nx-api/lvars-events.md
@@ -2,14 +2,14 @@
 
 Flight-Deck API Documentation: [Flight-Deck API](a32nx-flightdeck-api.md)
 
-In addition to the above documentation, all custom variables and custom events are documented by our developers on our project's GitHub: [:fontawesome-brands-github:{: .github } -  **Docs section on GitHub**](https://github.com/flybywiresim/a32nx/tree/master/fbw-a32nx/docs){target=new}
+In addition to the above documentation, all custom variables and custom events are documented by our developers on our project's GitHub: [:fontawesome-brands-github:{: .github } -  **Docs section on GitHub**](https://github.com/flybywiresim/aircraft/tree/master/fbw-a32nx/docs){target=new}
 
 ## Docs:
 
-- [Custom LVARs](https://github.com/flybywiresim/a32nx/blob/master/fbw-a32nx/docs/a320-simvars.md){target=new}
-- [Custom Events](https://github.com/flybywiresim/a32nx/blob/master/fbw-a32nx/docs/a320-events.md){target=new}
+- [Custom LVARs](https://github.com/flybywiresim/aircraft/blob/master/fbw-a32nx/docs/a320-simvars.md){target=new}
+- [Custom Events](https://github.com/flybywiresim/aircraft/blob/master/fbw-a32nx/docs/a320-events.md){target=new}
 
 ## Templates
 
-- **SPAD.neXt:** [flybywire-aircraft-a320-neo.xml](https://github.com/flybywiresim/a32nx/tree/master/fbw-a32nx/docs/SPAD.neXt){target=new}
-- **FSUIPC:** [flybywire-aircraft-a320-neo.evt](https://github.com/flybywiresim/a32nx/tree/master/fbw-a32nx/docs/FSUIPC){target=new}
+- **SPAD.neXt:** [flybywire-aircraft-a320-neo.xml](https://github.com/flybywiresim/aircraft/tree/master/fbw-a32nx/docs/SPAD.neXt){target=new}
+- **FSUIPC:** [flybywire-aircraft-a320-neo.evt](https://github.com/flybywiresim/aircraft/tree/master/fbw-a32nx/docs/FSUIPC){target=new}
diff --git a/docs/fbw-a32nx/faq.md b/docs/fbw-a32nx/faq.md
@@ -29,7 +29,7 @@
     No, it is a completely free and open-source aircraft.
 
 ??? info "Q: How do we report bugs?"
-    Report bugs to us in the [Discord server](https://discord.gg/flybywire){target=new}, under the `#a32nx-support` channel, or by creating a [GitHub issue](https://github.com/flybywiresim/a32nx/issues/new/choose){target=new}.
+    Report bugs to us in the [Discord server](https://discord.gg/flybywire){target=new}, under the `#a32nx-support` channel, or by creating a [GitHub issue](https://github.com/flybywiresim/aircraft/issues/new/choose){target=new}.
 
     Just make sure to search for existing issues first before creating a new one.
 
diff --git a/docs/fbw-a32nx/fbw-versions.md b/docs/fbw-a32nx/fbw-versions.md
diff --git a/docs/fbw-a32nx/feature-guides/autopilot-fbw.md b/docs/fbw-a32nx/feature-guides/autopilot-fbw.md
diff --git a/docs/fbw-a32nx/installation.md b/docs/fbw-a32nx/installation.md
diff --git a/docs/fbw-a32nx/support/index.md b/docs/fbw-a32nx/support/index.md
diff --git a/docs/fbw-a32nx/support/reported-issues.md b/docs/fbw-a32nx/support/reported-issues.md
diff --git a/mkdocs.yml b/mkdocs.yml
