Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: new overview docs #283

Merged
merged 71 commits into from
Apr 25, 2017
Merged

WIP: new overview docs #283

merged 71 commits into from
Apr 25, 2017

Conversation

kkowalsky
Copy link
Member

@kkowalsky kkowalsky commented Apr 12, 2017

closes #281 and #175

  • finish wireframes (@souperneon)

  • goal to update formatting for '/overview' page for pricing details to be 'Get Started' (@kkowalsky)

  • new words for 'Get Started' div (@kkowalsky)

  • redesign 'Get Started' div (@souperneon)

  • add detailed content for 'Get Started' steps (@rmglennon)

  • pick out FAQs for both main pricing and pricing docs, create answers (@kkowalsky/@rmglennon)

@kkowalsky
Copy link
Member Author

@rmglennon, new copy looks great.

Is is just me or does the H1 heading level look too big? @souperneon?

@rmglennon
Copy link
Member

Page formatting here is same as others, but I agree...perhaps we move headings on doc to H2 or something?

@kkowalsky
Copy link
Member Author

@rmglennon changes look great!

@souperneon
Copy link
Member

souperneon commented Apr 24, 2017

@rmglennon some more notes

  • In Account settings > Sign up for a Mapzen account, let's not make agree to terms a new step. For email users they have to check a box before they can proceed. It appears as a new step for GitHub users because they auth and come back to check a box. Let's make it a new paragraph and maybe even link to the terms.

(From Rhonda - removed step, added new sentence with link to terms page)

  • In Account settings > Add your Mapzen Flex payment method remove " Be sure to keep your credit card information updated if it expires or you are issued a new number." We will have some method of yelling at the user when their card is close to or has expired via email, dashboard alerts, etc. These will happen by june 1 and not by this launch. I think saying "have a valid credit card" is sufficient.

(From Rhonda - removed that sentence)

  • Some suggestions for the Set monthly spending limits section:
    With Mapzen Flex, you can set limits on your spending each month. This gives you the comfort of knowing that your bill will remain within the maximum amount you specify. YOu will only be charged for what you use which maybe less than the limit you set for the month.
    Limits can be changed at any time but cannot be set to an amount lower than the already accrued charges for that month. If no changes are made, the monthly spending limit stays the same month over month. We will notify you by email as you approach your spending limit.
    (Note: I moved this last line up from the next paragraph)

(From Rhonda - used these edits and reworked paragraph)

  • Unfinished section in Billing information > View your usage

(From Rhonda - removed section after confirming with Evan that this wasn't an option)

  • Left nav order can have API limits above Support?

(From Rhonda - done, reordered TOC)

@burritojustice
Copy link
Member

burritojustice commented Apr 24, 2017

  • in 3. Customize Billing Settings, your bill will remain within the amount you specify -> perhaps will not exceed the amount you specify

(From Rhonda: done, thanks)

@kkowalsky
Copy link
Member Author

the effective date is a nice touch on account settings @rmglennon 👌

@rmglennon
Copy link
Member

rmglennon commented Apr 24, 2017

I think I have addressed the feedback so far. Remaining known issue is that anchor links are not working within this section...investigating.

Update: these should be working now.

@rmglennon rmglennon merged commit 0338389 into master Apr 25, 2017
@rmglennon rmglennon deleted the katie/pricing branch April 25, 2017 18:41
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.

redesign docs overview page
4 participants