[Final-Post-Launch] App Tweaks

[cadorn]

$feature https://github.com/goodybag/lunchroom/issues/1

Landing

• [ ] submit feedback & subscribed state
  • [ ] @jrf0110 - UI
• [x] Signup to daily menus using phone number
  • [x] @jrf0110 - UI
  • [x] @cadorn - hookup
• [ ] Add share this link after signing up on landing page.
  • @jrf0110 https://github.com/goodybag/lunchroom-landing/issues/32

    User management

• [x] Skin @jrf0110
• [ ] Set password on checkout
• [ ] Login using email + password
• [ ] Reset password
• [ ] If we have the user’s email address and/or phone number. can we pre-populate that during checkout (in the appropriate fields)
• [x] Checkout Phone/CC validation
• [ ] Success page (after I press place order). We need to ask for phone number/email if they have not provided it.
  • @jrf0110 https://github.com/goodybag/lunchroom-landing/issues/30

    Menu

• [ ] different photo urls for different sections of site
• [ ] Options for items
  • [ ] @jrf0110 - data & UI
  • [ ] @cadorn - hookup
• [x] Signup to daily menus using phone number
• [x] Order for future days

  Emails

• [x] Need to show Pricing in HTML email - @jrf0110
• [x] Remember email in local storage
• [ ] HTML Email
• [ ] Text for 4 restaurants for daily emails

  SMS

• [ ] Send daily menues

  Implementation Issues

• [x] Phone number validation (needs util.js file)
  • Need to provide own path and tweak skin app attachment
• [ ] Remember cart on server if no local storage?
• [ ] Lunchrooms on goodybag.com
  • [ ] as redirect - https://github.com/goodybag/lunchroom/issues/26
  • [ ] as component - https://github.com/goodybag/lunchroom/issues/35
• [x] Remove external use of //lunchroom-stage.goodybag.com:8083/lunchroom/assets/semantic-ui-css/semantic.css
• [x] Include tab hash in URL hash so back button will work when switching tabs
• [x] Keep all browser history for back button when switching views
  • [x] While on checkout screen: browser “back” button doesn’t work.
• [x] Diet tags (veg tag repeating)
• [x] Remove hardcoded email data
• [ ] Multiple listener registration
• [ ] Changable message in header

[cadorn]

Prioritized functionality:

• [x] 1. Daily HTML menu emails
• [x] 1. Change timing: Daily-Menu-Email: 10:00am. Ordering Cut-off: 11am. Delivery: 12:00 to 12:30
  • Change content associated with this: e.g. "Sorry Times up. You must place your order by 11am."
• [x] 2. Ordering In advance: Allow people to order for other days in advance.
  • They can do this as individual checkouts, but better would be: They can do it in a single checkout, but the fee would need to be added for each day.
  • [x] @jrf0110 - UI https://github.com/goodybag/lunchroom-landing/issues/45
  • [x] @cadorn Order from advance days
  • [x] @cadorn Multi-day item checkout display
  • [x] @cadorn Multi-day order submit (one payment)
  • [x] @cadorn Multi-day order receipt (one payment)
  • [x] @cadorn Multi-day delivered emails
  • [x] @cadorn Multi-day order admin
• [x] 3. Fix diet tags. Veggie items need to get tagged.
• [x] 4. When you load a day's menu. Just prior to it loading the menu, it will first load: "This menu has not been created :(": it shouldn't do that and causes some initial confusion.
  • [x] @jrf0110 show splash screen https://github.com/goodybag/lunchroom-landing/issues/42 (currently shows white page until loaded instead of flashing)
• [ ] 5. Fix/improve aesthetics. For example:
  • [ ] * Photos should present well in each size @jrf0110
  • [x] * Tooltip when hovering over 'Deliver to' and 'Delivery time': "We'll send a text and email when your food arrives" https://github.com/goodybag/lunchroom-landing/issues/37 @jrf0110
  • [x] * Say "No Tips" in the checkout near the line items. Today, someone was spending time to find out how to give a tip. And when back to the initial screen where he finally read 'no tips'. https://github.com/goodybag/lunchroom-landing/issues/39 @jrf0110
  • [x] * If someone is on a day that's after today, display "You can order in advance for the rest of the week!"
  • [x] https://github.com/goodybag/lunchroom-landing/issues/43 @jrf0110 design
  • [x] @cadorn hookup
  • [ ] * Should we consider doing the item title on two lines instead of ending with a "…"? @jrf0110
  • [x] * Make checkout validation nice. e.g. a check mark after each thing is filled in correctly. @jrf0110
  • [x] * other thoughts? this is a simple flow..lets polish it up nicely and make it look like we put some care into it.
• [ ] 6. I would rather lose the temporary "to give feedback line" on the bottom of the page. and instead add a LIVE CHAT or Feedback tab
  • [ ] @jrf0110 design
  • [ ] @cadorn hookup
• [x] Unsubscribe from menus
  • [x] @jrf0110 UI - https://github.com/goodybag/lunchroom-landing/issues/46
  • [x] @cadorn implement
  • [x] @cadorn update email templates
• [x] @cadorn "Got status '402' while calling 'stripe.com'" BUT order GOES THROUGH! This happens when using test data on production.
• [x] @cadorn Error response during submit does not show in checkout form
• [x] @cadorn Updated email subscribe confirmation text
• [x] @cadorn Redirect old event links to current event
• [x] @cadorn The alt text for your food images have the same text no matter what the food item is

After that ^^ next things to do:

• [ ] 7. User login. Lets create real users, and lets remember their info.
• [ ] 8. URL. Can we make the actual URL for the week be something memorable. and something that represents their company e.g.
  • bazaarvoice.goodybag.com (always defaults to current day). then bazaarvoice.goodybag.com/thursday etc
  • OR: goodybag.com/bazaarvoice
• [ ] 9. Lets create the ability to send our users a text of 4 items (numbered 1-4). and they can simply reply to say what they want. or something like this.
  • OR: for the time being, just send them photos of the meals with a link to the menu.
• [x] 10. Restaurant orders should be grouped by number of each item
• [ ] 11. **Customizing menu items, only after we are confident about operations.

[jrf0110]

Photos should present well in each size

we'll just need separate photos for the item tiles and the modal view. Currently, the design has a different aspect ratio for the Order Review, but we'll just make them the same as item modal.

So, tile_photo_url and photo_url columns, where photo_url is the square version

[jrf0110]

Photos should present well in each size

I suppose we could add that to the existing item schema in Cater, however, I feel that it's outside of Cater's domain. If we can come up with good enough semantic names, I guess it works. photo_url_landscape photo_url_square - but those are somewhat misleading

[cadorn]

@jrf0110 If you can get all UI work for user/card management done today (and remaining UI work above) I'll setup the account component UI as a test later today ready to implement tomorrow; Today I will focus on advanced orders and various other smaller issues. Sound good?

[cadorn]

@jrf0110 FYI: Did not get to advance ordering today but everything is prepared to move forward if there are no more issues in the morning.

[cadorn]

Logs for staging and production are now on loggly. Client logs errors and debug statements; backend logs everything for now. (Will be deployed with payments update).

[cadorn]

@L8D I found the order submission bug in the process of implementing advance ordering. It should no longer happen after next update and all server errors will now show on client submission form. I think it was caused by old event links.

[cadorn]

@jrf0110 @jpanchal13 I have a preview of advance ordering ready to upload to staging tomorrow morning after ordering has started on production and we can use staging for testing. The functionality on the app side should be complete (I have not done final polish walkthrough), most backend work is done but I still need to update the order display in admin and deal with order delivery emails differently. Getting multi-day ordering to work turned out to be a lot of work that touched the whole flow and data model and I wish I would have added that from the start. I am glad I decided to do some refactoring work along with the advance ordering as I had to touch everything again anyway and it dramatically simplified things and will make adding user accounts much easier now. Logging is also in and various better error catching during order process. After I push to staging tomorrow morning I would like to get feedback on app by the afternoon so I can finish this update tomorrow ready for Wednesday morning. (preview PR: https://github.com/goodybag/lunchroom/pull/46)

[cadorn]

@jrf0110 @jpanchal13 update pushed to staging; I have yet to hook in new checkout validation and send delivery emails; everything else related to advance ordering is done; I have added a better testing system. You can now go to this URL to enable pre-filling the checkout form with test data: http://staging.lunchroom.goodybag.com/?TEST_USER_KEY=3FEB7109-9F4B-4757-A530-7FE7FD6E3130 (link also in goodybag-core project) Go to the URL again with a different value for the test key to disable again. This works for staging and will work on live.

[cadorn]

Advance order issues:

• [x] @cadorn Fix goodybag fee in receipt emails
• [ ] @jrf0110 https://github.com/goodybag/lunchroom-landing/issues/47
• [ ] @jrf0110 https://github.com/goodybag/lunchroom-landing/issues/49
• [ ] @jrf0110 Discuss how multi-day orders will be settled with cater (at order time for all days or per day once delivered? Also I have only one charge token...)
• [ ] @jrf0110 at checkout we need to change the display to show GB Fee, Taxes, Tip, Subtotal after each days order and then at the very bottom a grand total for all days ordered.
• [ ] @jrf0110 also at checkout the display order should be Subtotal, Taxes, GB Fee, Tips
• [x] @cadorn @jrf0110 I placed an advance order for Friday for three items but on admin panel nothing is showing up when I select the restaurant to see who ordered what.
• [x] @cadorn @jrf0110 In admin panel the name of the person who ordered is missing.

[cadorn]

Fixes:

• [x] Escape alt HTML in emails
• [x] Prevent duplicate orders

[cadorn]

Moved: https://github.com/goodybag/lunchroom.goodybag.com/issues/8