Content updates:

• replace getting started navigation gif so its not terrible.
• slam tutorial needs a gif / image
• move slam gif to top
• more images, graphics, videos, and gifs in index and description pages. Any index or short page needs graphics. Non-turtlebot.
• update readme hyperlinks
• Make the following pages much better: build pages
• remove word "system" and version 0.2.3
• quickstart tab doesnt mention its master
• build instructions for specific distributions should use debians NOT repos file. And lets put it all into the same workspace now.
• quickstart build script at top of master build page, or let them expand one or another to use.
• reduce trouble shoot guide duplicates and add more (transform issue, lifecycle, etc)
• somewhere we need to mention the message types of the server actions and give a full block diagram overview in detail
• add rb1 base and tiago for robots shown working from Office Marathon 2 paper experiments
• clear demo without lidar or lidar based mapping since that keeps being asked. At least document that also that's not required
• fix transform available plugin hyperlink

New pages / content:

• marathon experiments
• Roadmap (ackermann, non-circular, non-flat, moderner techniques. Grad, hybrid/lattice, MPC/TEB, time/velocity profiles, dynamic detection/tracking, ML on data, redo AMCL faster/better, lanes/keepout/speed/etc, multistory, multimodal mapping and localization [vision + lidar])
• Capabilities description (navigate, waypoints, bt into larger systems, plugins, servers, clear description for when to use plugins and when to create new server w/ data flow)
• Setup guide like in nav1 wiki (odom sources, tf, sensor streams), configuration guide and descriptions. here here. Parameter description and defaults. update viable parameters and namespaces in configuration section for DWB/controller/planner/navfn Website page for configuration guide and setup instructions #1589
• list of known plugins external (costmap [stvl, npvl], planner, controller [teb], recovery)
• Migration builds between distributions (dashing->eloquent [new waypoint follower, rehomologated world model into plan/control servers, created recovery plugins and added backup and wait, created nav2_core interfaces for controller and planners plugins, integrates with SLAM, STVL, and TEB, many bew Bt nodes, map server refactor, many stability improvements, using Tf based positioning, moving from tasks to rclcpp actions], eloquent->foxy [namespacing of params, new dwb params from ROS1 sync, controller interface update, set default BT plugins, many stability improvements, separate nav and localization lifecycle managers to reduce interdependency of localization/slam algorithm, all BT nodes are now plugins, fixes async issues in Bt navigator])
• an "about" page
• Comparison page ROS1 nav to ROS2
• Robots using
• repo structure
• Contributing -> getting involved: what's there + contribution guidelines actually describe the useful information: weekly meetings, process of tickets -> PRs, etc. + (discourse, answers, github ticket, contribution, maintaining, using)
• concepts descriptions (behavior trees, our specific BTs, our planners, our controllers, localization, mapping, what is planning / control, what is a costmap, how we use it and layers). clear description/demo without lidar or lidar based mapping since that keeps being asked. At least document that also that's not required
• read through this and see there are useful nuggets
• http://wiki.ros.org/navigation analyze documentation and add appropriate action items

Formatting:

• host on navigation.ros.og
• move website to a new repo
• missing gif in getting started page
• Navigation2 -> Navigation 2
• Remove titles with "Navigation2" as a prefix, we know what the project is if we're on the site
• Remove all move_base or nav1 references from home page, or any page other than comparison
• website max width restriction so paragraphs don't appear as a single line
• build instructions -> build and install
• remove use case recommendations page
• architecture slide without background
• center videos and images https://sphinx-rtd-theme.readthedocs.io/en/stable/demo/demo.html#directives
• images throughout single pages consistent sizes
• start each tutorial page with the successful outcome to be had at the end
• all images vectors
• all videos properly scaled for aspect ratio and gif-ified if appropriate
• remove (or put on top) all non-hidden section lists
• sidebar needs to be wider for text to not go to next line
• remove documentation guidelines boilerplate