2026 - Help Us Improve Isaac Sim Documentation: Share Your Developer Workflows!

[vick-yu]

Hello Isaac Sim Community,

We’re working to make our documentation more helpful and relevant for developers like you. To do this, we need your input!

We’d love to hear:

• Your commonly used workflows and practices with Isaac Sim
• The features or APIs you use most often
• Any pain points or areas where documentation could be clearer
• Your tips or best practices for working with Isaac Sim
• The questions you find yourself asking most often—whether you search the forums, documentation, or ask other users

Your feedback will help us identify gaps, clarify guides, and create new resources based on real developer needs.

Please reply to this thread and share your experiences and questions. Any level of detail is appreciated!

Thank you for helping us make Isaac Sim better for everyone!

[eclipse0922]

First, I appreciate the powerful ecosystem that Isaac Sim provides—Isaac Sim, cuRobo, Isaac ROS, Isaac Lab, etc. offer great flexibility for various workflows.
That said, here are a few areas where I think documentation could improve:

1. Gap between tutorials and real-world workflows
   The basic tutorials are helpful for getting started, but there's a gap when trying to apply them to actual projects. More intermediate-level, workflow-based examples would be valuable.
2. Outdated documentation
   Some docs haven't kept up with recent updates. For example, the cuRobo + Isaac Sim integration guide appears to be out of date, which can cause confusion for developers trying to follow along.
3. ROS2 examples primarily show Isaac Sim as a simulation backend
   Most ROS2 examples treat Isaac Sim as the simulation backend, with planning logic (MoveIt, Nav2) running externally. However, I've successfully used Isaac Sim as the control source—setting up a robot arm + camera inside Isaac Sim, running path planning internally (with cuRobo), and using OmniGraph to publish ROS2 messages to drive a real robot.
   This "sim-as-controller" workflow is technically possible, but without concrete examples, beginners may not realize it's a valid approach or may hesitate to try it. End-to-end examples showing Isaac Sim as the control source (not just the simulation backend) would give developers more confidence.
4. Slow PR turnaround
   When I've tried to submit fixes via pull requests, it takes a long time to get them reviewed and merged. Faster feedback cycles would encourage more community contributions.
5. Unclear contribution process
   For some documentation, it's not clear where the source lives or how to contribute fixes. A clear "How to Contribute" guide for each doc section would help the community help you.

[vick-yu]

@eclipse0922 Thanks for your thorough input. I’ve passed along your suggestions to our team, and they will take appropriate action.

[d-kleine]

For the docs, I would like to add that I think it would be helpful to have an option to pause or jump at a specific time stamp in an animated screencast. Currently, this is not possible in the browser (at least not for me).

[vick-yu]

@d-kleine Thanks, noted — we'll pass this along to the team

[vick-yu]

We've consolidated Isaac Sim feedback into our official thread: 2026 - FEEDBACK Request from Isaac Sim Users (#397). Please repost your suggestion there so it stays on the team's radar alongside other user requests.

Closing this discussion to avoid splitting feedback across multiple threads. Thanks everyone for your input — suggestions have been noted by the team.