A community member proposed introducing a "link button" component, which is a link with pre-made button stylings, and renaming the button component under forms to "submit button". However, other community members raised concerns that this would lead to more confusion, as buttons have many valid uses beyond just form submissions. They suggested that the root of the problem is that users have been incorrectly trained to think of buttons as links, and the solution should be to correct this misunderstanding, not conform to it. The community members discussed adding better component descriptions, tooltips, and a notification message in the settings to help educate users on the proper use of buttons versus links. They also considered a command to convert a link into a button-like link, but ultimately decided it would be better to focus on improving the understanding of the differences between the two components.
A couple issues with this. We aren't limiting the Button to Forms like Webflow does. There are a lot of valid uses for a button. "Submit" is just one button type.
We also don't want to mislead people by calling links buttons. The root of the problem is that users have been incorrectly trained to think that buttons are links. We want to correct that misunderstanding, not conform to it.
The solution we have is to add component descriptions to the top of the settings panel, like Figma has.
Open to more suggestions now that you understand the nuance of this problem!
WYT about a little notification message in the Settings for buttons? @Oleg Isonen Buttons are basically advanced components that should only be used by devs who know how to use them. Outside of our Form & Radix components, you need to know some JS to properly use a button. So a hint may be warranted to help out those beginners who keep getting confused by buttons vs links.
