You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I figured I'd raise this as a discussion point to see what people think so we can come to a consensus before raising anything.
Right now we've got a handful of CSS classes we re-use all over the auth views, in particular for things like <button> styles. In most real applications, I'd personally see this as something I need to commonly reuse, and I'd extract it to either a Blade component <x-button> or CSS class .button
That said, the buttons we have so far are not typical buttons you'd find in an app - there's no primary/secondary/danger/etc. styles and it's not guaranteed people will use these styles again as the button is specifically styled for the auth pages.
Thoughts?
The text was updated successfully, but these errors were encountered:
I figured I'd raise this as a discussion point to see what people think so we can come to a consensus before raising anything.
Right now we've got a handful of CSS classes we re-use all over the auth views, in particular for things like
<button>
styles. In most real applications, I'd personally see this as something I need to commonly reuse, and I'd extract it to either a Blade component<x-button>
or CSS class.button
That said, the buttons we have so far are not typical buttons you'd find in an app - there's no primary/secondary/danger/etc. styles and it's not guaranteed people will use these styles again as the button is specifically styled for the auth pages.
Thoughts?
The text was updated successfully, but these errors were encountered: