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

  • Hi Editors, we need help reviewing old and new wiki pages to make sure the new wiki has the latest, best and most correct information.

    Happy to help in anyway I can, just send me a message via the editors discussion group.

  • Hi Dennis,

    You are absolutely right,

    To this point in time all emphasis has been placed on simply getting all of the pages from the old Wiki into the new wiki and in "fixing" their links, images and structure to work in the new wiki.

    That plus some updating and a few new pages for PX4, Vibration, etc. has been a really major and totally time consuming project till now.

    There, are a lot of pages that should be combined into a single page and most of the pages are in need of serious updating.

    Also page titles and Table of Contents ordering and placement need a lot of work.

    Basically the import and repair task has just been completed and the making it current and fixing it up part has just begun.

    The reason, some of them are not in the TOCs is because they are duplicates and await further editing into single pages.

    Your excellent Mission Planner compile page indicates you have considerable capability in WordPress and if you feel at all inclined, please have a go at undertaking any of this.

    I have expanded the Editor Information page to cover importing information from one Wiki page to another and I am also more than happy to help in any way I can.

    http://dev.ardupilot.com/wiki/common-editor-information-resource/

    If you do decide to combine those pages, keep in mind that that they are common pages and can only be successfully edited in the Developer wiki.

    The pages you mention are not in the Developer Wikis menus / tables of contents, because they are targeted at (and automatically copied to) the other 3 wikis (where at least one of them is in each of the tables of contents.)

    By the way if you have any additional "tips" you think might be worthwhile, please feel free to stick them in the above tips section as well, I think this is going to be an important resource as time goes on.

    Thank You,

  • Observation and suggestion:

    Seems there are two files 'documentation' re Downloading and analyzing data logs.
    http://copter.ardupilot.com/wiki/common-downloading-and-analyzing-d...

      This is in the copter dropdown instructions and in the copter and plane table of contents.

    http://copter.ardupilot.com/wiki/common-mission-planner-datalogging

      additional details re parameters and pictures of how to download.

      This one seems to be dangling - no link to it but it has good info.

    Should these not be combined?  Or at least linked somhow.

    I leave that to those who have a grasp of the overall picture.

    Also, there is a great discussion about setting up Google Earth for KMZ files here http://diydrones.com/forum/topics/mission-planner-logs-and-kml-files that I would be happy to add but not sure where.  One of the above documents (near end) or in "Other Mission Planner features". 

    If some think adding the KMZ detail is a good idea - just point me to the location to add it and I will do it.

    Dennis

  • Hi Alex, 

    Definitely, would be great to contribute. My email is oliver.chalk@outlook.com, the way I would do it is to set up another page template and run it on a draft test page, that can be tested on numerous devices without affecting the current layout and then rolled out if everything works good! 

  • Hi Ollie,

    That sounds like it would be really cool and add to the functionality of the site considerably. If you'd like to be added as an editor, reply here with your email and I will send you the onboarding message tomorrow. Hopefully we can talk about getting a working prototype of this together soon. Thanks!

  • I notice you are now in our editors group, you are way more advanced in WordPress capabilities than I am and I would be very happy if you might actually be willing to help out with this a bit.

    This whole WordPress thing is very new to all of us.

    I would also like to very much request that 3DR give you immediate edit access.

  • Hi All,

    Great idea Ollie, I think we all miss the side menu.

    Seems to me a 2 tiered approach is the only reasonable solution, one methodology for small tablets (Not Ipads) and everything else.

    I don't think restricting ourselves to what can be nicely displayed on an Iphone (or Nexus 7 for that matter) is helping.

    I seriously hope we can make this work.

    And, of course, am happy to help in any way I can.

  • Oh weird but cool!

    True, well I did have a look on my iPad and it seemed to work well although the safari by default scales to the max width or width. Also on Xperia Z worked well. Not sure what this would be like on a 7" tablet though with lower res.

    And yeah fairly straightforward, can be set up as a page template and with one menu widget, as seems like you have a custom menu for each sub site that runs on table of contents?

    You could probably do some jQuery to hide/show easily? Or do a responsive CSS based on width?

  • It could be great for tablet users who can't use the drop-down menus, but then again it might take up half their screen. It would be ideal if there was an option to hide or show it.

  • Ah, of course.

    Max has been exploring some mobile options, perhaps we can find one that displays well on tablets and phones. 

This reply was deleted.