Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generating Tutorials within a ROS 2 Packge #121

Open
CursedRock17 opened this issue Apr 28, 2024 · 3 comments
Open

Generating Tutorials within a ROS 2 Packge #121

CursedRock17 opened this issue Apr 28, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@CursedRock17
Copy link

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.

@rkent
Copy link
Contributor

rkent commented Apr 29, 2024

I don't really understand this request.

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.

@rkent
Copy link
Contributor

rkent commented Apr 29, 2024

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:

<url type="tutorials">https://example.com/tutorials</url>

current rosdoc2 will show that link with the title "Tutorials".

Since that violates REP 149, I suppose the official response would be this is unsupported. But perhaps we should change that.

@tfoote
Copy link
Member

tfoote commented Aug 29, 2024

It would be great to push forward the proposal for standardized tutorial links possibly here and merging/extending with REP 149 and https://index.ros.org/contribute/metadata/#tutorials

Having infrastructure to make tutorials easier in rosdoc2 would be great for hosting the content in the repository.

Then we can provide cross refereneces from the TOC as well as rosindex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants