The Documentation WG is tasked to improve the Dronecode and project sites and to extend and maintain developer and user documentation.

The group are currently looking at how to:

• Create a compelling and unified Dronecode platform story across project websites.
• Document and update the Dronecode Roadmap and release cycle.
• Regular news and community updates.
• Project messaging, marketing and member recruiting.
• Improve user and development guide documentation.
• Enable translation of documentation and engagement with translation communities.

Key information:

• Lead: Hamish Willee
• Members: Peter Adams (Intel), Beatriz Palmeiro (Intel), Ulisses Furquim (Intel), Luis Strano (Intel), Chris Anderson (DroneCode), Mark Charlebois (Qualcomm), Hamish Willee (DroneCode, Dronekit), Lorenz Meier (PX4, QGC), Beat Küng (PX4)
• Meetings: Weekly on Weds 11am PST / 6.15 am AEST
• Contact: Site feedback or email: hamishwillee at gmail dot com

• Updated Dronecode site is being prototyped.
  • The site will continue to hold information about membership but will additionally become a hub for information about working with the platform/projects, and for getting hold of source code, roadmap information and documentation.
  • Site will be migrating from Drupal to WordPress in coming months, and we will have much greater control over content.
• Working Group wiki pages.
  • These have been created/updated for most WGs.
  • We are still iterating the information we provide.
• Working Group monthly updates.
  • We have decided to use the DC blog as the mechanism for publishing project updates (accomplishments, challenges, future plans).
  • A template has been created and a number of updates have been posted.
  • We hope to get all WG Leads posting in the coming months.
• The PX4 User Guide is being migrated to Gitbook
  • All main Dronecode projects will share the same documentation toolchain.
  • Translation is much better supported by Gitbook than WordPress.
• Create a compelling and unified Dronecode platform story
  • We have started to look at options to roll out across project sites, including common fonts/headers, footers, some common menus and branding elements.

We are working through open issues. None are reported here, because nothing is “blocking”, just not discussed yet.