Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Exploration - Checkout Block: What components are needed? #1208

Closed
nerrad opened this issue Nov 19, 2019 · 4 comments
Closed

Exploration - Checkout Block: What components are needed? #1208

nerrad opened this issue Nov 19, 2019 · 4 comments
Assignees
Labels
type: cooldown Things that are queued for a cooldown period (assists with planning).

Comments

@nerrad
Copy link
Contributor

nerrad commented Nov 19, 2019

What will be the components needed for the MVP?

Keeping in mind the MVP will not have inner blocks initially, we still need to identify the logical units in the main block. So this exploration should map out the various components and what we already have vs what needs created.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.63. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@nerrad nerrad added type: cooldown Things that are queued for a cooldown period (assists with planning). and removed type: feature request labels Nov 19, 2019
@nerrad nerrad changed the title Exploration - Checkout block: What are the largest modules of work and potential pain points? Exploration - Checkout Block: What components are needed? Nov 19, 2019
@Aljullu Aljullu self-assigned this Nov 20, 2019
@nerrad
Copy link
Contributor Author

nerrad commented Nov 20, 2019

As a part of this exploration, would be good to see what is being done in this package: https://github.com/Automattic/wp-calypso/tree/master/packages/composite-checkout

@Aljullu
Copy link
Contributor

Aljullu commented Nov 26, 2019

In a similar way as I listed the components I think will be needed for the Cart block (#1207), here it goes the list for the Checkout block. They are also listed with their name and the proposed path.

This exploration doesn't consider if some of these components should rely on other packages as a base (the discussion is ongoing in the Cart block exploration issue).

Express checkout

image

  • ExpressCheckout (/base/components/checkout/express-checkout)
  • ExpressCheckoutButton (/base/components/checkout/express-checkout-button)

Form

image

  • CheckoutForm (/base/components/checkout/form)
  • CheckoutFormStep (/base/components/checkout/form-step)
    • CheckoutContactInformation (/base/components/checkout/contact-information)
      image
    • CheckoutShippingAddress (/base/components/checkout/shipping-address)
      image
      • ShippingAddressPlaceholder (/base/components/checkout/shipping-address-placeholder)
        image
    • CheckoutBillingAddress (/base/components/checkout/billing-address)
      image
    • CheckoutShippingOptions (/base/components/checkout/shipping-options)
      image
      • CheckoutOrderNotesCheckbox (/base/components/checkout/order-notes-checkbox)
    • CheckoutPaymentMethod (/base/components/checkout/payment-method)
      image
      • PaymentMethodTabs (/base/components/checkout/payment-method-tabs)
      • PaymentMethodTab (/base/components/checkout/payment-method-tab)
      • PaymentMethodPlaceholder (/base/components/checkout/payment-method-placeholder)
        image
  • BackLink (defined in Exploration - Cart Block: What components will be needed? #1207)
    image
  • PlaceOrderButton (/base/components/checkout/place-order-button)
    image

Form components

  • Checkbox (/base/components/checkbox)
  • Select (/base/components/select)
  • TextInput (/base/components/text-input)
  • TextInputTooltip (/base/components/text-input-tooltip)
  • PhoneInput (/base/components/phone-input)
  • CountryInput (/base/components/country-input)
  • CountyInput (/base/components/county-input)
  • CreditCardInput (/base/components/credit-card-input)

Other

  • Separator (/base/components/separator)
    image

Sidebar

image

  • CheckoutSidebar (/base/components/checkout/sidebar)
    • All contents are already defined as Cart Block components.

@nerrad
Copy link
Contributor Author

nerrad commented Dec 2, 2019

Thanks @Aljullu for the excellent work in mapping out this block, I was able to use it to break things down into workable issues 🎉 I'm going to close this issue now that we have things mapped out for working on.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: cooldown Things that are queued for a cooldown period (assists with planning).
Projects
None yet
Development

No branches or pull requests

2 participants