search

wet-boew / wet-boew-styleguide

A style guide for the Web Experience Toolkit.
http://wet-boew.github.io/wet-boew-styleguide/index-en.html
36 stars 32 forks source link

Sign in/Sign out button and My Profile button Dropdown location #237

Closed MBlondin closed 7 years ago

MBlondin commented 9 years ago

With WET 4.1, where is/will the Sing in/Sign out button and Account settings button located (image is from WET 3.1) image

neoinsight commented 9 years ago

@thomasgohard had pointed me to this pattern in progress earlier this month: https://github.com/wet-boew/wet-boew/issues/6232

MBlondin commented 9 years ago

@neoinsight Thank you Lisa. @thomasgohard is this reference https://github.com/wet-boew/wet-boew/issues/6232 the official Sign in /Sign Out style as of WET 4?

RobJohnston commented 7 years ago

This has been done and examples are available for the GCWeb theme: http://wet-boew.github.io/themes-dist/GCWeb/content-signedon-en.html http://wet-boew.github.io/themes-dist/GCWeb/content-signedoff-en.html

Close?

neoinsight commented 7 years ago

@RobJohnston This looks good! Am pulling in @dk-tbs to represent the Content and IA spec. One thing I would recommend related to the spec is that the example for the signed-in state should show the recommended Canada.ca state for 'transactional scenarios' as per page 39 of the spec. In particular, that requires removing the Canada.ca menu, the Canada.ca search box, most of the footer and the promo tiles. All of these are not displayed so as not to lead people out of the signed-in transaction state accidentally.

Image from spec for small screen:

image

DK-TBS commented 7 years ago

Correct! I should point out though, that although the spec allows for the reduced header/footer etc in transactional scenarios, it doesn't actually demand it. So it's up to authors/owners to decide whether the transaction is sensitive enough that users should be prevented from accidentally clicking away from the process. The latest version of the spec describes it like this:

"On pages where users are engaged in a transactional process—where allowing them to navigate away from the current page would interrupt the intended flow and result in errors, loss of data or accidental termination of the session—elements of the global header and footer may be removed, as follows."

So it's an option, but not strictly mandated. Up to you to decide whether the errors or loss of data are a real and serious risk :)

RobJohnston commented 7 years ago

I was just trolling for issues that could be closed. Sounds like this one can be, no?

neoinsight commented 7 years ago

Yes thank you!