Group for the team maintaining and enhancing the APM:Copter, APM:Plane, APM:Rover and other manual wikis.

86 Members
Join Us!

Becoming a Documentation Editor!

Welcome! Documentation editors play a key role in the DIY Drones community. Our ongoing discussions and efforts for the Ardupilot.com sites can be found here at the APM Wiki Editors Discussion Group. The best way to get involved in documentation is to pay the Editors Discuss group a visit, request to join the group, and start participating!

If you'd like edit permission on the Ardupilot.com manual sites, to fix or add something, please join the group above. We'll send you an introductory email with information about how to get started editing the APM Wikis. 

This group here on DIY Drones has mostly just an organization role; it's a way for people who would like to join the documentation team to register their interest, and to show them the correct steps in getting started.

You need to be a member of diydrones to add comments!

Join diydrones

Comments are closed.

Comments

  • Developer

    Dennis

    I think we should just keep the information about compiling and working with the code in the developer's wiki.  I think it will just clutter up the other wikis to add it there as a -common page

  • I have a first draft of the structure (and the old details from the forum)  for Compiling Mission Planner.

     

    In the developer's wiki:   common-Compiling Mission Planner - Draft 

    Take a look and let me know if the structure seems OK and any other initial inputs.  

    Gary, an entry in Developer's webpage .dropdown Menu for Mission Planner may be appropriate soon.  and perhaps a link to wiki page (down at the bottom of the webpage that indicates where to get he source code.)  I leave that to you eventually.

     It will be late next week (26th) before I get back to next edits.  Going camping

  • Good point, the structure and how to get where are currently tricky.

    This stuff needs to be in the Editors info page as well - which is what I will do next.

    Welcome aboard Dennis.

  • Thanks all!  I needed that lesson!  Finally getting a feel for structure.  Next will start my wiki

  • Sorry Alex, just noticed you said the pretty much the same things I just said.

  • Hi dennis, copy this link into your top bookmark bar: http://ardupilot.com/

    This page gives you access to everywhere.

    Click on the Developer item in the menu bar to go to the Developer site

    and click on the Platforms item to select one of the main wikis.

  • FYI as long as an image is in any one of the five xxxx.ardupilot.com/wiki/ sites it is OK to not relink them. It is only for external images and especially the ones on the old Google wiki site that need to be copied in and relinked.

    Also just to clarify, common pages can only be successfully updated on the "dev" site since they are automatically overwritten on the other sites. And there is a (generally short) delay before a common page is actually copied to the other sites (the common pages or their edits may not show up right away on the other sites)

  • I have installed the new current common version of atmega32u2 programming into the developer wiki here and it is in each of the 3 main wikis and is in their TOCs as well.

    http://dev.ardupilot.com/wiki/commonatmega32u2-ppm-encoder/

  • http://ardupilot.com/ then select Developer. However, as a common page, users will access it from the regular Copter, Plane, or Rover wikis. They're the same page, just automatically copied and synced to the developer page. Also it is worth nothing that the software that performs this function takes a little while to copy the edits from the parent common page to the child pages, which is why your edits may not show up immediately on the copter site.

  • One last question:

    How does one get to the "Developer's" wiki from the real world? (when not logged into Wordpress wiki)    Or, how "will" one get there as this effort progresses.  I can not find a link anywhere that gets to a table of contents that might include the common page referred to in the last post ....

This reply was deleted.