Skip to content

Instantly share code, notes, and snippets.

@milkman4

milkman4/openquestions.md

Last active April 4, 2018 16:00
Show Gist options
  • Save milkman4/878766c371531bdd38ab665d1137149e to your computer and use it in GitHub Desktop.
Save milkman4/878766c371531bdd38ab665d1137149e to your computer and use it in GitHub Desktop.
Download ZIP
Open Questions for Accounts and Tour Builder
Raw
openquestions.md

Missing stories and/or questions on Tour Admin page

  • Handle log in/authentication for C3D Admins on accounts management page
    • Are we going to use auth0 for this?
    • If not, we need to build our own auth.
      • determined we're building our own, eventually.
      • MVP is what? auth0 email login and maybe social login?
  • add backend endpoints for editing parts of a tour account
  • add endpoints for editing parts of a user account information
  • research and add stripe interaction when we make changes on accounts
    • how does changes to the account database change the stripe configuration?
    • do we need to ping stripe via api for account info via stripe id?
  • “edit in tour builder” - we dont currently grant access to anyone but a single user...the capabilities for this is being worked on
    • “launch cms” page. All of the capabilities for a super user to edit someone elses tour have not been covered or thought about.
  • manage how changing fields affects subscriptions tiers
    • does changing a field affect the tier?
      • changing a field could change them to custom and have overrides
      • does changing a tier affect all people who already exist on that tier, or only new?
    • if a user is given batches of tour stops or custom fields, what happens upon upgrade?
      • once its custom, only open is to contact us to manage it ourselves
  • what happens when a status is turned to inactive vs live?
    • makes a FRONTEND tour not accessibile if inactive.
    • how does this get represented on the tour CMS frontend?
  • where do I get payment history from? stripe? are we going to be handling storing that data?
  • why are we limiting max stops AND max stops / tour? Why don’t we just limit max stops? limiting max stops / tour adds some confusing logic - and limits people to small tours.
  • what does creating a new account on the tour builder page entail? how do we link that account to an existing user?
  • toggling columns on account list
    • need stories for this
  • how does updating emails work? passwords? right now we’re using auth0 to log in...we dont have this ability with auth0 yet.
  • if someone removes a stop package, how does that get handled? do we provide an interface for that? is there a “stop count manager” thing?

Tour Builder stuff

test and integrate hughs new serverless api testing testing testing!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment