Hosting Nav2 & ROS 2 doxygen in a developer-friendly format.
Totally vibe-coded with Claude Code to the minimum degree required to function. Read the source code and submit PRs at your own (sanity's) risk. Contributions welcome, but manual testing is required.
If any found, put them in the description tables with a detailed description of what they do and an example usage in the C++ and Python examples.
-
Review this project in detail to understand what it does and its context
-
Now, I want to add to the Nav2 and ROS distributions. Also update Rolling Nav2's doxygen, if that's necessary. For now, focus on just the distribution and doxygen parts and copy over the Rolling action/service/topic message APIs to to start off with (both rolling and will need updates in another phase). The artwork for Nav2 release is here: . The artwork for the ROS 2 release is here: . Remove
-
Next, review the curent nav2 rolling branches messages, services, and topics in nav2_msgs. List all the new messages or new fields to those messages which we need to update on rolling. Then, propose the updates to the page(s) and new pages to cover them in rolling in the plan proposal, including full descriptions you plan to use.
-
Do all of this and also make all of these updates in Rolling and both, so that they are the same
-
Make sure all actions, srvs, and msgs are alphabetized in order on the index page for rolling and
-
Make sure all msg/action/srv pages's examples have the python and C++ examples using the new field(s) and ROS interfaces