diff --git a/docs/TODO_README.md b/docs/TODO_README.md index 335ba243b..cc1dbd646 100644 --- a/docs/TODO_README.md +++ b/docs/TODO_README.md @@ -133,7 +133,7 @@ is good enough for now but might be improved in the future. - [ ] Best Practices TODO - [ ] Systems Development TODO - [ ] Instrument Development TODO - - [ ] flyPad Development TODO + - [ ] flyPad Development TODO - page exists but needs update - [X] [Specific](dev-corner/dev-guide/specific/index.md) - [X] [Overview](dev-corner/dev-guide/specific/index.md) - [X] [Instruments Build Guide](dev-corner/dev-guide/specific/instruments-build-guide) diff --git a/docs/dev-corner/dev-guide/contribute.md b/docs/dev-corner/dev-guide/contribute.md index 57eaa59e0..e07d56c45 100644 --- a/docs/dev-corner/dev-guide/contribute.md +++ b/docs/dev-corner/dev-guide/contribute.md @@ -61,7 +61,8 @@ review and accept. Large PRs with a small error will prevent the entire PR from ## Helping others Please help other contributors to the project wherever you can, as people all start somewhere. If you require assistance -or wish to provide assistance, you can ask/answer questions on the [#dev-support](https://discord.gg/v3jAxJpwZm){target=new} channel on discord. +or wish to provide assistance, you can ask/answer questions on the +[#dev-support](https://discord.gg/v3jAxJpwZm){target=new} channel on discord. ## Finding tasks diff --git a/docs/dev-corner/dev-guide/index.md b/docs/dev-corner/dev-guide/index.md index d9ddf2683..32f27f484 100644 --- a/docs/dev-corner/dev-guide/index.md +++ b/docs/dev-corner/dev-guide/index.md @@ -24,11 +24,6 @@ assurance process. This documentation describes the FlyByWire Development Process and tools in detail to help you set up your development environment to be able to efficiently contribute to our projects. -!!! info "Structure" - Currently these sections are specific to the A32NX. It details with the necessary software and tools, downloading and compiling the A32NX successfully, as well as guidelines on how to contribute within the project. - - We will adapt our documentation to cover A380X development requirements in the future as well. - ## Topics | Quick Links | Description | diff --git a/docs/dev-corner/dev-guide/qa-process.md b/docs/dev-corner/dev-guide/qa-process.md index e6cb5b111..687c7ecab 100644 --- a/docs/dev-corner/dev-guide/qa-process.md +++ b/docs/dev-corner/dev-guide/qa-process.md @@ -7,13 +7,17 @@ description: The QA Process is a detailed guide on how to test and report on the ## QA at FlyByWire -FlyByWire Simulations aims to maintain professional standards as well as industry-wide best practices to maximize developer productivity and deliver high-quality, tested products. +FlyByWire Simulations aims to maintain professional standards as well as industry-wide best practices to maximize +developer productivity and deliver high-quality, tested products. -This is why we adopt a set of rules and practices that create a strong framework, not only around the usage of git, but also surrounding code quality. +This is why we adopt a set of rules and practices that create a strong framework, not only around the usage of git, but +also surrounding code quality. -Therefore, every change or addition to the code of our aircraft goes through a multistep development and quality assurance process. +Therefore, every change or addition to the code of our aircraft goes through a multistep development and quality +assurance process. -This documentation describes the FlyByWire QA Process and tools in detail to make sure we can efficiently and effectively deliver the highest quality in our products. +This documentation describes the FlyByWire QA Process and tools in detail to make sure we can efficiently and +effectively deliver the highest quality in our products. ## What you need @@ -27,44 +31,55 @@ To QA test for FlyByWire, you need the following prerequisites: ## Becoming a QA Tester -We try to keep the number of QA testers at a reasonable and manageable level to ensure quality and sufficient PRs to test for each QA team member. +We try to keep the number of QA testers at a reasonable and manageable level to ensure quality and sufficient PRs to +test for each QA team member. If you'd like to apply for the QA Trainee role, we recommend to actually conduct a few tests as described below without submitting any reports to GitHub! -Send an application message and your test reports to the [contact(s)](#contacts) at the bottom of this page via DM, and the QA leaders will decide if you are eligible for a QA Trainee role (provided there are open positions). +Send an application message and your test reports to the [contact(s)](#contacts) at the bottom of this page via DM, and +the QA leaders will decide if you are eligible for a QA Trainee role (provided there are open positions). !!! warning "" **Please do not submit reports to GitHub without having a QA Discord role.** ## What to Test -The FlyByWire development process provides a constant stream of new Pull Requests to be tested as every single code change goes through this workflow. All commits to the master branch (Development Version) are therefore code-reviewed and QA-tested. +The FlyByWire development process provides a constant stream of new Pull Requests to be tested as every single code +change goes through this workflow. All commits to the master branch (Development Version) are therefore code-reviewed +and QA-tested. 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") +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}
[QA Project Board on GitHub](https://github.com/orgs/flybywiresim/projects/7){target=new} +![QA Project Board on GitHub](../assets/qa-process/qa-board.png "QA Project Board on GitHub"){loading=lazy}
+[QA Project Board on GitHub](https://github.com/orgs/flybywiresim/projects/7){target=new} If you have gotten a grasp on the above instructions, pick a PR to test from the list. -Read the description and testing instructions of the PR carefully and make sure you have the required skills and the necessary time available to conduct the test in a high-quality fashion. +Read the description and testing instructions of the PR carefully and make sure you have the required skills and the +necessary time available to conduct the test in a high-quality fashion. !!! tip "Tip: Labels" You will notice that some PRs will have labels specific to the QA team: - - PRs that have the "QA Passed", have been tested, typically you will not have to perform another test unless requested to do so in the QA channel. Additional tests in Tier 2 reports are welcome! + - PRs that have the "QA Passed", have been tested, typically you will not have to perform another test unless + requested to do so in the QA channel. Additional tests in Tier 2 reports are welcome! - PRs that have the "QA Failed" do not require further testing, unless requested to do so. - PRs with the label "QA Ready to Test" should be prioritized over PRs that already have successful tests. - PRs with "QA Not Required" should not be tested. !!! tip "Tip: Projects" - You may take notice of the section for "Awaiting Actions", this section typically means the PR has been approved and is waiting to be merged. You do not have to test these PRs, as they will find their way to the development version of the aircraft shortly. + You may take notice of the section for "Awaiting Actions", this section typically means the PR has been approved and + is waiting to be merged. You do not have to test these PRs, as they will find their way to the development version + of the aircraft shortly. ## How to get PR Builds -Every pull request to the master branch triggers a build of the add-on with the changes made by that PR. This build can be downloaded and manually installed to your Community folder. +Every pull request to the master branch triggers a build of the add-on with the changes made by that PR. This build can +be downloaded and manually installed to your Community folder. How to download the PR for QA @@ -84,17 +99,21 @@ How to download the PR for QA 5. Unzip the file and place the "flybywire-aircraft-a320-neo" folder into your Community Folder. !!! info "PR Builds only for FlyByWire QA Team" - The PR builds are only meant for QA testing and not for daily use. Outside of the FlyByWire QA Team, we do not provide any support or answer any questions regarding these builds. + The PR builds are only meant for QA testing and not for daily use. Outside of the FlyByWire QA Team, we do not + provide any support or answer any questions regarding these builds. ## How to Test ### QA Tiers for PRs -The FlyByWire developers are required to categorize their PRs into two test tiers to indicate the complexity or importance of the PR. +The FlyByWire developers are required to categorize their PRs into two test tiers to indicate the complexity or +importance of the PR. -More complex features or features vital for the stability of the add-on will need considerably more testing than a simple change of a button text. +More complex features or features vital for the stability of the add-on will need considerably more testing than a +simple change of a button text. -The developer, developer leader and QA leader determine the tier of testing required and how many successful tests must be reported before a PR can be accepted and merged into the master branch. +The developer, developer leader and QA leader determine the tier of testing required and how many successful tests must +be reported before a PR can be accepted and merged into the master branch. #### Tier 1 @@ -110,43 +129,58 @@ The developer, developer leader and QA leader determine the tier of testing requ ### Clean Community Folder -It is important that the QA tests are done on a clean system with no other add-ons or liveries installed. These could create false issues and render the whole test meaningless. +It is important that the QA tests are done on a clean system with no other add-ons or liveries installed. These could +create false issues and render the whole test meaningless. Remove everything from your Community folder apart from the "flybywire-aircraft-a320-neo". -Typically, it is ok to keep your Navigraph data installed, though some PRs may require you to test using both the default simulator navdata and the Navigraph ones. Please check the description and instructions of each PR for such remarks. +Typically, it is ok to keep your Navigraph data installed, though some PRs may require you to test using both the +default simulator navdata and the Navigraph ones. Please check the description and instructions of each PR for such +remarks. !!! tip "Tip: Use MSFS Addons Linker" - An easy way to manage add-ons in the Community folder is the [MSFS Addons Linker](https://flightsim.to/file/1572/msfs-addons-linker){target=new} tool from [flightsim.to](https://flightsim.to/). + An easy way to manage add-ons in the Community folder is the + [MSFS Addons Linker](https://flightsim.to/file/1572/msfs-addons-linker){target=new} tool from + [flightsim.to](https://flightsim.to/). - It allows you to create presets to easily switch between different sets of installed add-ons. You can create a preset with only the "flybywire-aircraft-a320-neo" folder left in the Community folder. + It allows you to create presets to easily switch between different sets of installed add-ons. You can create a + preset with only the "flybywire-aircraft-a320-neo" folder left in the Community folder. ### Focus on the PR Test Instructions -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 or information that is expected to be the same through each QA test (such as how you installed the PR or if you emptied your community folder). +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 or information that is expected to be the same through each QA test (such as +how you installed the PR or if you emptied your community folder). -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. +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 -If the test instructions are unclear or any questions come up regarding the test or the outcome, please ask on the Discord "quality-assurance" channel for support. +If the test instructions are unclear or any questions come up regarding the test or the outcome, please ask on the +Discord "quality-assurance" channel for support. -Look in "quality-assurance" if a discussion thread already exists for this issue (thread title starting with PR#), and if it does, ask your questions directly there. +Look in "quality-assurance" if a discussion thread already exists for this issue (thread title starting with PR#), and +if it does, ask your questions directly there. !!! block "" Example:
![Discord Thread Example](../assets/qa-process/discord-thread.png "Discord Thread Example") -If no dedicated thread exists for the PR, please provide the #PR number and title in the "quality-assurance" channel and ask your question or describe your issue. +If no dedicated thread exists for the PR, please provide the #PR number and title in the "quality-assurance" channel and +ask your question or describe your issue. -Additionally, the "quality-assurance" channel contains some helpful pinned messages, so make sure you check those occasionally. +Additionally, the "quality-assurance" channel contains some helpful pinned messages, so make sure you check those +occasionally. ### Communication -Multiple tests in PRs are always welcome. It is still good practice to announce it on the Discord "quality-assurance" channel, if you are starting a test on a certain PR, so that the QA team is aware of progress in testing.
+Multiple tests in PRs are always welcome. It is still good practice to announce it on the Discord "quality-assurance" +channel if you are starting a test on a certain PR, so that the QA team is aware of progress in testing.
(Example: `Starting test on PR #1234 `) -Also reporting the PR# and test result after completing a report is strongly recommended as it helps both developers & QA members to see which PR have been tested and if there were issues in quick time.
+Also reporting the PR# and test result after completing a report is strongly recommended as it helps both developers & +QA members to see which PR have been tested and if there were issues in quick time.
(Example: `Tested PR #1234 : passed.`) ## Reporting on Tests @@ -183,18 +217,23 @@ Media: ``` !!! tip "" - Text wrapped with `` (a.k.a. html comments) in the template will not be visible on your report. You may remove these comments except for the required one at the top of the report. + Text wrapped with `` (a.k.a. html comments) in the template will not be visible on your report. You may + remove these comments except for the required one at the top of the report. ### "Report Details" Section -This section should be filled with details about your report. Please ensure this section is unaltered as our GitHub action read this area. This section is required. +This section should be filled with details about your report. Please ensure this section is unaltered as our GitHub +action read this area. This section is required. !!! warning "" For consistency purposes, please use the DD/MM/YYYY format for the report date. ### "Testing Process" Section -Fill this section with details about the testing process. Though there isn't a specific format to use, it's recommended to include a list of each task (as described in the PR testing instructions) and a note of any part that failed to pass. Common information, such as how you downloaded the PR or if your community folder was empty, should not be included in this section. +Fill this section with details about the testing process. Though there isn't a specific format to use, it's recommended +to include a list of each task (as described in the PR testing instructions) and a note of any part that failed to pass. +Common information, such as how you downloaded the PR or if your community folder was empty, should not be included in +this section. !!! danger "" This section is required. @@ -214,7 +253,8 @@ Used to indicate if the test was a success or a failure. ### "Negatives" Section -List any issues or negatives with this PR test. It is best you also include your expectation (if different from the testing instructions). +List any issues or negatives with this PR test. It is best you also include your expectation (if different from the +testing instructions). !!! info "" You can omit this section if no negatives are found. @@ -228,21 +268,26 @@ Any notes you may have, the positives in the PR, and anything extra you would li ### "Media" Section -If you have any media to be included in the report, make sure to include them in this section. Images, videos, YouTube links or Streamable links are welcome. Please ensure externally linked media is unlisted/public and available for at least 4 weeks from the date you post the report. +If you have any media to be included in the report, make sure to include them in this section. Images, videos, YouTube +links or Streamable links are welcome. Please ensure externally linked media is unlisted/public and available for at +least 4 weeks from the date you post the report. !!! info "" You can omit this section there is no media to include. !!! tip "Tip: Label Your Media" - We recommend you label your images (e.g. A-B-C) especially if you have linked them to a specific item in the negatives section, though for one or two images this is not necessary! + We recommend you label your images (e.g. A-B-C) especially if you have linked them to a specific item in the + negatives section, though for one or two images this is not necessary! !!! tip "Tip: Using Collapsible Sections" - If you need to include multiple images, you can take advantage of the Collapsed Sections feature GitHub offers. Learn more [here](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections){target=new} + If you need to include multiple images, you can take advantage of the Collapsed Sections feature GitHub offers. + Learn more [here](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections){target=new} ### Tips !!! 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. + 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/aircraft/pulls?q=is%3Apr+is%3Aclosed){target=new} @@ -253,35 +298,45 @@ If you have any media to be included in the report, make sure to include them in 2. Click on Saved replies. 3. Give your saved reply a name and paste the QA template. - Then, when writing a QA report, click on the arrow in the top-right corner of the comment field. Select your saved reply and insert the necessary data. + Then, when writing a QA report, click on the arrow in the top-right corner of the comment field. Select your saved + reply and insert the necessary data. - Alternatively, you can use the keyboard shortcut CTRL+. CTRL+1 -> note that the number represents your saved replies, so if you have multiple and your QA template is the third one, you would have to use CTRL+3. + Alternatively, you can use the keyboard shortcut CTRL+. CTRL+1 -> note that the number represents your saved + replies, so if you have multiple and your QA template is the third one, you would have to use CTRL+3. !!! tip "Tip: GitHub Text Customization" - GitHub offers a suite of markdown and HTML style tools to format and customize the text in your reports. Learn more [here](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github){target=new} + GitHub offers a suite of markdown and HTML style tools to format and customize the text in your reports. Learn more + [here](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github){target=new} ## Discord Roles -To manage the QA team and focus on quality, the FlyByWire QA Team currently has two levels of QA testers: **QA Trainee** and **QA Testers**. +To manage the QA team and focus on quality, the FlyByWire QA Team currently has two levels of QA testers: **QA Trainee** +and **QA Testers**. -After being accepted as a QA tester (see [Becoming a QA Tester](#becoming-a-qa-tester)) you will get the QA Trainee role. +After being accepted as a QA tester (see [Becoming a QA Tester](#becoming-a-qa-tester)) you will get the QA Trainee +role. !!! info "QA Roles" **QA Trainees** Should focus on Tier 1 tests at the beginning until the quality of tests and test reports has been established. - Moving from QA Trainee to QA Tester will be based on a combination of report numbers, quality of reports and handling of more in-depth/Tier 2 reports. + Moving from QA Trainee to QA Tester will be based on a combination of report numbers, quality of reports and + handling of more in-depth/Tier 2 reports. --- **QA Testers** - Free to test all available Pull Requests ready to test. The high standard they have proven as a QA Trainee will continue to be expected from them. + Free to test all available Pull Requests ready to test. The high standard they have proven as a QA Trainee will + continue to be expected from them. -In general, to maintain your QA Team status, a minimum of one test every few weeks is required. You can message a QA Team lead on Discord if you need to take a break from testing to retain your status, if you are not able to submit any test reports for an extended period of time. +In general, to maintain your QA Team status, a minimum of one test every few weeks is required. You can message a QA +Team lead on Discord if you need to take a break from testing to retain your status, if you are not able to submit any +test reports for an extended period of time. -Special QA requests to IRL pilots will be made in the #pilot-feedback channel. If you are a pilot and wish to contribute to the project with your knowledge, please contact an online moderator or an administrator on our Discord server. +Special QA requests to IRL pilots will be made in the #pilot-feedback channel. If you are a pilot and wish to contribute +to the project with your knowledge, please contact an online moderator or an administrator on our Discord server. ## Contacts diff --git a/docs/dev-corner/dev-guide/resources.md b/docs/dev-corner/dev-guide/resources.md index 910df505e..07051e02b 100644 --- a/docs/dev-corner/dev-guide/resources.md +++ b/docs/dev-corner/dev-guide/resources.md @@ -6,18 +6,18 @@ description: Resources for working with and on the A32NX and A380X code. # Resources On this page, you will find all the necessary resources, links, and documentation you might need to work with and on the -A32NX code. +A32NX and A380X code. ## GitHub Repositories -The main GitHub repository for the A32NX aircraft is: +The main GitHub repository for the FlyByWire aircraft is: **[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 this version. +The Development versions of the FlyByWire A32NX and A380X are 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 this version. The Stable version is a snapshot (in git terms, a [Tag](https://github.com/flybywiresim/aircraft/tags){target=new}) of the development branch. @@ -32,44 +32,32 @@ to supporting developers (in fact, most channels). [:fontawesome-brands-discord:{: .discord } - **Discord Link**](https://discord.gg/flybywire){target=new} -First get yourself the "programmer" role in +First, get yourself the "programmer" role in [#roles](https://discord.com/channels/738864299392630914/751780817772216401/816730253543604224){target=new}. The most general channel for getting help for development is [#dev-support](https://discord.gg/v3jAxJpwZm){target=new}. -There are many other channels for specific systems or subprojects. If you are working on the flyPad EFB for example, the -`#efb` channel would be an important channel for collaborating and support. +There are several other channels for specific systems or subprojects. ## Tech Stack -Our tech stack includes the following: +Below you can find a table summary of the languages and technologies used in the FylByWire aircraft project. -!!! info "Tech Stack / Language Summary" - Below you can find a table summary of the languages and technologies used in the A32NX project. - - | Category | Language / Technology | - |:------------------------------|-----------------------------------------------------------| - | General | React | - | flyPadOS | Tailwind CSS, Redux | - | Autopilot / Flight Controls | MATLAB / C++ | - | Systems / Physics Simulations | Rust | - | Displays / Avionics | Typescript / React (deprecated) / MSFS Avionics Framework | +| Category | Language / Technology | +|:---------------------------------------------|-----------------------------------------------------------| +| General | React | +| flyPadOS | Tailwind CSS, Redux | +| Autopilot / Flight Controls / Extra Backends | MATLAB / C++ | +| Systems / Physics Simulations | Rust | +| Displays / Avionics | Typescript / React (deprecated) / MSFS Avionics Framework | - Systems development for aircraft uses Rust and the `msfs-rs` library. - Avionics programming is done using JavaScript or TypeScript (depending on the project), with the `React.js` rendering - library. + library or the newer + [MSFS Avionics Framework](https://microsoft.github.io/msfs-avionics-mirror/docs/intro/){target=new}. - Front-end web or desktop app development uses the same technologies outlined above. - Server-side development uses `nest.js` for the API and `MySQL` for the database backend. Knowledge of all items on this list is obviously not necessary, but this can hopefully give you a better insight into what your skills can fit into. -## Tools - -A number of tools make development in Microsoft Flight Simulator easier. - -- [WebUI-DevKit](https://github.com/dga711/msfs-webui-devkit){target=new} - In-game development overlay for html-ui - content. Provides fast reload, console output, and more! -- [devtools-backend-refurb](https://github.com/dga711/devtools-backend-refurb){target=new} - Chrome DevTools server - targeting Coherent GT. Gives you DevTools for html-ui content. WARNING: This is still a work in progress, and tends to - be very finicky. diff --git a/docs/dev-corner/dev-guide/specific/.pages b/docs/dev-corner/dev-guide/specific/.pages index 010e747f9..00295aa16 100644 --- a/docs/dev-corner/dev-guide/specific/.pages +++ b/docs/dev-corner/dev-guide/specific/.pages @@ -2,6 +2,6 @@ title: Specific nav: - index.md - instruments-build-guide.md - - flypad-dev-guide.md + #- flypad-dev-guide.md - flypad-localization.md - javascript-dev-guide.md diff --git a/docs/dev-corner/dev-guide/specific/flypad-dev-guide.md b/docs/dev-corner/dev-guide/specific/flypad-dev-guide.md index 50074a96a..9e958ef6f 100644 --- a/docs/dev-corner/dev-guide/specific/flypad-dev-guide.md +++ b/docs/dev-corner/dev-guide/specific/flypad-dev-guide.md @@ -5,6 +5,8 @@ search: # flyPad Development Guide +

This guide needs to be updated.

+ ## Quick Reloading the flyPad As the aircraft in your project folder is now connected to your MSFS community folder via the Symlink you created in the previous step, each time you load in to the A32NX on MSFS, any changes you've made since the sim was last opened should be updated. diff --git a/docs/dev-corner/dev-guide/specific/flypad-localization.md b/docs/dev-corner/dev-guide/specific/flypad-localization.md index fd2cb7f15..491a6cde5 100644 --- a/docs/dev-corner/dev-guide/specific/flypad-localization.md +++ b/docs/dev-corner/dev-guide/specific/flypad-localization.md @@ -1,8 +1,10 @@ # flyPadOS 3 Localization Process -This page is pulled externally from the FBW Aircraft 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. +We have partnered with Localazy, who offer top-notch software localization services, bringing multi-language support to +our EFB, enhancing the user experience.
[![localazy-mono-logo.svg](../../assets/localazy-mono-logo.svg){ width="300" }](https://localazy.com/term/software-localization?utm_source=flybywiresim. diff --git a/docs/dev-corner/index.md b/docs/dev-corner/index.md index 89a691353..ca172c0dc 100644 --- a/docs/dev-corner/index.md +++ b/docs/dev-corner/index.md @@ -1,6 +1,7 @@ --- title: Development Corner - Overview -description: The Development Corner is dedicated to providing information about the various FlyByWire projects and how to contribute. +description: The Development Corner is dedicated to providing information about the various FlyByWire projects and how + to contribute. --- @@ -9,18 +10,19 @@ description: The Development Corner is dedicated to providing information about Welcome to the Development Corner of the FlyByWire Documentation site. -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. +This section of the FlyByWire Documentation is dedicated to the development aspects of the A32NX and A380X aircraft. 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/aircraft/blob/master/.github/Contributing.md){ .md-button target=new} ## Quick Links -| Topics | -|:-------------------------------------------------------| -| [Development Guide](dev-guide/index.md) | -| [Livery Creator Guide](livery-creators/index.md) | -| [Documentation Guide](documentation-guide/index) | -| [Other](other) | -| [FlyByWire Projects](flybywire-projects/index.md) | +| Topics | +|:--------------------------------------------------| +| [Development Guide](dev-guide/index.md) | +| [Livery Creator Guide](livery-creators/index.md) | +| [Documentation Guide](documentation-guide/index) | +| [Other](other) | +| [FlyByWire Projects](flybywire-projects/index.md) | [//]: # (| [Localization Guide](localization-guide/index.md) |)