feat(how-to): rename how to guide section

[ghost]

Description

Rename "how-to guide" section to "advanced" and move to the tutorials folder

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The Reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[ghost]

#126 is unfortunately blocked due to a merge conflict that I wasn't able to resolve, so I thought it might be quicker to submit a clean new PR instead.

[kenji-miyake]

@LalithVipulananthan I'm sorry but I wanted you to wait for my review. 😢
I personally think that:

• Tutorial should be step-by-step documents that we want everyone to do.
• How-to guides should be other documents that we don't think everyone needs them.

So I recommend reverting this. What do you think?

[kenji-miyake]

Also, if you want to change the structure, which is a relatively big change, you had to write more background information and reasons in the description so that others can understand it.

[ghost]

@kenji-miyake I apologise for both merging without your review and for the lack of detail in the PR.

Based on your comment on @soblin's original PR, I had assumed that you were okay with the proposed structural change and so that's why I didn't give so much detail for this PR and also why I merged it as soon as @soblin approved the PR.

Whilst we are here, @kminoda was proposing that the scenario testing tutorials should be moved into an advanced tutorials section, which kind of overlaps with this PR.

Perhaps it would be an idea to create a Design discussion to make proposals and suggestions on how to handle advanced tutorials and how-to guides?

[kenji-miyake]

@LalithVipulananthan I'm sorry for my unclear comment. 🙇 But I just commented and didn't approve it.

that's why I didn't give so much detail for this PR

It wasn't good because the reasons of changes aren't clear if I see #126.

Whilst we are here, @kminoda was proposing that the scenario testing tutorials should be moved into an advanced tutorials section, which kind of overlaps with this PR.

I think it's good, but to do that, we didn't have to move all contents from how-to guides.

Perhaps it would be an idea to create a Design discussion to make proposals and suggestions on how to handle advanced tutorials and how-to guides?

Yes, it's a good idea. But before that, I think it's good to revert this to avoid confusion.

[kenji-miyake]

For example, considering Running Autoware without CUDA, is this a tutorial? I don't think so.

[ghost]

@kenji-miyake

Yes, it's a good idea. But before that, I think it's good to revert this to avoid confusion.

Understood. So, what is the best way to revert this change?

[kenji-miyake]

Just click this button. I'll do it this time.