USF-1325: Checkout dropin install/init #69
Conversation
|
Hi @jeff-matthews, nice work! Just to let you know, we (Thunderbolts team) are currently working on a refactor, primarily focused on removing the address containers and replacing them with those from the account dropin. If you're interested in reviewing the changes, please refer to this PR: https://git.corp.adobe.com/Commerce-Storefront/checkout-domain-package/pull/747 |
|
After discussing with Naxto, we agreed to remove the standalone install instructions and replace with guidance to use the boilerplate implementation due to the complexity (checkout dropin uses containers from fice other dropins). Naxto and team will review initializer configuration options/use cases next week and provide feedback on what we can do there. |
|
|
||
| ## Admin configuration | ||
|
|
||
| Before you can use the Checkout dropin on your storefront, you must enable and configure [payment providers](https://experienceleague.adobe.com/en/docs/commerce-admin/stores-sales/payments/payments) and [checkout options](https://experienceleague.adobe.com/en/docs/commerce-admin/stores-sales/point-of-purchase/checkout/checkout-process) in the Adobe Commerce Admin. |
There was a problem hiding this comment.
Are there any special callouts we want/need to make about Admin config?
jeff-matthews
requested review from
keoko
and removed request for
emipallares
|
Thanks @mcocapiza. I addressed all of your review feedback. How does this look? |
This pull request (PR) adds the initial docs for installing and initializing the checkout dropin. These docs are for developers who choose not to start a storefront project with the boilerplate template.
I derived info from the commerce-checkout.js file in the boilerplate, but I'm not sure if it's accurate. For example, does a standalone checkout dropin install require the cart, order confirmation, and auth containers?
Also, what about initializer config options? How do we tell developers to do that?