design / Inline menu

[edenvidal]

• the "/" menu is a quick way to add things. thinks of it as the "add" menu, but inline - when you type "/" in a text field, a dropdown menu appears. this menu shows different types of content you can add, like text, headings, lists, images, or embeds.
• you can scroll through the options or start typing to filter and find what you need quickly. for example, typing "/image" will give
• this is nice https://twitter.com/jh3yy/status/1778948403243725283

[atulbhatt-system32]

@edenvidal For now we don't have any direct typing experience in stage. We can only type when in content-editable mode. So how do you think we should carry on with the "/" menu? Shall we just pop up a menu like cmdk menu shows?

[edenvidal]

@atulbhatt-system32 can't we display the menu on stage? like for every time someone hit "/" ?

[atulbhatt-system32]

yes @edenvidal we can do it like cmd+k by pressing "/"

[atulbhatt-system32]

How is it different from pressing "A" at @edenvidal

What do you mean by inline?

Currently "A" also works kinda inline. It adds new node based on which node is currently selected.

[edenvidal]

@atulbhatt-system32, you're right. It differs from pressing A. the justification is the experience of adding content without context switching.

It is probably worth mentioning that:

• the exact representation of the same data fuels the "a" menu.
• no "a" is available while writing content, so "/" works in this case.
• everything that comes after the "/" is a search/filter for the inline menu.