Skip to content

docs: restructure documentation#213

Open
lukeschmitt-tr wants to merge 12 commits into
mainfrom
docs-restructure
Open

docs: restructure documentation#213
lukeschmitt-tr wants to merge 12 commits into
mainfrom
docs-restructure

Conversation

@lukeschmitt-tr

@lukeschmitt-tr lukeschmitt-tr commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

This PR comprehensively updates the documentation structure and fleshes out areas that needed more detail. This includes:

  • Adds a Software and Tools section that describes the CLI and MCP server
  • Adds a new Programming Guide section that includes concepts and now contains the API and script writing guide
  • Splits up troubleshooting items by type and introduces a quick check guide for common issues
  • Groups tutorials by type
  • Adds a link to additional public-facing guides
  • Standardizes language
  • Adds redirects for relocated pages

Recommend reviewing commit-by-commit

Move the CLI and MCP server pages into a new Software & Tools section,
relocate the TOTL and touchscreen guides next to their apps under
Tutorials, regroup the tutorials landing page, rename the LeRobot
entries for clarity, and tidy the top-level navigation.

Add sphinx-reredirects with redirect stubs for the four moved pages
(cli, mcp_server, totl, touchscreen) so existing links keep working.
Add a Programming Guide section that gives the API reference a narrative
front door: a Concepts page covering the driver model (lifecycle, modes,
motion commands, frames and units, reading state, error handling, and
logging) and a Writing a Script walkthrough extracted from the demo
scripts page. Nest the API reference under it. The demo scripts page is
now a clean catalog that points back to the guide.
Move the firmware upgrade procedure out of the software setup page into a
dedicated Firmware Upgrade page so the setup walkthrough stays focused on
network configuration and driver installation.
Rework the software setup intro to describe the host PC, add uv/uvx
install options, drop the stale ROS environment note, and fix grammar.
Add a local table of contents to the configuration page, fix its heading
hierarchy and overview wording, and apply prose fixes across hardware
setup. Standardize on "Arm Controller" and one-sentence-per-line.
@lukeschmitt-tr lukeschmitt-tr marked this pull request as ready for review June 18, 2026 18:36
Turn the single troubleshooting page into a landing with quick checks and
an LED status reference, and split the content into connection, errors,
and motion guides. Rework the error-code reference into root-cause
families with the exact get_error_information() strings, a log-reading
guide, and richer fixes grounded in the controller source.
Add an Additional Guides section to Service and Maintenance linking the
Trossen Arm product and maintenance guides.
Explain why homing is needed and merge the redundant STEP-file sentences
in the Service section, and remove em-dashes from the VR and data
collection UI guides per house style.
@lukeschmitt-tr lukeschmitt-tr force-pushed the docs-restructure branch 2 times, most recently from 421d948 to 29700a8 Compare June 22, 2026 18:21
Update Claude Code, VS Code MCP, and Docker links to their current URLs,
point the virtualenv link at the live docs root, and fix the host
networking link in the connection guide. Refresh stale redirects across
the tutorials (GitHub tree->blob demo links, HuggingFace renames, NVIDIA,
MuJoCo, Amazon), drop dead documentation anchors (ffmpeg, anaconda), and
point the Isaac Lab install link at the current docs. Add linkcheck_ignore
for URLs that reject automated requests but are valid for users.
Add demo cross-references to the factory reset, Ethernet, joint
characteristics, joint modes, and joint limits sections so each
configuration points to the demo that exercises it.
Comment thread docs/getting_started/configuration.rst Outdated
Comment thread docs/getting_started/demo_scripts.rst Outdated
Comment thread docs/getting_started/software_setup.rst Outdated
Comment thread docs/programming_guide/concepts.rst Outdated
Comment thread docs/programming_guide/concepts.rst Outdated
Comment thread docs/troubleshooting/errors.rst Outdated

If the problem persists, please submit a support ticket at `Trossen Robotics Support <https://www.trossenrobotics.com/support>`_.

Error Code Reference

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prefer clear pattern of issue and solution before change
prefer actionable bullet points over long sentence

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

each section now has a description of the issue with bulleted suggestions following

Comment thread docs/troubleshooting/motion.rst Outdated
Comment thread docs/tutorials/openpi.rst
Comment thread docs/tutorials/touchscreen.rst Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants