Closed zspencer closed 9 months ago
If I could get some review on the direction that would be appreciated; even though the tests aren't passing yet.
Experience tells me that each section of the checkout experience needs a more human friendly heading that addresses the shopper in a conversation. For example, instead of just "Delivery Area" for the new delivery selection area you would have "Choose your delivery area" -- also that heading stays in edit or persisted mode. And for next section "Add items to your cart" or something. The latter would replace Name/Description/Price table-style headings.
I like the idea of putting some headings! @anaulin has been advocating for splitting the Cart
and the Products
into their own pieces; which I think is the logical next step.
How about:
<Card>
<h3>Delivering To</h3>
<select>...</select>
</Card>
@anaulin has been advocating for splitting the Cart and the Products into their own pieces; which I think is the logical next step.
Makes sense, especially for when product lists start to get longer. Like adding a "View cart" button or panel pinned to the bottom of the screen which pops up a summary overlay. I literally built this for ticket purchasing at Eventbrite π
@zinc-collective/convene-maintainers and @zinc-collective/convene-contributors - I am marking this as ready for review, since it has test coverage on the new endpoints.
prompt the shopper more clearly to select the delivery area before they can do anything else (maybe even like a modal overlay)
Agreed.
if there is only 1 delivery area in the marketplace, select that for them automagically and don't prompt them to select anything
Ya! I'm going to do that in a follow-on PR!
So, in reviewing a bunch of the delivery app workflows, most of them have:
This lends me to believe we want to switch to gathering the
DeliveryArea
thenDeliveryAddress
then showing theProducts
that are available.This uses TurboFrames to replace pieces of the page, rather than relying on TurboStreams. On the one hand, it's lot easier (just respond with html with matching
turbo_frame_tag
s`).Blerg; anyway, I'm checking this in now; but not sure if I like it enough.
Thoughts? In particular:
After!
Video
https://github.com/zinc-collective/convene/assets/50284/3f645a18-01ca-4318-b54e-2ade59e6a8c6