Add user research recruitment banner #2301
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Trello: https://trello.com/c/yGMU3sR2 We're only showing the banner on the dashboard so that we don't overwhelm people by showing it everywhere. Ideally we'd have used the GOV.UK Components button [1] for the two buttons. However, the `govuk-button--inverse` CSS class [2] is not supported by the component and there's no easy way to override it. Since we're not using that component we've had to introduce `ApplicationHelper#arrow_svg` to generate the arrow SVG for the start-style button [3]. It would be worth opening a PR to add an `inverse` property to the GOV.UK Components button so we can avoid this duplication. [1]: https://components.publishing.service.gov.uk/component-guide/button [2]: https://design-system.service.gov.uk/components/button/#buttons-on-dark-backgrounds [3]: https://design-system.service.gov.uk/components/button/#start-buttons
Trello: https://trello.com/c/yGMU3sR2 We set a session cookie to hide the banner until the user restarts their browser.
Trello: https://trello.com/c/yGMU3sR2 If the user clicks on "Find out more" then we assume that they've completed the Google Form and therefore we don't want to annoy them by continuing to show them the recruitment banner. We've introduced the `UserResearchRecruitmentController#participate` action so that we can record that the user has clicked the button before sending them off to the Google Form.
Based on this feedback from Joseph [1]: > When you click ‘Sign up’, it would be better if this opened a new tab > rather than replacing the current tab - this could be quite frustrating > for some users who’d then need to navigate back to Signon and might > actually cause people to close the form immediately. [1]: https://trello.com/c/yGMU3sR2/211#comment-64d0dc81295a6fd92483e962
15 tasks
11 tasks
|
Superseded by #2303. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trello: https://trello.com/c/yGMU3sR2
Supersedes #2295.
This is a reworked version of #2295 where I've curated the commits as per @mike29736's suggestion and changed the "Hide this" button to actually look like a button (to address @chrisroos' question in #2295 and @mike29736's concern.
This adds a "sticky" banner on the Signon home page to recruit user research participants for GOV.UK Publishing. The "Find out more" button opens a Google Form (managed by the User Research folk) in a new browser tab. If the user clicks on this button, we record that in the Signon database and we never show them the banner again. If the user clicks on the "Hide this" button then we hide the banner for the duration of the current browser session, but it will be displayed to the user in their next browser session.
As per these recommendations, I tested the version in #2295 against the following devices/browsers (using BrowserStack). Since making the change to the "Hide this" button implementation, I've re-tested in the same browsers...
Desktop
iPad
iPhone