You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more so a question related to how we create things with rosdoc2, would it be possible to create a Tutorials.rst file just like how we create an Index.rst file when a client first builds documentation with this tool? I keep seeing calls to centralize everything more, especially with the moving of everything over to docs.ros.org, so I would assume that if we create a Tutorials file it would prompt package maintainers to provide users with some various in-depth guides to using their package effectively. And by generate I don't mean develop tutorials off the bat, I mean just create a file that might say
There are no tutorials available now, come back later or contribute
Also, I wouldn't mind one bit putting in a PR to make this happen, if everybody feels this is beneficial.
The text was updated successfully, but these errors were encountered:
Note that rosdoc2 now automatically shows documentation that you have in the standard location (doc/). If you wanted to show tutorials, one way to do this would be to create a doc/tutorials/ folder containing the tutorials. Those would then be available on rosdoc2 results, all under a 'tutorials' link.
I did another test, and here is another alternative.
REP 149 which defines what is in package.xml has a section with urls. rosdoc2 will now show the urls that are defined there.
Although REP 149 specifies "The type should be one of the following identifiers: website (default), bugtracker or repository." that is not enforced in catkin_pkg.package.parse_package, so alternate types are accepted. So if you add an entry to package.url like:
This is more so a question related to how we create things with rosdoc2, would it be possible to create a
Tutorials.rst
file just like how we create anIndex.rst
file when a client first builds documentation with this tool? I keep seeing calls to centralize everything more, especially with the moving of everything over to docs.ros.org, so I would assume that if we create aTutorials
file it would prompt package maintainers to provide users with some various in-depth guides to using their package effectively. And by generate I don't mean develop tutorials off the bat, I mean just create a file that might sayAlso, I wouldn't mind one bit putting in a PR to make this happen, if everybody feels this is beneficial.
The text was updated successfully, but these errors were encountered: