Checkout UI Custom

⚠️ Maintenance ⚠️

Starting June 1st 2023, this application will no longer be maintained by VTEX.

---

The Checkout UI Custom app is responsible for customizing your store's Checkout UI through the admin's interface.

Configuration

1. Using your terminal and the VTEX IO Toolbelt, log into the desired VTEX account.
2. Run vtex install vtex.checkout-ui-custom on the account you're working on.
3. Access your VTEX account's admin.
4. Access Store Setup and then Checkout UI Custom.
5. Make the desired changes using the interface and click on Publish.

ℹ️ _Once the app is installed in your account, the checkout6-custom.js and checkout6-custom.css files will be replaced by the ones generated by this app.*

Modus Operandi

If you access your VTEX account's admin using a Development workspace and publish your changes, the configurations performed using the app will only be applied into the workspace you are working in and not in your store Checkout.

However, notice the following: you should not perform any changes in your account's Master workspace to make your Checkout UI configurations publicly available. Instead, you should use a Development workspace and the History tab displayed on the admin app.

The History tab enables you to load app change history and, therefore, helps your checkout UI coding by reusing configurations performed in previous workspaces.

Let's assume you were working in a Development workspace called testredcolor, and now want your changes to be public. According to how workspaces work in the platform, your changes first need to be applied in a Production workspace that, in turn, will be promoted to Master later.

For this purpose, you can access the History tab using the desired Production workspace, load your last changes from testredcolor and then click on Publish, copying your configurations to the Production workspace you are currently working in.

⚠️ The Header and Footer HTMLs are still configured using the admin's Portal (/admin/portal/#/sites). In order to properly use the Checkout UI Custom app, it is strongly recommended to use the HTMLs stated below:

• Header HTML:

<header class="main-header">
  <div class="container">
    <div class="header-link">
      <a href="/" title="add more products" class="buy-more-link link"
        >Continue shopping</a
      >
      <a
        href="/checkout/#/cart"
        title="back to cart"
        class="back-cart-link link"
        >Back to Cart</a
      >
    </div>
    <a href="/" title="Go to homepage" class="logo">{logo.image}</a>
  </div>
</header>

If you want to insert other contents, make sure of include the class .v-custom-mhide to hide it on mobile resolutions. For example:

<header class="main-header"> ... </header>
<div class="promobar v-custom-mhide> ... </div>

• Footer HTML:

<footer class="main-footer">
  <div class="container">
    <a class="credits-vtex" href="http://www.vtex.com/" target="_blank"
      ><img src="http://brand.vtex.com/static/media/VTEX_pink_RGB.751a9fb5.svg"
    /></a>
  </div>
</footer>

If you are yet using the classic CMS

You can create a workspace and install the app by there. While using the app, you will need apply your changes and copy/paste the content of the files to your portal.

For VTEX Developers

When developing a new version of Checkout UI Custom, take care to compile the checkout files prior to opening a PR and/or publishing a new version of the app. This can be done by running yarn app in your CLI, inside the app's /checkout-ui-custom/ subfolder.

During implementation, you will need to run vtex link on the root folder and also watch assets by running yarn watch in the /checkout-ui-custom/ subfolder

❗Note that during implementation, avoid publishing changes to the workspace. As this will permanently add the changes to the workspace and any changes to the app will not be shown.

Contributors ✨

Thanks goes to these wonderful people:

This project follows the all-contributors specification. Contributions of any kind welcome!