This page has moved to

Click here if you are not redirected.


非常欢迎大家给Dronecode项目的相关指南积极投稿。 投稿内容包括PX4和QGroundControl 开发者和用户指南,以及MAVLink指南。 本篇章用来向投稿者们解释如何对项目指南进行更改、添加内容和创建翻译。

You will need a (free) Github account to contribute to the guides.


Fixing typos or editing the text an existing page is easy:

  1. 点击指南相关页面顶部的工具栏图标Edit

    Gitbook: 编辑页面按钮


  2. 进行修改。

  3. 页面底部会提示投稿者创建一个单独的分支,然后 引导其提交一个拉取请求

The documentation team reviews submitted pull requests and will either merge it or work with you to update it.

If you want to add new pages or images, then you will need to work through the git tool rather than github. Often you will want to build the library using the gitbook toolchain to test your changes.

Adding New Pages and Images - Big Changes

If you want to add new pages or images that can't easily be done through the Github interface. In this case you make changes in the same way as you would for code changes:

  1. Use the git toolchain to get the documentation source code
  2. Modify it as needed (add, change, delete).
  3. Test that it renders properly using the Gitbook client
  4. Create a branch for your changes and create a pull request (PR) to pull it back into the documentation.

Change requests can be either done on the Gitbook website using the Gitbook editor or locally (more flexible, but less user-friendly). Most of these instructions cover the local setup.

Developer or User Guide?

There are different types of PX4 users, and it is important that documentation goes into the right place.

The Developer Guide is for documentation that is relevant to software developers. This includes users who need to:

  • 添加或修改软件平台功能,如模块、飞行模式等。
  • 添加新硬件支持/集成,如飞行控制器、外围、机型等。
  • 从外部源与平台通信,例如一个配套的计算机。
  • 了解软件架构

The User Guide, by contrast, is primarily for users who want to:

  • 使用 PX4 控制飞行器
  • 使用 PX4,基于已支持/现存的机型,构建、修改或配置类似载具。

For example, detailed information about how to build/configure an existing airframe are in the User Guide, while instructions for defining a new airframe are in the Developer Guide.

Get/Push Documentation Source Code

To get the library(s) sources onto your local computer you will need to use the git toolchain. The instructions below explain how to get git and use it on your local computer.

  1. Download git for your computer from
  2. Sign up for github if you haven't already
  3. Create a copy (Fork) of the desired library on Github (instructions here). The library repo URLs are:
  4. Clone (copy) your forked repository to your local computer:

     cd ~/wherever/
     git clone<your git name>/<repository_name>.git For example, to clone the PX4 userguide fork for a user with github account "john_citizen_smith": 
     git clone
  5. Navigate to your local repository (px4_user_guide is used below):

     cd ~/wherever/px4_user_guide
  6. Add a remote called "upstream" to point to the original library. The exmaple below shows how to do this for the user guide (note the URL format - it is the repo URL with extension ".git").

     git remote add upstream

    A "remote" is a handle to a particular repository. The remote named origin is created by default when you clone the repository, and points to your fork of the guide. You want to create a new remote upstream that points to the official version of the document.

  7. Create a branch for your changes:

     git checkout -b <your_feature_branch_name>

    This creates a local branch on your computer named your_feature_branch_name.

  8. Make changes to the documentation as needed (general guidance on this in following sections)

  9. Once you are satisfied with your changes, you can add them to your local branch using a "commit":

     git add <file name>
     git commit -m "<your commit message>" For a good commit message, please refer to 

    Contributing section.

  10. Push your local branch (including commits added to it) to your forked repository on github

    git push origin your_feature_branch_name
  11. Go to your forked repository on Github in a web browser, e.g.:<your git name>/px4_user_guide.git. There you should see the message that a new branch has been pushed to your forked repository.

  12. Create a pull request (PR):
    • On the right hand side of the "new branch message" (see one step before), you should see a green button saying "Compare & Create Pull Request". Press it.
    • A pull request template will be created. It will list your commits and you can (must) add a meaningful title (in case of a one commit PR, it's usually the commit message) and message (explain what you did for what reason. Check other pull requests for comparison)
  13. You're done! Responsible members of PX4 guides will now have a look at your contribution and decide if they want to integrate it. Check if they have questions on your changes every once in a while.

Source Code Structure

The guide uses the Legacy Gitbook Toolchain toolchain. Instructions for how this toolchain is setup and used can be found in the toolchain documentation.

In overview:

  • Pages are written in separate files using markdown (almost the same syntax used by Github wiki).
  • The structure of the book is defined in a file named If you add a new page to the library you must add an entry to this file.
  • This is a multilingual book, so there is a file in the root directory defining what languages are supported.
    • Pages for each language are stored in the folder named for the associated language code (e.g. "zh" for Chinese, "en" for English).
    • You should only ever edit the ENGLISH version of files. We use translation software to manage the other trees.
  • Images must be stored in a sub folder of /assets. This is two folders down from content folders, so if you add an image you will reference it like: ![Image Description](../../assets/path_to_file/filename.jpg)
  • A file named book.json defines any dependencies of the build.
  • A web hook is used to track whenever files are merged into the master branch on this repository, causing the book to rebuild.

Style guide

  1. Files/file names

  2. Put new files in an appropriate sub-folder

  3. Use descriptive names. In particular, image filename should describe what they contain.
  4. Use lower case and separate words using underscores "_"

  5. Images

  6. Use the smallest size and lowest resolution that makes the image still useful.

  7. New images should be created in a sub-folder of /assets/ by default (so they can be shared between translations).

  8. Content:

  9. Use "style" (bold, emphasis, etc) consistently. Bold for button presses and menu definitions. Emphasis for tool names. Otherwise use as little as possible.

  10. Headings and page titles should use "First Letter Capitalisation"
  11. The page title should be a first level heading (#). All other headings should be h2 (##) or lower.
  12. Don't add any style to headings.
  13. Don't translate the first part of a note, tip or warning declaration (e.g. > **Note**) as this precise text is required to render the note properly.

Building the Gitbook Locally

Everything you need to install and build Gitbook locally is also explained in the toolchain documentation.

  1. Install nodejs on your computer (version 4-6 recommended).
  2. Install gitbook via NPM. At the terminal prompt, simply run the following command to install GitBook:

     npm install gitbook-cli -g
  3. Navigate to your local repository:

     cd ~/wherever/px4_user_guide

    1 Install gitbook dependencies:

     gitbook install

    If you run into an error: /usr/bin/env: node: No such file or directory, run ln -s /usr/bin/nodejs /usr/bin/node

  4. Build your book:

     gitbook build
  5. To preview and serve your book, run:

     gitbook serve
    • Now you can browse your local book on http://localhost:4000/
    • Exit serving using CTRL+c in the terminal prompt.
  6. You can also serve on a different port instead of 4000:

     gitbook serve --port 4003
  7. You can also output as html, pdf, epub or mobi:

     gitbook help


We'd love your help to translate QGroundControl and our guides for PX4, QGroundControl and MAVLink. For more information see: Translation.


All PX4/Dronecode documentation is free to use and modify under terms of the permissive CC BY 4.0 licence.

results matching ""

    No results matching ""