Documentation on using multi level menus

[maximedegreve]

To support our internal product teams better in incorporating action menus I've updated our docs.
I've also updated our ActionList docs to avoid linking directly to the React components and I've added the nav list there as well.

Note: I still need to update the alt text for the images but I wanted to share this early.

[langermank]

Some grammar suggestions and a few questions 🙂 excited about multi-level!

[langermank]

Was there a decision made elsewhere to use ... to indicate opening a dialog? This is a new pattern to me.

[maximedegreve]

This came out of a earlier conversation you shared where it's confusing if a danger action will trigger a confirmation dialog or not.

Both Apple and Microsoft indicate that a dialog will appear by showing a ... at the back of the title. Therefore I think it's good practice to mimic this behaviour.

[mperrotti]

It does seem to be a pattern used by macOS and Windows (maybe Linux too?), but I didn't realize "..." indicates a the menu item opens dialog until Max told me. It's not obvious - but I think it's ok to follow this pattern as long as it's not critical for users to know that a dialog will be opened.

[langermank]

I feel like it can easily look like truncated text 😅 but I think it's interesting and we should try it.

[maximedegreve]

I'm pretty sure that we shouldn't truncate action list items in menus anyway because you can't have tooltips or another way to read what's behind the truncation?

I remember that discussion we had on the command palette.

[emilybrick]

is there a reason for the explicit Documentation link, rather than just linking to the component docs from the main heading/title?

[maximedegreve]

Not sure. It's something we don't do on headings right now in the documentation. I guess because they also don't get underlined.

[mperrotti]

Thanks for adding all of this detail! Looks great.

[langermank]

Just a few more wording nitpicks, otherwise looks great!