Skip to content

Improving Buying Guide user flow and layout#1

Merged
benlachman merged 7 commits intomasterfrom
buying-guide
Aug 22, 2017
Merged

Improving Buying Guide user flow and layout#1
benlachman merged 7 commits intomasterfrom
buying-guide

Conversation

@rickychilcott
Copy link
Copy Markdown
Contributor

@rickychilcott rickychilcott commented Aug 17, 2017

@benlachman this is taking shape.

  • Get Nate to remove background tan color from meter types
  • make meter icons the same size
  • remove the detailed text in step two and replace with the image of the CC
  • make reset -> "start over" and a text link instead of button.
  • change step three to ask as a positive question (e.g. Is the space within 4ft clear…) so that yeses result in positive outcome.
  • make the go buy glow into a nice big button. And the congratulatory text larger
  • test on mobile (wasn't working yesterday)
  • disable links after a user selects a response for each question

- Scroll to question
- Scroll to top on reset
- Horizontal layout
@benlachman
Copy link
Copy Markdown
Contributor

  • Get Nate to remove background tan color from meter types
  • make reset -> "start over" and a text link instead of button.
  • make meter icons the same size
  • test on mobile (wasn't working yesterday)
  • remove the detailed text in step two and replace with the image of the CC
  • change step three to ask as a positive question (e.g. Is the space within 4ft clear…) so that yeses result in positive outcome.
  • make the go buy glow into a nice big button. And the congratulatory text larger.

@rickychilcott
Copy link
Copy Markdown
Contributor Author

OK, I made several changes to the UI, support mobile now, and other minor changes.

I think designing of graphics is all that really remains.

@benlachman are you going to reach out to Nate or shall I? The graphics should be built as the same size, as to fix the sizing problems you experienced before. Also, I haven't seen a credit card graphic anywhere, but maybe I've missed it. Not sure if we have something already.

One other thought/question. When people get to question-3, should we be logging it anywhere? I'm wondering if we want to capture which paths people go down to understand where to focus our attention next?

Comment thread buying-guide.html Outdated
</section>
</div>
<p>
Yay! Glow is compatabile with Glow. You'll be saving money and helping the environment before you know it. <br /><a class="button special fit cta" href="{{ site.share.kickstarter }}">Buy Now</a>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Glow is compatible with Glow"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ha! Good catch. I started with the idea of Home being compatible with a Glow, but then switched it and must have missed it. Clearly, what I wrote doesn't make sense, but how should we think about it?

@rickychilcott
Copy link
Copy Markdown
Contributor Author

@benlachman have you had a chance to review this and figure out how/who/etc of graphics? I'm just not sure who has done what design-wise.

Comment thread _data/buying_guide.yml Outdated
- id: 2
question:
helper_text: We need at least enough space for a credit card to lie flat on the meter panel surface above the meter without interference from a) the contoured circular flange around the meter and b)flange extending from the top of the meter panel
helper_text: We need at least enough space for a credit card to lie flat aginst the meter panel surface without interference.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in aginst

@benlachman benlachman merged commit 69e2752 into master Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants