@saasquatch/mint-components 1.12.0-8 → 1.12.1-0

package/dist/esm/sqm-stencilbook.entry.js

@@ -1,12 +1,12 @@
 import { h, r as registerInstance, c as Host } from './index-17b4da69.js';
 import { a as commonjsGlobal, u as useMemo, k as useState, f as useEffect, c as createCommonjsModule, n as h$1 } from './stencil-hooks.module-ac12ca1c.js';
-import './global-6306a9b8.js';
-import { x as xn, j as jn, a as setUserIdentity, d as dist, o as an, p as setProgramId } from './index.module-6c840c4e.js';
+import './global-04c7d3b5.js';
+import { $ as $n, S as Sn, b as setUserIdentity, d as dist, X as Xe, o as setProgramId } from './index.module-def4aec5.js';
 import './cjs-bdfb4486.js';
 import './mixins-f60a614c.js';
 import { c as createStyleSheet } from './JSS-67b5cff8.js';
 import { G as GenericTableView } from './GenericTableView-d59d8ab4.js';
-import './useChildElements-fc84e640.js';
+import './useChildElements-32e1bda1.js';
 import { l as luxon } from './luxon-7600be8d.js';
 import './utils-334c1e34.js';
 import './sqm-text-span-view-8d140661.js';
@@ -17,16 +17,17 @@ import { E as EmailRegistrationView } from './email-registration-view-a89a88bf.j
 import { L as LeaderboardRankView } from './sqm-leaderboard-rank-view-10657658.js';
 import { L as LogoutCurrentUserView } from './sqm-logout-current-user-view-2c6122cd.js';
 import { N as NavigationSidebarView } from './sqm-navigation-sidebar-view-0312e073.js';
-import { N as NavigationSidebarItemView } from './sqm-navigation-sidebar-item-view-f8e78810.js';
-import { P as PortalEmailVerificationView } from './sqm-portal-email-verification-view-c6ac5430.js';
+import { N as NavigationSidebarItemView } from './sqm-navigation-sidebar-item-view-60ef06cc.js';
+import { P as PortalEmailVerificationView } from './sqm-portal-email-verification-view-4307c992.js';
 import { P as PortalForgotPasswordView } from './sqm-portal-forgot-password-view-c2ed8fed.js';
-import { P as PortalProfileView } from './sqm-portal-profile-view-15ddbec8.js';
-import './utilities-443732be.js';
+import { P as PortalProfileView } from './sqm-portal-profile-view-ffe955c8.js';
+import './utilities-3f5bba22.js';
+import { P as PortalRegistrationFormView } from './sqm-portal-registration-form-view-1d3066e1.js';
 import { P as PortalResetPasswordView } from './sqm-portal-reset-password-view-79a85e02.js';
 import { P as PortalVerifyEmailView } from './sqm-portal-verify-email-view-d7ea2c56.js';
-import { S as ShareButtonView, L as LeaderboardView, C as CopyTextView, B as BigStatView, P as PortalFrameView, E as EditProfileView, u as useShareLink, a as useShareButton, b as useDemoBigStat, c as StatContainerView, d as PortalChangePasswordView, e as PortalLoginView, f as PortalRegisterView, T as TaskCardView, g as ProgressBarView, h as PoweredByImg$1, i as PortalFooterView, H as HeroView, R as ReferralIframeView, N as NameFieldsView, j as CheckboxFieldView, D as DropdownFieldView, I as InputFieldView, k as RewardExchangeView, r as rewardExchangeCustomErrorMsg, l as rewardExchangeLongText, m as rewardExchangeSelected, n as chooseAmountFixed, o as chooseAmountFixedNoDescription, p as chooseAmountVariable, q as chooseAmountVariableNoDescription, s as chooseAmountVariableDisabled, t as chooseAmountVariableUnavailable, v as confirmFixed, w as confirmVariable, x as redemptionError, y as queryError, z as success, A as successVariable, F as loading, G as empty$1, J as rewardExchange, K as CardFeedView, M as CouponCodeView, O as ProgressBar$2, Q as autoColorScaleCss, U as ShadowViewAddon } from './ShadowViewAddon-69b61037.js';
+import { S as ShareButtonView, L as LeaderboardView, C as CopyTextView, B as BigStatView, P as PortalFrameView, E as EditProfileView, u as useShareLink, a as useShareButton, b as useDemoBigStat, c as StatContainerView, d as PortalChangePasswordView, e as PortalLoginView, f as PortalRegisterView, T as TaskCardView, g as ProgressBarView, h as PoweredByImg$1, i as PortalFooterView, H as HeroView, R as ReferralIframeView, N as NameFieldsView, j as CheckboxFieldView, D as DropdownFieldView, I as InputFieldView, k as RewardExchangeView, r as rewardExchangeCustomErrorMsg, l as rewardExchangeLongText, m as rewardExchangeSelected, n as chooseAmountFixed, o as chooseAmountFixedNoDescription, p as chooseAmountVariable, q as chooseAmountVariableNoDescription, s as chooseAmountVariableDisabled, t as chooseAmountVariableUnavailable, v as confirmFixed, w as confirmVariable, x as redemptionError, y as queryError, z as success, A as successVariable, F as loading, G as empty$1, J as rewardExchange, K as CardFeedView, M as CouponCodeView, O as ProgressBar$2, Q as autoColorScaleCss, U as ShadowViewAddon } from './ShadowViewAddon-e012b2aa.js';
 import { P as PortalContainerView, a as PortalSectionView } from './sqm-portal-container-view-6c582684.js';
-import { O as OtherRegionSlotView, I as InvoiceTableView, T as TaxForm } from './sqm-invoice-table-view-e9075c0b.js';
+import { O as OtherRegionSlotView, I as InvoiceTableView, T as TaxForm } from './sqm-invoice-table-view-6e13a323.js';
 
 /**
  * lodash (Custom Build) <https://lodash.com/>
@@ -2535,36 +2536,36 @@ const routes = `
 `;
 const TemplateNavigation = createHookStory(() => {
   return (h("div", null,
-    h("button", { onClick: () => xn.push("/") }, "/"),
-    h("button", { onClick: () => xn.push("/foo") }, "/foo"),
-    h("button", { onClick: () => xn.push("/bar") }, "/bar"),
-    h("button", { onClick: () => xn.push("/baz/bang") }, "/baz/bang"),
-    h("button", { onClick: () => xn.push("/refer") }, "/refer"),
-    h("button", { onClick: () => xn.push("/refer/1") }, "/refer/1"),
-    h("button", { onClick: () => xn.push("/refer/2") }, "/refer/2"),
-    h("button", { onClick: () => xn.back() }, "Back"),
-    h("button", { onClick: () => xn.forward() }, "Forward"),
+    h("button", { onClick: () => $n.push("/") }, "/"),
+    h("button", { onClick: () => $n.push("/foo") }, "/foo"),
+    h("button", { onClick: () => $n.push("/bar") }, "/bar"),
+    h("button", { onClick: () => $n.push("/baz/bang") }, "/baz/bang"),
+    h("button", { onClick: () => $n.push("/refer") }, "/refer"),
+    h("button", { onClick: () => $n.push("/refer/1") }, "/refer/1"),
+    h("button", { onClick: () => $n.push("/refer/2") }, "/refer/2"),
+    h("button", { onClick: () => $n.back() }, "Back"),
+    h("button", { onClick: () => $n.forward() }, "Forward"),
     h("hr", null),
     h("sqm-router", { innerHTML: templates })));
 });
 const RouteNavigation = createHookStory(() => {
   return (h("div", null,
-    h("button", { onClick: () => xn.push("/") }, "/"),
-    h("button", { onClick: () => xn.push("/foo") }, "/foo"),
-    h("button", { onClick: () => xn.push("/bar") }, "/bar"),
-    h("button", { onClick: () => xn.push("/baz/bang") }, "/baz/bang"),
-    h("button", { onClick: () => xn.push("/refer") }, "/refer"),
-    h("button", { onClick: () => xn.push("/refer/1") }, "/refer/1"),
-    h("button", { onClick: () => xn.push("/refer/2") }, "/refer/2"),
-    h("button", { onClick: () => xn.back() }, "Back"),
-    h("button", { onClick: () => xn.forward() }, "Forward"),
+    h("button", { onClick: () => $n.push("/") }, "/"),
+    h("button", { onClick: () => $n.push("/foo") }, "/foo"),
+    h("button", { onClick: () => $n.push("/bar") }, "/bar"),
+    h("button", { onClick: () => $n.push("/baz/bang") }, "/baz/bang"),
+    h("button", { onClick: () => $n.push("/refer") }, "/refer"),
+    h("button", { onClick: () => $n.push("/refer/1") }, "/refer/1"),
+    h("button", { onClick: () => $n.push("/refer/2") }, "/refer/2"),
+    h("button", { onClick: () => $n.back() }, "Back"),
+    h("button", { onClick: () => $n.forward() }, "Forward"),
     h("hr", null),
     h("sqm-router", { innerHTML: routes })));
 });
 const Styling = createHookStory(() => {
   return (h("div", null,
-    h("button", { onClick: () => xn.push("/") }, "/"),
-    h("button", { onClick: () => xn.push("/foo") }, "/foo"),
+    h("button", { onClick: () => $n.push("/") }, "/"),
+    h("button", { onClick: () => $n.push("/foo") }, "/foo"),
     h("hr", null),
     h("div", { style: { display: "flex", justifyContent: "space-around" } },
       h("sqm-router", { innerHTML: `<template path="/">
@@ -2578,7 +2579,7 @@ function useTemplate(templateString) {
   const [previewTemplate, setPreviewTemplate] = useState(templateString);
   function setPath(e) {
     //@ts-ignore
-    xn.push(e.target.value);
+    $n.push(e.target.value);
   }
   return {
     states: { previewTemplate, editedTemplate },
@@ -2742,8 +2743,8 @@ const FullStackFrame = () => {
       "Current path:",
       " ",
       h("code", null,
-        h("strong", null, (_a = jn()) === null || _a === void 0 ? void 0 : _a.pathname))),
-    h("button", { onClick: xn.back }, "Go Back")));
+        h("strong", null, (_a = Sn()) === null || _a === void 0 ? void 0 : _a.pathname))),
+    h("button", { onClick: $n.back }, "Go Back")));
 };
 const FullStackFrameLoggedOut = () => {
   var _a;
@@ -2767,8 +2768,8 @@ const FullStackFrameLoggedOut = () => {
       "Current path:",
       " ",
       h("code", null,
-        h("strong", null, (_a = jn()) === null || _a === void 0 ? void 0 : _a.pathname))),
-    h("button", { onClick: xn.back }, "Go Back")));
+        h("strong", null, (_a = Sn()) === null || _a === void 0 ? void 0 : _a.pathname))),
+    h("button", { onClick: $n.back }, "Go Back")));
 };
 
 const PortalFrame = /*#__PURE__*/Object.freeze({
@@ -3495,7 +3496,7 @@ function useExchangeButton() {
   const { id, accountId } = setupGraphQL$6();
   const [points, setPoints] = useState(10);
   const [rate, setRate] = useState(100);
-  const [exchange, { data, errors }] = an(EXCHANGE);
+  const [exchange, { data, errors }] = Xe(EXCHANGE);
   return {
     states: {
       points,
@@ -4096,16 +4097,16 @@ function DefaultTemplateView(props) {
         gridTemplateColumns: "repeat(9, 80px)",
         gridGap: "10px",
       } },
-      h("button", { onClick: () => xn.push("/") }, "Dashboard"),
-      props.leadSubmit && (h("button", { onClick: () => xn.push("/refer") }, "Submit a Referral")),
-      h("button", { onClick: () => xn.push("/activity") }, "Activity"),
-      h("button", { onClick: () => xn.push("/editProfile") }, "Edit Profile"),
-      h("button", { onClick: () => xn.push("/login") }, "Login"),
-      h("button", { onClick: () => xn.push("/register") }, "Register"),
-      h("button", { onClick: () => xn.push("/emailVerification") }, "Email Verification"),
-      h("button", { onClick: () => xn.push("/verifyEmail") }, "Verify Email"),
-      h("button", { onClick: () => xn.push("/forgotPassword") }, "Forgot Password"),
-      h("button", { onClick: () => xn.push("/resetPassword") }, "Reset Password")),
+      h("button", { onClick: () => $n.push("/") }, "Dashboard"),
+      props.leadSubmit && (h("button", { onClick: () => $n.push("/refer") }, "Submit a Referral")),
+      h("button", { onClick: () => $n.push("/activity") }, "Activity"),
+      h("button", { onClick: () => $n.push("/editProfile") }, "Edit Profile"),
+      h("button", { onClick: () => $n.push("/login") }, "Login"),
+      h("button", { onClick: () => $n.push("/register") }, "Register"),
+      h("button", { onClick: () => $n.push("/emailVerification") }, "Email Verification"),
+      h("button", { onClick: () => $n.push("/verifyEmail") }, "Verify Email"),
+      h("button", { onClick: () => $n.push("/forgotPassword") }, "Forgot Password"),
+      h("button", { onClick: () => $n.push("/resetPassword") }, "Reset Password")),
     h("br", null),
     h("div", { innerHTML: states.previewTemplate })));
 }
@@ -7417,6 +7418,126 @@ const PortalRegister = /*#__PURE__*/Object.freeze({
   TermsAndConditions: TermsAndConditions
 });
 
+const PortalRegistrationForm_stories = {
+  title: "Components/Microsite Register Form New",
+};
+const defaultProps$4 = {
+  states: {
+    error: "",
+    loading: false,
+    confirmPassword: true,
+    hideInputs: false,
+    loginPath: "/login",
+  },
+  callbacks: {
+    submit: () => console.log("Submit!"),
+    inputFunction: () => { },
+  },
+  refs: {
+    formRef: {},
+  },
+  content: { pageLabel: "Register", confirmPasswordLabel: "Confirm Password" },
+};
+const errorProps$2 = {
+  states: {
+    error: "Something went wrong. Please try again.",
+    loading: false,
+    confirmPassword: true,
+    hideInputs: false,
+    loginPath: "/login",
+  },
+  callbacks: {
+    submit: () => console.log("Submit!"),
+    inputFunction: () => { },
+  },
+  refs: {
+    formRef: {},
+  },
+  content: {
+    pageLabel: "Register",
+    confirmPasswordLabel: "Confirm Password",
+  },
+};
+const loadingProps$2 = {
+  states: {
+    error: "",
+    loading: true,
+    confirmPassword: true,
+    hideInputs: false,
+    loginPath: "/login",
+  },
+  callbacks: {
+    submit: () => console.log("Submit!"),
+    inputFunction: () => { },
+  },
+  refs: {
+    formRef: {},
+  },
+  content: { pageLabel: "Register", confirmPasswordLabel: "Confirm Password" },
+};
+const slottedProps$1 = {
+  states: {
+    error: "",
+    loading: false,
+    confirmPassword: true,
+    hideInputs: false,
+    loginPath: "/login",
+  },
+  callbacks: {
+    submit: () => console.log("Submit!"),
+    inputFunction: () => { },
+  },
+  refs: {
+    formRef: {},
+  },
+  content: {
+    pageLabel: "Register",
+    confirmPasswordLabel: "Confirm Password",
+    formData: (h("div", null,
+      h("sl-input", { style: { marginBottom: "var(--sl-spacing-x-large)" }, exportparts: "label: input-label, base: input-base", label: "Slotted Input", required: true }),
+      h("sl-input", { exportparts: "label: input-label, base: input-base", label: "Slotted Input 2", required: true }))),
+  },
+};
+const Default$4 = () => h(PortalRegistrationFormView, Object.assign({}, defaultProps$4));
+const RegisterWithError$1 = () => (h(PortalRegistrationFormView, Object.assign({}, errorProps$2)));
+const RegisterLoading$1 = () => (h(PortalRegistrationFormView, Object.assign({}, loadingProps$2)));
+const FieldsHidden$1 = () => {
+  return (h("sqm-portal-register", { demoData: {
+      states: {
+        error: "",
+        loading: true,
+        registrationFormState: {},
+        confirmPassword: true,
+        hideInputs: true,
+        loginPath: "/login",
+      },
+    } }));
+};
+const SlottedInputs$1 = () => (h(PortalRegistrationFormView, Object.assign({}, slottedProps$1)));
+const RegisterWithMarketingEmailsCheckbox = () => (h(PortalRegistrationFormView, Object.assign({}, defaultProps$4, { content: {
+    ...defaultProps$4.content,
+    emailOptIn: (h("sqm-checkbox-field", { checkboxLabel: "I would like to receive marketing and promotional emails for this referral program" })),
+  } })));
+const TermsAndConditions$1 = () => (h(PortalRegistrationFormView, Object.assign({}, defaultProps$4, { content: {
+    ...defaultProps$4.content,
+    terms: (h("p", null,
+      "By signing up you agree to the",
+      " ",
+      h("a", { href: "https://example.com", target: "_blank" }, "Terms and Conditions"))),
+  } })));
+
+const NewPortalRegistrationForm = /*#__PURE__*/Object.freeze({
+  __proto__: null,
+  'default': PortalRegistrationForm_stories,
+  Default: Default$4,
+  RegisterWithError: RegisterWithError$1,
+  RegisterLoading: RegisterLoading$1,
+  FieldsHidden: FieldsHidden$1,
+  SlottedInputs: SlottedInputs$1,
+  RegisterWithMarketingEmailsCheckbox: RegisterWithMarketingEmailsCheckbox,
+  TermsAndConditions: TermsAndConditions$1
+});
+
 const scenario$6 = "@author:derek\n@owner:ian\nFeature: Forgot Password\n\n  @motivating\n  Scenario: Users can request to reset their password\n    Given a user enters their email address\n    And that email address is linked to a previously created account\n    When they click \"Reset Password\"\n    Then the button enters a loading state\n    When the password reset email is sent\n    Then a confirmation banner is shown stating a password reset email was sent\n\n  @motivating\n  Scenario: Users are notified if sending their password reset email fails\n    Given a user enters their email address\n    And that email address is linked to a previously created account\n    When they click \"Reset Password\"\n    Then the button enters a loading state\n    When the password reset email fails to send\n    Then the user does not receive a password reset email\n    And an error banner is shown stating that they should try again\n\n  @motivating\n  @landmine\n  Scenario: If the input email is not associated to an account a success banner is shown but an email is not be sent\n    Given the user entered an email address that is not associated to an accoun\n    When they click \"Reset Password\"\n    Then the button enters a loading state\n    But no email is sent\n    And a success banner is shown stating a password reset email was sent if the given email was associated to an account\n\n  @motivating\n  Scenario: Users can resend password reset email\n    Given a user had previously requested to reset their password\n    When they enter their email address\n    And that email address is linked to a previously created account\n    And they click \"Reset Password\"\n    Then the user receives a second password reset email\n    And a success banner is shown stating that their email was sent\n\n  @motivating\n  Scenario Outline: The email link can be configured to redirect users to a specific base path but defaults to \"/resetPassword\"\n    Given a user viewing the password reset component\n    And the component <mayHave> \"redirect-path\" with <value>\n    When they request a password reset email\n    And they click the link in the email\n    Then they are redirected to <redirectPath>\n    Examples:\n      | mayHave      | value            | redirectPath     |\n      | doesn't have | N/A              | /resetPassword   |\n      | has          | /resetMyPassword | /resetMyPassword |\n\n  @minutia\n  Scenario Outline: Navigation back to the login page can be customized but defaults to \"/login\"\n    Given a user viewing the password reset component\n    And the component <mayHave> \"login-path\" with <value>\n    Then they see a \"Sign In\" text button\n    When they click \"Sign In\"\n    Then they are redirected to <redirectPath>\n    Examples:\n      | mayHave      | value   | redirectPath |\n      | doesn't have | N/A     | /login       |\n      | has          | /signin | /signin      |";
 
 const PortalForgotPassword_stories = {
@@ -7425,7 +7546,7 @@ const PortalForgotPassword_stories = {
     scenario: scenario$6,
   },
 };
-const defaultProps$4 = {
+const defaultProps$5 = {
   states: {
     error: "",
     loading: false,
@@ -7440,7 +7561,7 @@ const defaultProps$4 = {
     messageSlot: "Enter your email below to receive a password reset link.",
   },
 };
-const errorProps$2 = {
+const errorProps$3 = {
   states: {
     error: "Something went wrong. Please try again.",
     loading: false,
@@ -7455,7 +7576,7 @@ const errorProps$2 = {
     messageSlot: "Enter your email below to receive a password reset link.",
   },
 };
-const loadingProps$2 = {
+const loadingProps$3 = {
   states: {
     error: "",
     loading: true,
@@ -7485,15 +7606,15 @@ const successProps = {
     messageSlot: "Enter your email below to receive a password reset link.",
   },
 };
-const Default$4 = () => h(PortalForgotPasswordView, Object.assign({}, defaultProps$4));
-const ForgotPasswordWithError = () => (h(PortalForgotPasswordView, Object.assign({}, errorProps$2)));
-const ForgotPasswordLoading = () => (h(PortalForgotPasswordView, Object.assign({}, loadingProps$2)));
+const Default$5 = () => h(PortalForgotPasswordView, Object.assign({}, defaultProps$5));
+const ForgotPasswordWithError = () => (h(PortalForgotPasswordView, Object.assign({}, errorProps$3)));
+const ForgotPasswordLoading = () => (h(PortalForgotPasswordView, Object.assign({}, loadingProps$3)));
 const ForgotPasswordSuccess = () => (h(PortalForgotPasswordView, Object.assign({}, successProps)));
 
 const PortalForgotPassword = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': PortalForgotPassword_stories,
-  Default: Default$4,
+  Default: Default$5,
   ForgotPasswordWithError: ForgotPasswordWithError,
   ForgotPasswordLoading: ForgotPasswordLoading,
   ForgotPasswordSuccess: ForgotPasswordSuccess
@@ -7526,12 +7647,12 @@ const defaultStates = {
   loadingVerification: false,
   countdown: 10,
 };
-const defaultProps$5 = {
+const defaultProps$6 = {
   states: defaultStates,
   callbacks: defaultCallbacks,
   content: defaultContent,
 };
-const errorProps$3 = {
+const errorProps$4 = {
   states: {
     ...defaultStates,
     error: "Something went wrong. Please try again.",
@@ -7539,7 +7660,7 @@ const errorProps$3 = {
   callbacks: defaultCallbacks,
   content: defaultContent,
 };
-const loadingProps$3 = {
+const loadingProps$4 = {
   states: {
     ...defaultStates,
     loading: true,
@@ -7564,16 +7685,16 @@ const loadingVerificationProps = {
   callbacks: defaultCallbacks,
   content: defaultContent,
 };
-const Default$5 = () => h(PortalEmailVerificationView, Object.assign({}, defaultProps$5));
-const EmailVerificationWithError = () => (h(PortalEmailVerificationView, Object.assign({}, errorProps$3)));
-const EmailVerificationLoading = () => (h(PortalEmailVerificationView, Object.assign({}, loadingProps$3)));
+const Default$6 = () => h(PortalEmailVerificationView, Object.assign({}, defaultProps$6));
+const EmailVerificationWithError = () => (h(PortalEmailVerificationView, Object.assign({}, errorProps$4)));
+const EmailVerificationLoading = () => (h(PortalEmailVerificationView, Object.assign({}, loadingProps$4)));
 const EmailVerificationCheckingVerification = () => (h(PortalEmailVerificationView, Object.assign({}, loadingVerificationProps)));
 const EmailVerificationSuccess = () => (h(PortalEmailVerificationView, Object.assign({}, successProps$1)));
 
 const PortalEmailVerification = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': PortalEmailVerification_stories,
-  Default: Default$5,
+  Default: Default$6,
   EmailVerificationWithError: EmailVerificationWithError,
   EmailVerificationLoading: EmailVerificationLoading,
   EmailVerificationCheckingVerification: EmailVerificationCheckingVerification,
@@ -7588,7 +7709,7 @@ const PortalResetPassword_stories = {
     scenario: scenario$8,
   },
 };
-const defaultProps$6 = {
+const defaultProps$7 = {
   states: {
     error: "",
     loading: false,
@@ -7634,7 +7755,7 @@ const defaultPropsNoConfirm = {
     failed: () => console.log("failed"),
   },
 };
-const errorProps$4 = {
+const errorProps$5 = {
   states: {
     error: "Something went wrong. Please try again.",
     loading: false,
@@ -7657,7 +7778,7 @@ const errorProps$4 = {
     failed: () => console.log("failed"),
   },
 };
-const loadingProps$4 = {
+const loadingProps$5 = {
   states: {
     error: "",
     loading: true,
@@ -7726,17 +7847,17 @@ const validatingCodeProps = {
     failed: () => console.log("failed"),
   },
 };
-const Default$6 = () => h(PortalResetPasswordView, Object.assign({}, defaultProps$6));
+const Default$7 = () => h(PortalResetPasswordView, Object.assign({}, defaultProps$7));
 const DefaultWithoutConfirmField = () => (h(PortalResetPasswordView, Object.assign({}, defaultPropsNoConfirm)));
-const ResetPasswordWithError = () => (h(PortalResetPasswordView, Object.assign({}, errorProps$4)));
-const ResetPasswordLoading = () => (h(PortalResetPasswordView, Object.assign({}, loadingProps$4)));
+const ResetPasswordWithError = () => (h(PortalResetPasswordView, Object.assign({}, errorProps$5)));
+const ResetPasswordLoading = () => (h(PortalResetPasswordView, Object.assign({}, loadingProps$5)));
 const ResetPasswordSuccess = () => (h(PortalResetPasswordView, Object.assign({}, successProps$2)));
 const CodeValidating = () => (h(PortalResetPasswordView, Object.assign({}, validatingCodeProps)));
 
 const PortalResetPassword = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': PortalResetPassword_stories,
-  Default: Default$6,
+  Default: Default$7,
   DefaultWithoutConfirmField: DefaultWithoutConfirmField,
   ResetPasswordWithError: ResetPasswordWithError,
   ResetPasswordLoading: ResetPasswordLoading,
@@ -7752,7 +7873,7 @@ const PortalVerifyEmail_stories = {
     scenario: scenario$9,
   },
 };
-const errorProps$5 = {
+const errorProps$6 = {
   states: {
     error: "Something went wrong. Please try again.",
     loading: false,
@@ -7786,7 +7907,7 @@ const verifiedProps = {
   },
   content: {},
 };
-const EmailVerificationWithError$1 = () => (h(PortalVerifyEmailView, Object.assign({}, errorProps$5)));
+const EmailVerificationWithError$1 = () => (h(PortalVerifyEmailView, Object.assign({}, errorProps$6)));
 const EmailVerificationSuccess$1 = () => (h(PortalVerifyEmailView, Object.assign({}, verifiedProps)));
 
 const PortalVerifyEmail = /*#__PURE__*/Object.freeze({
@@ -7799,7 +7920,7 @@ const PortalVerifyEmail = /*#__PURE__*/Object.freeze({
 const AssetCard_stories = {
   title: "Components/Asset Card",
 };
-const Default$7 = () => {
+const Default$8 = () => {
   const props = {
     text: { titleText: "Marketing Banner" },
     imgUrl: "https://res.cloudinary.com/saasquatch/image/upload/v1634255445/squatch-assets/Copy_of_saasquatch-logo-tree-large-horizontal.png",
@@ -7827,7 +7948,7 @@ const CardWithNoImg = () => {
 const AssetCard = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': AssetCard_stories,
-  Default: Default$7,
+  Default: Default$8,
   CardWithLongText: CardWithLongText,
   CardWithNoImg: CardWithNoImg
 });
@@ -7916,7 +8037,7 @@ const ChangePassword_stories = {
     scenario: scenario$a,
   },
 };
-const defaultProps$7 = {
+const defaultProps$8 = {
   states: {
     open: false,
     loading: false,
@@ -7960,7 +8081,7 @@ const openProps = {
     submit: (e) => console.log("Submit", e),
   },
 };
-const errorProps$6 = {
+const errorProps$7 = {
   states: {
     open: true,
     loading: false,
@@ -8004,7 +8125,7 @@ const passwordErrorProps = {
     submit: (e) => console.log("Submit", e),
   },
 };
-const loadingProps$5 = {
+const loadingProps$6 = {
   states: {
     open: true,
     loading: true,
@@ -8048,17 +8169,17 @@ const successProps$3 = {
     submit: (e) => console.log("Submit", e),
   },
 };
-const Default$8 = () => h(PortalChangePasswordView, Object.assign({}, defaultProps$7));
+const Default$9 = () => h(PortalChangePasswordView, Object.assign({}, defaultProps$8));
 const Open = () => h(PortalChangePasswordView, Object.assign({}, openProps));
-const Error$2 = () => h(PortalChangePasswordView, Object.assign({}, errorProps$6));
+const Error$2 = () => h(PortalChangePasswordView, Object.assign({}, errorProps$7));
 const PaswordError = () => (h(PortalChangePasswordView, Object.assign({}, passwordErrorProps)));
-const Loading$1 = () => h(PortalChangePasswordView, Object.assign({}, loadingProps$5));
+const Loading$1 = () => h(PortalChangePasswordView, Object.assign({}, loadingProps$6));
 const Success = () => h(PortalChangePasswordView, Object.assign({}, successProps$3));
 
 const ChangePassword = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': ChangePassword_stories,
-  Default: Default$8,
+  Default: Default$9,
   Open: Open,
   Error: Error$2,
   PaswordError: PaswordError,
@@ -8069,7 +8190,7 @@ const ChangePassword = /*#__PURE__*/Object.freeze({
 const PortalProfile_stories = {
   title: "Components/Microsite Profile",
 };
-const defaultProps$8 = {
+const defaultProps$9 = {
   states: {
     success: false,
     loading: false,
@@ -8141,7 +8262,7 @@ const noCountry = {
     onChange: (e) => console.log(e),
   },
 };
-const loadingProps$6 = {
+const loadingProps$7 = {
   states: {
     success: false,
     loading: true,
@@ -8213,7 +8334,7 @@ const disabledProps = {
     onChange: (e) => console.log(e),
   },
 };
-const errorProps$7 = {
+const errorProps$8 = {
   states: {
     success: false,
     loading: false,
@@ -8285,17 +8406,17 @@ const successProps$4 = {
     onChange: (e) => console.log(e),
   },
 };
-const Default$9 = () => h(PortalProfileView, Object.assign({}, defaultProps$8));
+const Default$a = () => h(PortalProfileView, Object.assign({}, defaultProps$9));
 const DefaultNoCountry = () => h(PortalProfileView, Object.assign({}, noCountry));
-const Loading$2 = () => h(PortalProfileView, Object.assign({}, loadingProps$6));
+const Loading$2 = () => h(PortalProfileView, Object.assign({}, loadingProps$7));
 const Disabled$1 = () => h(PortalProfileView, Object.assign({}, disabledProps));
-const Error$3 = () => h(PortalProfileView, Object.assign({}, errorProps$7));
+const Error$3 = () => h(PortalProfileView, Object.assign({}, errorProps$8));
 const Success$1 = () => h(PortalProfileView, Object.assign({}, successProps$4));
 
 const PortalProfile = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': PortalProfile_stories,
-  Default: Default$9,
+  Default: Default$a,
   DefaultNoCountry: DefaultNoCountry,
   Loading: Loading$2,
   Disabled: Disabled$1,
@@ -10255,7 +10376,7 @@ const ProgramMenu = /*#__PURE__*/Object.freeze({
 const PoweredByImg_stories = {
   title: "Powered By",
 };
-const Default$a = () => {
+const Default$b = () => {
   return h(PoweredByImg$1, null);
 };
 const CustomColor = () => {
@@ -10268,7 +10389,7 @@ const CustomWidthAndHeight = () => {
 const PoweredByImg = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': PoweredByImg_stories,
-  Default: Default$a,
+  Default: Default$b,
   CustomColor: CustomColor,
   CustomWidthAndHeight: CustomWidthAndHeight
 });
@@ -10281,7 +10402,7 @@ const PortalFooter_stories = {
     scenario: scenario$f,
   },
 };
-const defaultProps$9 = {
+const defaultProps$a = {
   supportEmail: "support@example.com",
   supportText: "For program support, contact {email}",
   hidePoweredBy: false,
@@ -10291,12 +10412,12 @@ const defaultProps$9 = {
   paddingBottom: "large",
   paddingLeft: "large",
 };
-const DefaultFooter = () => h(PortalFooterView, Object.assign({}, defaultProps$9));
-const FooterWithTerms = () => (h(PortalFooterView, Object.assign({}, defaultProps$9, { termsLink: "https://example.com", termsText: "Terms and Conditions" })));
-const FooterWithFAQ = () => (h(PortalFooterView, Object.assign({}, defaultProps$9, { faqLink: "https://example.com", faqText: "FAQ" })));
-const FooterWithTermsAndFAQ = () => (h(PortalFooterView, Object.assign({}, defaultProps$9, { termsLink: "https://example.com", termsText: "Terms and Conditions", faqLink: "https://example.com", faqText: "FAQ" })));
-const FooterNoPoweredBy = () => (h(PortalFooterView, Object.assign({}, defaultProps$9, { termsLink: "https://example.com", termsText: "Terms and Conditions", faqLink: "https://example.com", faqText: "FAQ", hidePoweredBy: true })));
-const FooterNoSupportText = () => (h(PortalFooterView, Object.assign({}, defaultProps$9, { termsLink: "https://example.com", termsText: "Terms and Conditions", faqLink: "https://example.com", faqText: "FAQ", hideSupportText: true })));
+const DefaultFooter = () => h(PortalFooterView, Object.assign({}, defaultProps$a));
+const FooterWithTerms = () => (h(PortalFooterView, Object.assign({}, defaultProps$a, { termsLink: "https://example.com", termsText: "Terms and Conditions" })));
+const FooterWithFAQ = () => (h(PortalFooterView, Object.assign({}, defaultProps$a, { faqLink: "https://example.com", faqText: "FAQ" })));
+const FooterWithTermsAndFAQ = () => (h(PortalFooterView, Object.assign({}, defaultProps$a, { termsLink: "https://example.com", termsText: "Terms and Conditions", faqLink: "https://example.com", faqText: "FAQ" })));
+const FooterNoPoweredBy = () => (h(PortalFooterView, Object.assign({}, defaultProps$a, { termsLink: "https://example.com", termsText: "Terms and Conditions", faqLink: "https://example.com", faqText: "FAQ", hidePoweredBy: true })));
+const FooterNoSupportText = () => (h(PortalFooterView, Object.assign({}, defaultProps$a, { termsLink: "https://example.com", termsText: "Terms and Conditions", faqLink: "https://example.com", faqText: "FAQ", hideSupportText: true })));
 
 const PortalFooter = /*#__PURE__*/Object.freeze({
   __proto__: null,
@@ -10578,7 +10699,7 @@ const props$1 = {
     },
   },
 };
-const errorProps$8 = {
+const errorProps$9 = {
   states: {
     registrationFormState: {
       validationErrors: {
@@ -10596,7 +10717,7 @@ const NameFields = () => {
   return h(NameFieldsView, Object.assign({}, props$1));
 };
 const NameFieldsWithErrors = () => {
-  return h(NameFieldsView, Object.assign({}, errorProps$8));
+  return h(NameFieldsView, Object.assign({}, errorProps$9));
 };
 
 const NameFields$1 = /*#__PURE__*/Object.freeze({
@@ -10614,7 +10735,7 @@ const CheckboxField_stories = {
     scenario: scenario$j,
   },
 };
-const defaultProps$a = {
+const defaultProps$b = {
   states: {
     registrationFormState: {
       validationErrors: {},
@@ -10655,35 +10776,35 @@ const defaultRegisterProps = {
     invalidEmailErrorMessage: "Must be a valid email address",
   },
 };
-const Default$b = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$a))));
-const DefaultChecked = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$a, { states: {
-    ...defaultProps$a.states,
+const Default$c = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$b))));
+const DefaultChecked = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$b, { states: {
+    ...defaultProps$b.states,
     checked: true,
   } }))));
-const CustomLabel = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$a, { content: {
-    ...defaultProps$a.content,
+const CustomLabel = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$b, { content: {
+    ...defaultProps$b.content,
     checkboxLabel: "I Agree",
   } }))));
-const Error$4 = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$a, { states: {
-    ...defaultProps$a.states,
+const Error$4 = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$b, { states: {
+    ...defaultProps$b.states,
     registrationFormState: {
       validationErrors: {
         agree: "Must be checked",
       },
     },
   } }))));
-const CustomError = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$a, { states: {
-    ...defaultProps$a.states,
+const CustomError = createHookStory(() => (h(CheckboxFieldView, Object.assign({}, defaultProps$b, { states: {
+    ...defaultProps$b.states,
     registrationFormState: {
       validationErrors: {
         agree: "Must be checked",
       },
     },
   }, content: {
-    ...defaultProps$a.content,
+    ...defaultProps$b.content,
     errorMessage: "This checkbox must be checked to continue",
   } }))));
-const TermsAndConditions$1 = createHookStory(() => (h(PortalRegisterView, Object.assign({}, defaultRegisterProps, { 
+const TermsAndConditions$2 = createHookStory(() => (h(PortalRegisterView, Object.assign({}, defaultRegisterProps, { 
   //@ts-ignore
   content: {
     ...defaultRegisterProps.content,
@@ -10710,16 +10831,34 @@ const TermsAndConditionsLongCustomLabel = createHookStory(() => (h(PortalRegiste
 const CheckboxField = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': CheckboxField_stories,
-  Default: Default$b,
+  Default: Default$c,
   DefaultChecked: DefaultChecked,
   CustomLabel: CustomLabel,
   Error: Error$4,
   CustomError: CustomError,
-  TermsAndConditions: TermsAndConditions$1,
+  TermsAndConditions: TermsAndConditions$2,
   TermsAndConditionsCustomLabel: TermsAndConditionsCustomLabel,
   TermsAndConditionsLongCustomLabel: TermsAndConditionsLongCustomLabel
 });
 
+const scenario$k = "@owner:zach\n@author:zach\nFeature: Marketing Emails Checkbox\n\n  A checkbox that is used to opt in for referral program marketing emails.\n\n    Background: A user is on the portal registration page\n        Given a user is viewing the \"/register\"\n        And \"/register\" contains the registration form\n        And the registration form has the following fields\n            | fields                      |\n            | first name                  |\n            | last name                   |\n            | email                       |\n            | password                    |\n            | Marketing Emails Checkbox   |\n    \n    @motivating\n    Scenario: Checkbox is optional by default\n        Given the user is filling out the registration form\n        And the name fields have valid input\n        And the email field has valid input\n        And the password field has valid input\n        And the checkbox is not checked\n        When they try to register\n        Then the form is submitted\n        And there is no error for the checkbox\n\n    Scenario: The form field name is provided by default\n        Given the customer has added a marketing emails checkbox to their registration form\n        Then the field name is automatically set to \"marketing-emails\"\n        And the name is configurable \n\n\n\n  ";
+
+const MarketingEmailsCheckbox_stories = {
+  title: "Components/Marketing Emails Checkbox",
+  parameters: {
+    scenario: scenario$k,
+  },
+};
+const Default$d = () => {
+  return h("sqm-marketing-emails-checkbox", null);
+};
+
+const MarketingEmailsCheckbox = /*#__PURE__*/Object.freeze({
+  __proto__: null,
+  'default': MarketingEmailsCheckbox_stories,
+  Default: Default$d
+});
+
 const UseCheckboxField_stories = {
   title: "Hooks / useCheckboxField",
   parameters: {
@@ -10749,7 +10888,7 @@ function setupGraphQL$9() {
   }, []);
   return { id, accountId };
 }
-const TermsAndConditions$2 = createHookStory(() => {
+const TermsAndConditions$3 = createHookStory(() => {
   setupGraphQL$9();
   return (h("sqm-portal-register", null,
     h("div", { slot: "terms" },
@@ -10787,7 +10926,7 @@ const MissingName = createHookStory(() => {
 const UseCheckboxField = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': UseCheckboxField_stories,
-  TermsAndConditions: TermsAndConditions$2,
+  TermsAndConditions: TermsAndConditions$3,
   TermsAndConditionsWithLabel: TermsAndConditionsWithLabel,
   MultipleCheckboxes: MultipleCheckboxes,
   OptionalCheckboxes: OptionalCheckboxes,
@@ -10797,7 +10936,7 @@ const UseCheckboxField = /*#__PURE__*/Object.freeze({
 const DropdownField_stories = {
   title: "Components/Dropdown Field",
 };
-const defaultProps$b = {
+const defaultProps$c = {
   states: {
     registrationFormState: {},
   },
@@ -10812,24 +10951,24 @@ const defaultProps$b = {
     ],
   },
 };
-const Default$c = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$b))));
-const CustomLabel$1 = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$b, { content: {
-    ...defaultProps$b.content,
+const Default$e = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$c))));
+const CustomLabel$1 = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$c, { content: {
+    ...defaultProps$c.content,
     dropdownLabel: "Pick your favorite",
   } }))));
-const Error$5 = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$b, { states: {
-    ...defaultProps$b.states,
+const Error$5 = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$c, { states: {
+    ...defaultProps$c.states,
     registrationFormState: {
       validationErrors: {
         options: "Must select an option",
       },
     },
   } }))));
-const CustomError$1 = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$b, { content: {
-    ...defaultProps$b.content,
+const CustomError$1 = createHookStory(() => (h(DropdownFieldView, Object.assign({}, defaultProps$c, { content: {
+    ...defaultProps$c.content,
     errorMessage: "An option must be selected to continue",
   }, states: {
-    ...defaultProps$b.states,
+    ...defaultProps$c.states,
     registrationFormState: {
       validationErrors: {
         options: "Must select an option",
@@ -10840,7 +10979,7 @@ const CustomError$1 = createHookStory(() => (h(DropdownFieldView, Object.assign(
 const DropdownField = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': DropdownField_stories,
-  Default: Default$c,
+  Default: Default$e,
   CustomLabel: CustomLabel$1,
   Error: Error$5,
   CustomError: CustomError$1
@@ -10905,15 +11044,15 @@ const UseDropdownField = /*#__PURE__*/Object.freeze({
   MissingName: MissingName$1
 });
 
-const scenario$k = "@author:derek\n@owner:derek\nFeature: Form Input Field\n\n    This component is used as a custom registration field during registration. The field can be text,\n    a date or phone number. A motivating use case is to ask for a users company name, this value would then be mapped\n    through the Managed Identity Service and upserted on the user after registration.\n\n    Background: A user exists and is viewing the hosted portal registration\n        Given a user is viewing \"/register\"\n        And \"/register\" contains the registration form\n        And the registration form has a custom input field\n\n    @motivating\n    Scenario Outline: Input fields are required by default but can be optional\n        Given the input has prop \"field-optional\" with <value>\n        And the input is empty\n        When the user tries to register\n        Then the input <mayBe> highlighted in red\n        And an error message <mayAppear> in red below\n        And form submission <mayBe> blocked\n        Examples:\n            | value | mayBe | mayAppear      |\n            | false | is    | appears        |\n            |       | is    | appears        |\n            | true  | isn't | doesn't appear |\n\n    @motivating\n    Scenario: Input field labels are configurable\n        Given the input has prop \"field-label\" with value \"My Custom Input\"\n        When the user views the registration form\n        Then they see the input field\n        And it has label \"My Custom Input\" above the input\n\n    @minutia\n    Scenario Outline: The validation error message is configurable\n        The error message string is evaluated as an ICU string, but currently is provided no context\n        Given the input is required\n        And it has prop \"error-message\" with <value>\n        When the user tries to register\n        But they haven't filled in the input\n        Then they see <errorMessage> below\n        Examples:\n            | value             | errorMessage      |\n            |                   | Cannot be empty   |\n            | My Custom Message | My Custom Message |\n\n    @motivating\n    Scenario: Form data attribute name is configurable\n        Given the input has prop \"field-name\" with value \"myCustomField\"\n        When the user types \"testing testing\" into the input\n        And they register\n        Then \"testing testing\" is submitted under \"myCustomField\" in the form data\n\n    @motivating\n    Scenario Outline: The input field is a text input by default\n        Given the input <mayHave> prop \"field-type\" with <value>\n        When the user views the input field\n        Then it is a text input\n        Examples:\n            | mayHave      | value |\n            | has          | text  |\n            | doesn't have |       |\n\n    @motivating\n    Scenario: Date type inputs are supported\n        Given the input has prop \"field-type\" \"date\"\n        When the user views the input field\n        Then they see \"mm/dd/yyyy\" as a placeholder\n        And they see a calendar icon on the right\n        When they start typing a date\n        Then it maintains the \"mm/dd/yyyy\" format\n        When they click the calendar icon\n        Then a dropdown appears\n        And they see a calendar\n        When they select a date\n        Then it is applied to the input\n\n    @landmine\n    Scenario: The clear text button in the date picker does not clear the date\n        Due to an incompatibility between our shoelace version and the browser, the clear funtionality is not supported currently\n        Given the input has prop \"field-type\" \"date\"\n        And the user has entered a date\n        When they click the calendar icon\n        And click the 'clear' text button\n        Then their selected date is not cleared\n\n    @motivating\n    Scenario: Phone number type inputs are supported\n        Given the input has prop \"field-type\" with value \"tel\"\n        When the user starts typing a phone number in the input\n        Then it is formatted into the following form \"(XXX) XXX-XXXX\"\n        When they pre-fix their phone number with a \"1\"\n        Then it is formatted into the following form \"1 (XXX) XXX-XXXX\"\n\n    @landmine\n    Scenario: Telephone formatting is removed after 10 numbers\n        Given a user using a phone number input field\n        And they entered their 10 character phone number\n        And it was not prefixed with a 1\n        When they add another character\n        Then the formatting is removed\n\n    @landmine\n    Scenario Outline: Input values are always recorded as strings in the form data\n        Given the input has prop \"field-type\" with <value>\n        And it has a \"field-name\"\n        When the user inputs <formInput>\n        And they register\n        Then <formData> is recorded in the form data as a string\n        Examples:\n            | value | formInput      | formData       |\n            | text  | Hello there    | Hello there    |\n            | date  | 05/07/2021     | 2021-05-07     |\n            | tel   | (250) 234-9877 | (250) 234-9877 |\n\n    @minutia\n    Scenario Outline: The input field component fails fast if a field name isn't provided\n        Given the input <mayHave> prop \"field-name\"\n        And it <mayHavePropValue>\n        When a user views the input\n        Then an alert with an error message is displayed in place of the input\n        And it has a details section\n        When \"More details\" is clicked\n        Then the following information is displayed\n            | information          |\n            | component being used |\n            | missing attribute(s) |\n        Examples:\n            | mayBeAnAttribute | mayHavePropValue |\n            | doesn't have     | N/A              |\n            | has              | \"\"               |\n            | has              |                  |";
+const scenario$l = "@author:derek\n@owner:derek\nFeature: Form Input Field\n\n    This component is used as a custom registration field during registration. The field can be text,\n    a date or phone number. A motivating use case is to ask for a users company name, this value would then be mapped\n    through the Managed Identity Service and upserted on the user after registration.\n\n    Background: A user exists and is viewing the hosted portal registration\n        Given a user is viewing \"/register\"\n        And \"/register\" contains the registration form\n        And the registration form has a custom input field\n\n    @motivating\n    Scenario Outline: Input fields are required by default but can be optional\n        Given the input has prop \"field-optional\" with <value>\n        And the input is empty\n        When the user tries to register\n        Then the input <mayBe> highlighted in red\n        And an error message <mayAppear> in red below\n        And form submission <mayBe> blocked\n        Examples:\n            | value | mayBe | mayAppear      |\n            | false | is    | appears        |\n            |       | is    | appears        |\n            | true  | isn't | doesn't appear |\n\n    @motivating\n    Scenario: Input field labels are configurable\n        Given the input has prop \"field-label\" with value \"My Custom Input\"\n        When the user views the registration form\n        Then they see the input field\n        And it has label \"My Custom Input\" above the input\n\n    @minutia\n    Scenario Outline: The validation error message is configurable\n        The error message string is evaluated as an ICU string, but currently is provided no context\n        Given the input is required\n        And it has prop \"error-message\" with <value>\n        When the user tries to register\n        But they haven't filled in the input\n        Then they see <errorMessage> below\n        Examples:\n            | value             | errorMessage      |\n            |                   | Cannot be empty   |\n            | My Custom Message | My Custom Message |\n\n    @motivating\n    Scenario: Form data attribute name is configurable\n        Given the input has prop \"field-name\" with value \"myCustomField\"\n        When the user types \"testing testing\" into the input\n        And they register\n        Then \"testing testing\" is submitted under \"myCustomField\" in the form data\n\n    @motivating\n    Scenario Outline: The input field is a text input by default\n        Given the input <mayHave> prop \"field-type\" with <value>\n        When the user views the input field\n        Then it is a text input\n        Examples:\n            | mayHave      | value |\n            | has          | text  |\n            | doesn't have |       |\n\n    @motivating\n    Scenario: Date type inputs are supported\n        Given the input has prop \"field-type\" \"date\"\n        When the user views the input field\n        Then they see \"mm/dd/yyyy\" as a placeholder\n        And they see a calendar icon on the right\n        When they start typing a date\n        Then it maintains the \"mm/dd/yyyy\" format\n        When they click the calendar icon\n        Then a dropdown appears\n        And they see a calendar\n        When they select a date\n        Then it is applied to the input\n\n    @landmine\n    Scenario: The clear text button in the date picker does not clear the date\n        Due to an incompatibility between our shoelace version and the browser, the clear funtionality is not supported currently\n        Given the input has prop \"field-type\" \"date\"\n        And the user has entered a date\n        When they click the calendar icon\n        And click the 'clear' text button\n        Then their selected date is not cleared\n\n    @motivating\n    Scenario: Phone number type inputs are supported\n        Given the input has prop \"field-type\" with value \"tel\"\n        When the user starts typing a phone number in the input\n        Then it is formatted into the following form \"(XXX) XXX-XXXX\"\n        When they pre-fix their phone number with a \"1\"\n        Then it is formatted into the following form \"1 (XXX) XXX-XXXX\"\n\n    @landmine\n    Scenario: Telephone formatting is removed after 10 numbers\n        Given a user using a phone number input field\n        And they entered their 10 character phone number\n        And it was not prefixed with a 1\n        When they add another character\n        Then the formatting is removed\n\n    @landmine\n    Scenario Outline: Input values are always recorded as strings in the form data\n        Given the input has prop \"field-type\" with <value>\n        And it has a \"field-name\"\n        When the user inputs <formInput>\n        And they register\n        Then <formData> is recorded in the form data as a string\n        Examples:\n            | value | formInput      | formData       |\n            | text  | Hello there    | Hello there    |\n            | date  | 05/07/2021     | 2021-05-07     |\n            | tel   | (250) 234-9877 | (250) 234-9877 |\n\n    @minutia\n    Scenario Outline: The input field component fails fast if a field name isn't provided\n        Given the input <mayHave> prop \"field-name\"\n        And it <mayHavePropValue>\n        When a user views the input\n        Then an alert with an error message is displayed in place of the input\n        And it has a details section\n        When \"More details\" is clicked\n        Then the following information is displayed\n            | information          |\n            | component being used |\n            | missing attribute(s) |\n        Examples:\n            | mayBeAnAttribute | mayHavePropValue |\n            | doesn't have     | N/A              |\n            | has              | \"\"               |\n            | has              |                  |";
 
 const InputField_stories = {
   title: "Components/Input Field",
   parameters: {
-    scenario: scenario$k,
+    scenario: scenario$l,
   },
 };
-const defaultProps$c = {
+const defaultProps$d = {
   states: {
     registrationFormState: {
       validationErrors: {},
@@ -10950,21 +11089,21 @@ const defaultRegisterProps$1 = {
     invalidEmailErrorMessage: "Must be a valid email address",
   },
 };
-const Default$d = () => h(InputFieldView, Object.assign({}, defaultProps$c));
-const CustomLabel$2 = () => (h(InputFieldView, Object.assign({}, defaultProps$c, { content: { ...defaultProps$c.content, fieldLabel: "My Label" } })));
-const Error$6 = () => (h(InputFieldView, Object.assign({}, defaultProps$c, { states: {
-    ...defaultProps$c.states,
+const Default$f = () => h(InputFieldView, Object.assign({}, defaultProps$d));
+const CustomLabel$2 = () => (h(InputFieldView, Object.assign({}, defaultProps$d, { content: { ...defaultProps$d.content, fieldLabel: "My Label" } })));
+const Error$6 = () => (h(InputFieldView, Object.assign({}, defaultProps$d, { states: {
+    ...defaultProps$d.states,
     registrationFormState: {
       validationErrors: {
         field: "Cannot be empty",
       },
     },
   } })));
-const CustomError$2 = () => (h(InputFieldView, Object.assign({}, defaultProps$c, { content: {
-    ...defaultProps$c.content,
+const CustomError$2 = () => (h(InputFieldView, Object.assign({}, defaultProps$d, { content: {
+    ...defaultProps$d.content,
     errorMessage: "A value must be entered to continue",
   }, states: {
-    ...defaultProps$c.states,
+    ...defaultProps$d.states,
     registrationFormState: {
       validationErrors: {
         field: "Cannot be empty",
@@ -10972,27 +11111,27 @@ const CustomError$2 = () => (h(InputFieldView, Object.assign({}, defaultProps$c,
     },
   } })));
 const DateType = () => {
-  return (h(InputFieldView, Object.assign({}, defaultProps$c, { content: {
-      ...defaultProps$c.content,
+  return (h(InputFieldView, Object.assign({}, defaultProps$d, { content: {
+      ...defaultProps$d.content,
       fieldLabel: "Date",
       fieldType: "date",
     } })));
 };
 const TelType = () => {
-  return (h(InputFieldView, Object.assign({}, defaultProps$c, { content: {
-      ...defaultProps$c.content,
+  return (h(InputFieldView, Object.assign({}, defaultProps$d, { content: {
+      ...defaultProps$d.content,
       fieldLabel: "Phone Number",
       fieldType: "tel",
     } })));
 };
 const RegistrationField = () => (h(PortalRegisterView, Object.assign({}, defaultRegisterProps$1, { content: {
     ...defaultRegisterProps$1.content,
-    formData: h(InputFieldView, Object.assign({}, defaultProps$c)),
+    formData: h(InputFieldView, Object.assign({}, defaultProps$d)),
   } })));
 const RegistrationFieldCustomLabel = () => (h(PortalRegisterView, Object.assign({}, defaultRegisterProps$1, { content: {
     ...defaultRegisterProps$1.content,
-    formData: (h(InputFieldView, Object.assign({}, defaultProps$c, { content: {
-        ...defaultProps$c.content,
+    formData: (h(InputFieldView, Object.assign({}, defaultProps$d, { content: {
+        ...defaultProps$d.content,
         fieldLabel: "Data",
       } }))),
   } })));
@@ -11000,7 +11139,7 @@ const RegistrationFieldCustomLabel = () => (h(PortalRegisterView, Object.assign(
 const InputField = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': InputField_stories,
-  Default: Default$d,
+  Default: Default$f,
   CustomLabel: CustomLabel$2,
   Error: Error$6,
   CustomError: CustomError$2,
@@ -11013,7 +11152,7 @@ const InputField = /*#__PURE__*/Object.freeze({
 const UseInputField_stories = {
   title: "Hooks / useInputField",
   parameters: {
-    scenario: scenario$k,
+    scenario: scenario$l,
   },
 };
 function setupGraphQL$b() {
@@ -11095,12 +11234,12 @@ const UseInputField = /*#__PURE__*/Object.freeze({
   MissingName: MissingName$2
 });
 
-const scenario$l = "@author:derek\n@owner:derek\nFeature: Reward Exchange List\n\n    The Reward Exchange List gives end users the power to exchange their rewards for other rewards.\n    It populates a list from the reward exchange rules set up on a given tenant.\n\n    Background:\n        Given a tenant with reward exchange rules\n\n    @motivating\n    @ui\n    Scenario: The empty state is shown if there are no visible exchanges\n        Given a user with no visible exchanges\n        When they view the reward exchange\n        Then no exchange options are displayed\n        And they see an image of a present\n        And \"Redeem Rewards\" in bold\n        And \"Use your points to redeem rewards once they become available\" below the bolded text\n        And the pagination buttons are disabled\n\n    @minutia\n    @ui\n    Scenario: A custom empty state can be provided\n        Given a user with no visible exchanges\n        And a custom empty state has been supplied in the \"empty\" slot\n        When they view the reward exchange\n        Then they see the custom empty state\n\n    @motivating\n    @ui\n    Scenario: A Loading Skeleton is displayed when the reward exchange rules are loading\n        Given a user\n        When they load the reward exchange list\n        Then they see a loading Skeleton\n        And it has 8 skeleton cards\n        When the reward exchange rules have loaded\n        Then the skeleton is replaced with reward exchange options\n\n    @motivating\n    Scenario: An error banner appears when the reward exchange list fails to load\n        Given a user trying to view the reward exchange list\n        But it fails to load\n        Then an error banner is displayed\n        And it displays \"Unable to load reward exchange list. Please try again\"\n\n    @motivating\n    @ui\n    Scenario: The exchange progress bar progresses through the exchange process\n        Given a user who is eligible for the tenants reward exchange rules\n        When they view the reward exchange list\n        Then the process bar displays the following elements\n            | elements                                                           |\n            | Step 1 `Rewards` title in black                                    |\n            | Step 1 circle with green outline, white fill and number 1 in green |\n            | Step 2 `Select` title in grey                                      |\n            | Step 2 circle with grey fill and number 2 in white                 |\n            | Step 3 `Confirm` title in grey                                     |\n            | Step 3 circle with grey fill and number 3 in white                 |\n            | lines between all steps are greyed out                             |\n        When they continue to the selection page\n        Then the progress bar displays the following elements\n            | elements                                                           |\n            | Step 1 `Rewards` title in black                                    |\n            | Step 1 circle with white checkmark and green fill                  |\n            | Step 2 `Select` title in black                                     |\n            | Step 2 circle with green outline, white fill and number 2 in green |\n            | Step 3 `Confirm` title in grey                                     |\n            | Step 3 circle with grey fill and number 3 in white                 |\n            | Green line between step 1 and 2                                    |\n            | Grey line between step 2 and 3                                     |\n        When they continue to the confirmation page\n        Then the progress bar displays the following elements\n            | elements                                                           |\n            | Step 1 `Rewards` title in black                                    |\n            | Step 1 circle with white checkmark and green fill                  |\n            | Step 2 `Select` title in black                                     |\n            | Step 2 circle with white checkmark and green fill                  |\n            | Step 3 `Confirm` title in black                                    |\n            | Step 3 circle with green outline, white fill and number 3 in green |\n            | Green line between all steps                                       |\n        When they continue to the redemption page\n        Then the progress bar displays the following elements\n            | elements                                          |\n            | Step 1 `Rewards` title in black                   |\n            | Step 1 circle with white checkmark and green fill |\n            | Step 2 `Select` title in black                    |\n            | Step 2 circle with white checkmark and green fill |\n            | Step 3 `Confirm` title in black                   |\n            | Step 3 circle with white checkmark and green fill |\n            | Green line between all steps                      |\n\n    @motivating\n    Scenario: Users must choose a reward exchange option to continue to the selection page\n        Given a user who is eligible for the tenants reward exchange rules\n        When they view the reward exchange list\n        Then the 'Continue' button is disabled\n        When they select a reward exchange card\n        Then the card is outlined in brand colour with a brand colour cirlcular check box icon in the top right\n        And the continue button is no longer disabled\n        When they click \"Continue\"\n        Then they are brought to the selection page\n\n    @motivating\n    @ui\n    Scenario: Reward exchange rule names and images are used in the reward exchange cards\n        Given a tenant reward exchange rule\n        And it has name \"My Visa Exchange Rule\"\n        And it has an image\n        When a user views the reward exchange list\n        Then they see a exchange card with title \"My Visa Exchange Rule\"\n        And the exchange image on the left hand side of the card\n\n    @motivating\n    Scenario Outline: Reward exchange source values are displayed on reward exchange cards\n        Given a <type> reward exchange rule\n        When a user views the reward exchange list\n        Then they see <text> under the name on the exchange option cards\n        And the pretty values are localized to a user locale\n        Examples:\n            | type                        | text                                                                |\n            | FIXED_GLOBAL_REWARD         | the exchange source pretty value                                    |\n            | STEPPED_FIXED_GLOBAL_REWARD | the exchange source min pretty value to the source max pretty value |\n            | VARIABLE_GLOBAL_REWARD      | the exchange source min pretty value to the source max pretty value |\n            | VARIABLE_CREDIT_REWARD      | the exchange source min pretty value to the source max pretty value |\n\n    @motivating\n    Scenario Outline: Reward exchange cards can display customized error messages\n        Given a reward exchange rule\n        And it has <availabilityPredicate>\n        And the reward exchange list has prop \"not-available-error\" with <value>\n        When the user views the reward exchange list\n        Then the card for the reward exchange rule is disabled\n        And <message> is displayed\n        Examples:\n            | availabilityPredicate                                         | value                                                                                                           | message                         |\n            | 'champion' in user.segments ? \"NOT_CHAMPION\" : true           | {unavailableReasonCode, select, NOT_CHAMPION {Sorry must be a champion!} other {unavailableReasonCode} }        | Sorry must be a champion!       |\n            | user.customFields.purchaseCount < 10 ? \"MORE_PURCHASE\" : true | {unavailableReasonCode, select, MORE_PURCHASE {Complete 10 purchases to unlock} other {unavailableReasonCode} } | Complete 10 purchases to unlock |\n\n    @motivating\n    Scenario: Exchange options are disabled if they put a user over the W9 limit\n        Given a user who is approaching their W9 limit\n        And a reward exchange rule\n        And its destination reward has a US taxable value that would put the user over their limit\n        When they view the reward exchange list\n        Then the reward exchange card is disabled\n        And a \"US Tax Limit\" error message is displayed on to the right of a exclamation triangle icon\n        And the text is orange\n        And the icon is orange\n\n    @motivating\n    Scenario Outline: Exchange options are disabled if a users lacks enough credit to redeem\n        Given a <type> reward exchange rule\n        But the user lacks enough credit to exchange for it\n        When they view the reward exchange list\n        Then the reward exchange card is disabled\n        And a <text> error message is displayed on to the right of a exclamation triangle icon\n        And the text is orange\n        And the icon is orange\n        Examples:\n            | type                        | text                            |\n            | FIXED_GLOBAL_REWARD         | {prettySourceValue} required    |\n            | STEPPED_FIXED_GLOBAL_REWARD | {prettySourceMinValue} required |\n            | VARIABLE_GLOBAL_REWARD      | {prettySourceMinValue} required |\n            | VARIABLE_CREDIT_REWARD      | {prettySourceMinValue} required |\n\n    @motivating\n    Scenario: Users can go back to the Rewards page from the Select page\n        Given a user viewing the Select page\n        Then they see a \"Cancel\" text button\n        And a \"Continue to confirmation\" brand colour button in the bottom right corner\n        When they click \"Cancel\"\n        Then they return to the Rewards page\n\n    @motivating\n    Scenario: Users can go back to the Select Page from the Confirm page\n        Given a user viewing the Confirm page\n        Then they see a \"Back\" text button\n        And a \"Redeem\" brand colour button in the bottom right corner\n        When they click \"Back\"\n        Then they return to the Select Page\n\n    @motivating\n    Scenario: Reward rules with visibility predicates that evaluates to false are not shown\n        Given a tenant reward exchange rule with visibility predicates that evaluates to false\n        When a user views the reward exchange list\n        Then they do not see the card for that reward exchange rule\n\n    @motivating\n    Scenario Outline: Users can choose their reward option for variable rewards on the Select page\n        Given a <type> exchange rule\n        And it has the following fields\n            | fields      |\n            | name        |\n            | description |\n            | image       |\n        When a user views the reward exchange list\n        And they progress to the Select page for this exchange\n        Then they see the exchange rule image on the left hand side\n        And on the right hand side they see the following in this order from top to bottom\n            | elements                                                                                          |\n            | exchange name                                                                                     |\n            | exchange description                                                                              |\n            | select list with all exchange options using pretty values, destination reward above source reward |\n        Examples:\n            | type                        |\n            | STEPPED_FIXED_GLOBAL_REWARD |\n            | VARIABLE_GLOBAL_REWARD      |\n            | VARIABLE_CREDIT_REWARD      |\n\n    @motivating\n    Scenario: Users who selected a fixed exchange rule see exchange information on the Select page\n        Given a \"FIXED_GLOBAL_REWARD\" exchange rule\n        And it has the following fields\n            | fields      |\n            | name        |\n            | description |\n            | image       |\n        When a user views the reward exchange list\n        And they progress to the Select page for this exchange\n        Then they see the exchange rule image on the left hand side\n        And on the right hand side they see the following in this order from top to bottom\n            | elements                                               |\n            | exchange name                                          |\n            | exchange source pretty value displayed in brand colour |\n            | exchange description                                   |\n\n    @motivating\n    Scenario Outline: Users selection variable rewards can only select rewards they are eligible to exchange for\n        Given a <type> exchange rule\n        When a user views the reward exchange list\n        And they progress to the Select page for this exchange\n        Then they see a drop down with all the reward exchange selections\n        When they click on the drop down\n        But they are not eligible for all of the exchanges options <dueToReason>\n        Then the ineligble options are disabled\n        And under the source value is <text>\n        Examples:\n            | type                        | dueToReason                     | text                         |\n            | STEPPED_FIXED_GLOBAL_REWARD | due to insufficent source value | {prettySourceValue} required |\n            | VARIABLE_GLOBAL_REWARD      | due to insufficent source value | {prettySourceValue} required |\n            | VARIABLE_CREDIT_REWARD      | due to insufficent source value | {prettySourceValue} required |\n            | STEPPED_FIXED_GLOBAL_REWARD | W9                              | US Tax Limit                 |\n            | VARIABLE_GLOBAL_REWARD      | W9                              | US Tax Limit                 |\n            | VARIABLE_CREDIT_REWARD      | W9                              | US Tax Limit                 |\n\n    @motivating\n    Scenario Outline: The Confirm page allows users to view their exchange before committing\n        Given a <type> exchange rule\n        When a user views the reward exchange list\n        And they select the exchange\n        And they progress to Confirm page\n        Then they see a row with title \"Reward\"\n        And it contains the exchange name\n        And it contains the exchange image\n        And they <maySee> a row with title \"Reward Amount\"\n        And it <mayContain> <amountTitle>\n        And they see a row with title \"Cost to Redeem\"\n        And it contains the source reward pretty value in bolded text\n        Examples:\n            | type                        | maySee | mayContain      | amountTitle                  |\n            | FIXED_GLOBAL_REWARD         | don't  | doesn't contain | N/A                          |\n            | VARIABLE_GLOBAL_REWARD      | see    | contains        | the pretty destination value |\n            | STEPPED_FIXED_GLOBAL_REWARD | see    | contains        | the pretty destination value |\n            | VARIABLE_CREDIT_REWARD      | see    | contains        | the pretty destination value |\n\n    @motivating\n    Scenario: An error banner is displayed if an error occurs during redemeption\n        Given a user has selected a reward to exchange\n        And is on the confirmation page\n        When they click \"Redeem\"\n        But an error occurs\n        Then an error banner appears\n        And it contains details about the error\n        And the reward exchange is not completed\n\n    @motivating\n    Scenario: Confetti is displayed when a reward exchange succeeds\n        Given a user has selected a reward to exchange\n        And they are on the confirmation page\n        When they click \"Redeem\"\n        And the exchange is successful\n        Then they see confetti centered on the success page\n        And they see text describing what they exchanged for their new reward\n        And they see a \"Done\" brand colour button\n        When they click \"Done\"\n        Then they see the Rewards page\n\n    @motivating\n    Scenario: Fuel tank codes are shown when a reward exchange succeeds\n        Given a user has selected to exchange for a fuel tank reward\n        When they complete the reward exchange\n        And are on the success page\n        Then they see a textbox with their fuel tank code\n        And a clipboard icon\n        When they click the clipboard icon\n        Then their fuel tank code is copied to their clipboard\n\n    @motivating\n    Scenario Outline: Users can exchange for any type of reward\n        Given a <type> reward exchange rule for a <reward>\n        And a user who has enough source credit to exchange for the reward\n        When they go through the exchange flow\n        And exchange for their reward\n        Then their credit is exchanged for the <reward>\n        Examples:\n            | type                        | reward         |\n            | FIXED_GLOBAL_REWARD         | gift card      |\n            | FIXED_GLOBAL_REWARD         | fuel tank code |\n            | FIXED_GLOBAL_REWARD         | discount       |\n            | FIXED_GLOBAL_REWARD         | credit reward  |\n            | STEPPED_FIXED_GLOBAL_REWARD | gift card      |\n            | STEPPED_FIXED_GLOBAL_REWARD | discount       |\n            | STEPPED_FIXED_GLOBAL_REWARD | credit reward  |\n            | VARIABLE_GLOBAL_REWARD      | gift card      |\n            | VARIABLE_GLOBAL_REWARD      | discount       |\n            | VARIABLE_GLOBAL_REWARD      | credit reward  |\n            | VARIABLE_CREDIT_REWARD      | credit reward  |";
+const scenario$m = "@author:derek\n@owner:derek\nFeature: Reward Exchange List\n\n    The Reward Exchange List gives end users the power to exchange their rewards for other rewards.\n    It populates a list from the reward exchange rules set up on a given tenant.\n\n    Background:\n        Given a tenant with reward exchange rules\n\n    @motivating\n    @ui\n    Scenario: The empty state is shown if there are no visible exchanges\n        Given a user with no visible exchanges\n        When they view the reward exchange\n        Then no exchange options are displayed\n        And they see an image of a present\n        And \"Redeem Rewards\" in bold\n        And \"Use your points to redeem rewards once they become available\" below the bolded text\n        And the pagination buttons are disabled\n\n    @minutia\n    @ui\n    Scenario: A custom empty state can be provided\n        Given a user with no visible exchanges\n        And a custom empty state has been supplied in the \"empty\" slot\n        When they view the reward exchange\n        Then they see the custom empty state\n\n    @motivating\n    @ui\n    Scenario: A Loading Skeleton is displayed when the reward exchange rules are loading\n        Given a user\n        When they load the reward exchange list\n        Then they see a loading Skeleton\n        And it has 8 skeleton cards\n        When the reward exchange rules have loaded\n        Then the skeleton is replaced with reward exchange options\n\n    @motivating\n    Scenario: An error banner appears when the reward exchange list fails to load\n        Given a user trying to view the reward exchange list\n        But it fails to load\n        Then an error banner is displayed\n        And it displays \"Unable to load reward exchange list. Please try again\"\n\n    @motivating\n    @ui\n    Scenario: The exchange progress bar progresses through the exchange process\n        Given a user who is eligible for the tenants reward exchange rules\n        When they view the reward exchange list\n        Then the process bar displays the following elements\n            | elements                                                           |\n            | Step 1 `Rewards` title in black                                    |\n            | Step 1 circle with green outline, white fill and number 1 in green |\n            | Step 2 `Select` title in grey                                      |\n            | Step 2 circle with grey fill and number 2 in white                 |\n            | Step 3 `Confirm` title in grey                                     |\n            | Step 3 circle with grey fill and number 3 in white                 |\n            | lines between all steps are greyed out                             |\n        When they continue to the selection page\n        Then the progress bar displays the following elements\n            | elements                                                           |\n            | Step 1 `Rewards` title in black                                    |\n            | Step 1 circle with white checkmark and green fill                  |\n            | Step 2 `Select` title in black                                     |\n            | Step 2 circle with green outline, white fill and number 2 in green |\n            | Step 3 `Confirm` title in grey                                     |\n            | Step 3 circle with grey fill and number 3 in white                 |\n            | Green line between step 1 and 2                                    |\n            | Grey line between step 2 and 3                                     |\n        When they continue to the confirmation page\n        Then the progress bar displays the following elements\n            | elements                                                           |\n            | Step 1 `Rewards` title in black                                    |\n            | Step 1 circle with white checkmark and green fill                  |\n            | Step 2 `Select` title in black                                     |\n            | Step 2 circle with white checkmark and green fill                  |\n            | Step 3 `Confirm` title in black                                    |\n            | Step 3 circle with green outline, white fill and number 3 in green |\n            | Green line between all steps                                       |\n        When they continue to the redemption page\n        Then the progress bar displays the following elements\n            | elements                                          |\n            | Step 1 `Rewards` title in black                   |\n            | Step 1 circle with white checkmark and green fill |\n            | Step 2 `Select` title in black                    |\n            | Step 2 circle with white checkmark and green fill |\n            | Step 3 `Confirm` title in black                   |\n            | Step 3 circle with white checkmark and green fill |\n            | Green line between all steps                      |\n\n    @motivating\n    Scenario: Users must choose a reward exchange option to continue to the selection page\n        Given a user who is eligible for the tenants reward exchange rules\n        When they view the reward exchange list\n        Then the 'Continue' button is disabled\n        When they select a reward exchange card\n        Then the card is outlined in brand colour with a brand colour cirlcular check box icon in the top right\n        And the continue button is no longer disabled\n        When they click \"Continue\"\n        Then they are brought to the selection page\n\n    @motivating\n    @ui\n    Scenario: Reward exchange rule names and images are used in the reward exchange cards\n        Given a tenant reward exchange rule\n        And it has name \"My Visa Exchange Rule\"\n        And it has an image\n        When a user views the reward exchange list\n        Then they see a exchange card with title \"My Visa Exchange Rule\"\n        And the exchange image on the left hand side of the card\n\n    @motivating\n    Scenario Outline: Reward exchange source values are displayed on reward exchange cards\n        Given a <type> reward exchange rule\n        When a user views the reward exchange list\n        Then they see <text> under the name on the exchange option cards\n        And the pretty values are localized to a user locale\n        Examples:\n            | type                        | text                                                                |\n            | FIXED_GLOBAL_REWARD         | the exchange source pretty value                                    |\n            | STEPPED_FIXED_GLOBAL_REWARD | the exchange source min pretty value to the source max pretty value |\n            | VARIABLE_GLOBAL_REWARD      | the exchange source min pretty value to the source max pretty value |\n            | VARIABLE_CREDIT_REWARD      | the exchange source min pretty value to the source max pretty value |\n\n    @motivating\n    Scenario Outline: Reward exchange cards can display customized error messages\n        Given a reward exchange rule\n        And it has <availabilityPredicate>\n        And the reward exchange list has prop \"not-available-error\" with <value>\n        When the user views the reward exchange list\n        Then the card for the reward exchange rule is disabled\n        And <message> is displayed\n        Examples:\n            | availabilityPredicate                                         | value                                                                                                           | message                         |\n            | 'champion' in user.segments ? \"NOT_CHAMPION\" : true           | {unavailableReasonCode, select, NOT_CHAMPION {Sorry must be a champion!} other {unavailableReasonCode} }        | Sorry must be a champion!       |\n            | user.customFields.purchaseCount < 10 ? \"MORE_PURCHASE\" : true | {unavailableReasonCode, select, MORE_PURCHASE {Complete 10 purchases to unlock} other {unavailableReasonCode} } | Complete 10 purchases to unlock |\n\n    @motivating\n    Scenario: Exchange options are disabled if they put a user over the W9 limit\n        Given a user who is approaching their W9 limit\n        And a reward exchange rule\n        And its destination reward has a US taxable value that would put the user over their limit\n        When they view the reward exchange list\n        Then the reward exchange card is disabled\n        And a \"US Tax Limit\" error message is displayed on to the right of a exclamation triangle icon\n        And the text is orange\n        And the icon is orange\n\n    @motivating\n    Scenario Outline: Exchange options are disabled if a users lacks enough credit to redeem\n        Given a <type> reward exchange rule\n        But the user lacks enough credit to exchange for it\n        When they view the reward exchange list\n        Then the reward exchange card is disabled\n        And a <text> error message is displayed on to the right of a exclamation triangle icon\n        And the text is orange\n        And the icon is orange\n        Examples:\n            | type                        | text                            |\n            | FIXED_GLOBAL_REWARD         | {prettySourceValue} required    |\n            | STEPPED_FIXED_GLOBAL_REWARD | {prettySourceMinValue} required |\n            | VARIABLE_GLOBAL_REWARD      | {prettySourceMinValue} required |\n            | VARIABLE_CREDIT_REWARD      | {prettySourceMinValue} required |\n\n    @motivating\n    Scenario: Users can go back to the Rewards page from the Select page\n        Given a user viewing the Select page\n        Then they see a \"Cancel\" text button\n        And a \"Continue to confirmation\" brand colour button in the bottom right corner\n        When they click \"Cancel\"\n        Then they return to the Rewards page\n\n    @motivating\n    Scenario: Users can go back to the Select Page from the Confirm page\n        Given a user viewing the Confirm page\n        Then they see a \"Back\" text button\n        And a \"Redeem\" brand colour button in the bottom right corner\n        When they click \"Back\"\n        Then they return to the Select Page\n\n    @motivating\n    Scenario: Reward rules with visibility predicates that evaluates to false are not shown\n        Given a tenant reward exchange rule with visibility predicates that evaluates to false\n        When a user views the reward exchange list\n        Then they do not see the card for that reward exchange rule\n\n    @motivating\n    Scenario Outline: Users can choose their reward option for variable rewards on the Select page\n        Given a <type> exchange rule\n        And it has the following fields\n            | fields      |\n            | name        |\n            | description |\n            | image       |\n        When a user views the reward exchange list\n        And they progress to the Select page for this exchange\n        Then they see the exchange rule image on the left hand side\n        And on the right hand side they see the following in this order from top to bottom\n            | elements                                                                                          |\n            | exchange name                                                                                     |\n            | exchange description                                                                              |\n            | select list with all exchange options using pretty values, destination reward above source reward |\n        Examples:\n            | type                        |\n            | STEPPED_FIXED_GLOBAL_REWARD |\n            | VARIABLE_GLOBAL_REWARD      |\n            | VARIABLE_CREDIT_REWARD      |\n\n    @motivating\n    Scenario: Users who selected a fixed exchange rule see exchange information on the Select page\n        Given a \"FIXED_GLOBAL_REWARD\" exchange rule\n        And it has the following fields\n            | fields      |\n            | name        |\n            | description |\n            | image       |\n        When a user views the reward exchange list\n        And they progress to the Select page for this exchange\n        Then they see the exchange rule image on the left hand side\n        And on the right hand side they see the following in this order from top to bottom\n            | elements                                               |\n            | exchange name                                          |\n            | exchange source pretty value displayed in brand colour |\n            | exchange description                                   |\n\n    @motivating\n    Scenario Outline: Users selection variable rewards can only select rewards they are eligible to exchange for\n        Given a <type> exchange rule\n        When a user views the reward exchange list\n        And they progress to the Select page for this exchange\n        Then they see a drop down with all the reward exchange selections\n        When they click on the drop down\n        But they are not eligible for all of the exchanges options <dueToReason>\n        Then the ineligble options are disabled\n        And under the source value is <text>\n        Examples:\n            | type                        | dueToReason                     | text                         |\n            | STEPPED_FIXED_GLOBAL_REWARD | due to insufficent source value | {prettySourceValue} required |\n            | VARIABLE_GLOBAL_REWARD      | due to insufficent source value | {prettySourceValue} required |\n            | VARIABLE_CREDIT_REWARD      | due to insufficent source value | {prettySourceValue} required |\n            | STEPPED_FIXED_GLOBAL_REWARD | W9                              | US Tax Limit                 |\n            | VARIABLE_GLOBAL_REWARD      | W9                              | US Tax Limit                 |\n            | VARIABLE_CREDIT_REWARD      | W9                              | US Tax Limit                 |\n\n    @motivating\n    Scenario Outline: The Confirm page allows users to view their exchange before committing\n        Given a <type> exchange rule\n        When a user views the reward exchange list\n        And they select the exchange\n        And they progress to Confirm page\n        Then they see a row with title \"Reward\"\n        And it contains the exchange name\n        And it contains the exchange image\n        And they <maySee> a row with title \"Reward Amount\"\n        And it <mayContain> <amountTitle>\n        And they see a row with title \"Cost to Redeem\"\n        And it contains the source reward pretty value in bolded text\n        Examples:\n            | type                        | maySee | mayContain      | amountTitle                  |\n            | FIXED_GLOBAL_REWARD         | don't  | doesn't contain | N/A                          |\n            | VARIABLE_GLOBAL_REWARD      | see    | contains        | the pretty destination value |\n            | STEPPED_FIXED_GLOBAL_REWARD | see    | contains        | the pretty destination value |\n            | VARIABLE_CREDIT_REWARD      | see    | contains        | the pretty destination value |\n\n    @motivating\n    Scenario: An error banner is displayed if an error occurs during redemeption\n        Given a user has selected a reward to exchange\n        And is on the confirmation page\n        When they click \"Redeem\"\n        But an error occurs\n        Then an error banner appears\n        And it contains details about the error\n        And the reward exchange is not completed\n\n    @motivating\n    Scenario: Confetti is displayed when a reward exchange succeeds\n        Given a user has selected a reward to exchange\n        And they are on the confirmation page\n        When they click \"Redeem\"\n        And the exchange is successful\n        Then they see confetti centered on the success page\n        And they see text describing what they exchanged for their new reward\n        And they see a \"Done\" brand colour button\n        When they click \"Done\"\n        Then they see the Rewards page\n\n    @motivating\n    Scenario: Fuel tank codes are shown when a reward exchange succeeds\n        Given a user has selected to exchange for a fuel tank reward\n        When they complete the reward exchange\n        And are on the success page\n        Then they see a textbox with their fuel tank code\n        And a clipboard icon\n        When they click the clipboard icon\n        Then their fuel tank code is copied to their clipboard\n\n    @motivating\n    Scenario Outline: Users can exchange for any type of reward\n        Given a <type> reward exchange rule for a <reward>\n        And a user who has enough source credit to exchange for the reward\n        When they go through the exchange flow\n        And exchange for their reward\n        Then their credit is exchanged for the <reward>\n        Examples:\n            | type                        | reward         |\n            | FIXED_GLOBAL_REWARD         | gift card      |\n            | FIXED_GLOBAL_REWARD         | fuel tank code |\n            | FIXED_GLOBAL_REWARD         | discount       |\n            | FIXED_GLOBAL_REWARD         | credit reward  |\n            | STEPPED_FIXED_GLOBAL_REWARD | gift card      |\n            | STEPPED_FIXED_GLOBAL_REWARD | discount       |\n            | STEPPED_FIXED_GLOBAL_REWARD | credit reward  |\n            | VARIABLE_GLOBAL_REWARD      | gift card      |\n            | VARIABLE_GLOBAL_REWARD      | discount       |\n            | VARIABLE_GLOBAL_REWARD      | credit reward  |\n            | VARIABLE_CREDIT_REWARD      | credit reward  |";
 
 const RewardExchangeList_stories = {
   title: "Components/Reward Exchange List",
   parameters: {
-    scenario: scenario$l,
+    scenario: scenario$m,
   },
 };
 const StoryBase = (props) => () => {
@@ -11148,12 +11287,12 @@ const RewardExchangeList = /*#__PURE__*/Object.freeze({
   Empty: Empty$2
 });
 
-const scenario$m = "@author:derek\n@owner:derek\nFeature: Program Explainer\n\n    @motivating\n    @ui\n    Scenario Outline: The program explainer wraps program explainer steps and aligns them\n        Given a program explainer component\n        And it has <number> program explainer steps as components\n        When a user views the program explainer\n        Then they see <number> steps aligned horizontally\n        And they have equal height/width\n        And equal padding in between\n        When they are viewed on a screen smaller than 500px\n        Then the steps stack vertically with equal padding in between\n        And they have equal width\n        But height may vary\n        Examples:\n            | number |\n            | 2      |\n            | 3      |\n            | 4      |\n\n    @motivating\n    @ui\n    Scenario: The program explainer displays a section header\n        Given a program explainer step with props\n            | prop   | value     |\n            | header | My Header |\n        And it has program explainer steps as children\n        When a user views the program explainer\n        Then they see \"My Header\" centered above the explainer steps\n\n    @motivating\n    @ui\n    Scenario: Colours are customizable\n        Given a program explainer with props\n            | prop             | value  |\n            | text-color       | purple |\n            | background-color | grey   |\n        When a user views the program explainer\n        Then the header is purple\n        And the background between steos is grey\n";
+const scenario$n = "@author:derek\n@owner:derek\nFeature: Program Explainer\n\n    @motivating\n    @ui\n    Scenario Outline: The program explainer wraps program explainer steps and aligns them\n        Given a program explainer component\n        And it has <number> program explainer steps as components\n        When a user views the program explainer\n        Then they see <number> steps aligned horizontally\n        And they have equal height/width\n        And equal padding in between\n        When they are viewed on a screen smaller than 500px\n        Then the steps stack vertically with equal padding in between\n        And they have equal width\n        But height may vary\n        Examples:\n            | number |\n            | 2      |\n            | 3      |\n            | 4      |\n\n    @motivating\n    @ui\n    Scenario: The program explainer displays a section header\n        Given a program explainer step with props\n            | prop   | value     |\n            | header | My Header |\n        And it has program explainer steps as children\n        When a user views the program explainer\n        Then they see \"My Header\" centered above the explainer steps\n\n    @motivating\n    @ui\n    Scenario: Colours are customizable\n        Given a program explainer with props\n            | prop             | value  |\n            | text-color       | purple |\n            | background-color | grey   |\n        When a user views the program explainer\n        Then the header is purple\n        And the background between steos is grey\n";
 
 const ProgramExplainer_stories = {
   title: "Components/Program Explainer",
   parameters: {
-    scenario: scenario$m,
+    scenario: scenario$n,
   },
 };
 const OneStep = () => {
@@ -11209,12 +11348,12 @@ const ProgramExplainer = /*#__PURE__*/Object.freeze({
   ProgramExplainerGeneric: ProgramExplainerGeneric
 });
 
-const scenario$n = "@author:derek\n@owner:derek\nFeature: Program Explainer Step\n\n    @motivating\n    @ui\n    Scenario: The program explainer step displays a icon, header and description\n        Given a program explainer step with props\n            | prop        | value                            |\n            | header      | My Header                        |\n            | description | My program explainer description |\n            | icon        | person-plus-fill                 |\n        When a user views the explainer step\n        Then they see an person icon with a + in the top left hand corner\n        And the icon is weight 300 brand colour\n        And below they see \"My Header\" in large bold font\n        And below they see \"My program explainer description\" in medium font\n        And the step background colour is weight 50 brand colour\n\n    @motivating\n    @ui\n    Scenario: The program explainer can display an image in place of an icon\n        Given a program explainer\n        And it has an \"image-url\" prop with a value of a valid url to an image\n        When a user views the explainer step\n        Then the image is displayed in place of an incon in the top left hand corner\n\n    @motivating\n    @ui\n    Scenario: Colours are customizable\n        Given a program explainer step with props\n            | prop             | value            |\n            | text-color       | purple           |\n            | background-color | grey             |\n        When a user views the explainer step\n        Then they see the step background is grey\n        And the header text is purple\n        And the description text is purple\n";
+const scenario$o = "@author:derek\n@owner:derek\nFeature: Program Explainer Step\n\n    @motivating\n    @ui\n    Scenario: The program explainer step displays a icon, header and description\n        Given a program explainer step with props\n            | prop        | value                            |\n            | header      | My Header                        |\n            | description | My program explainer description |\n            | icon        | person-plus-fill                 |\n        When a user views the explainer step\n        Then they see an person icon with a + in the top left hand corner\n        And the icon is weight 300 brand colour\n        And below they see \"My Header\" in large bold font\n        And below they see \"My program explainer description\" in medium font\n        And the step background colour is weight 50 brand colour\n\n    @motivating\n    @ui\n    Scenario: The program explainer can display an image in place of an icon\n        Given a program explainer\n        And it has an \"image-url\" prop with a value of a valid url to an image\n        When a user views the explainer step\n        Then the image is displayed in place of an incon in the top left hand corner\n\n    @motivating\n    @ui\n    Scenario: Colours are customizable\n        Given a program explainer step with props\n            | prop             | value            |\n            | text-color       | purple           |\n            | background-color | grey             |\n        When a user views the explainer step\n        Then they see the step background is grey\n        And the header text is purple\n        And the description text is purple\n";
 
 const ProgramExplainerStep_stories = {
   title: "Components/Program Explainer Step",
   parameters: {
-    scenario: scenario$n,
+    scenario: scenario$o,
   },
 };
 const ProgramExplainerStep = () => {
@@ -11231,12 +11370,12 @@ const ProgramExplainerStep$1 = /*#__PURE__*/Object.freeze({
   ProgramExplainerStepCustom: ProgramExplainerStepCustom
 });
 
-const scenario$o = "@author:derek\n@owner:logan\nFeature: Brand Configuration\n\n\t@motivating\n\tScenario: The brand components creates a colour pallet from a brand colour and applies it to children\n\t\tGiven a brand component with \"brand-color\" \"#4225c4\"\n\t\tAnd it is wrapping several mint components\n\t\tWhen a user views the children components\n\t\tThen the following css variables are set\n\t\t\t| variable                      | value                       |\n\t\t\t| --sl-color-primary-50         | hsla(251, 68%, 95%, 1)      |\n\t\t\t| --sl-color-primary-100        | hsla(251, 68%, 86%, 1)      |\n\t\t\t| --sl-color-primary-200        | hsla(251, 68%, 76%, 1)      |\n\t\t\t| --sl-color-primary-300        | hsla(251, 68%, 66%, 1)      |\n\t\t\t| --sl-color-primary-400        | hsla(251, 68%, 56%, 1)      |\n\t\t\t| --sl-color-primary-500        | hsla(251, 68%, 46%, 1)      |\n\t\t\t| --sl-color-primary-600        | hsla(251, 68%, 39%, 1)      |\n\t\t\t| --sl-color-primary-700        | hsla(251, 68%, 32%, 1)      |\n\t\t\t| --sl-color-primary-800        | hsla(251, 68%, 25%, 1)      |\n\t\t\t| --sl-color-primary-900        | hsla(251, 68%, 18%, 1)      |\n\t\t\t| --sl-color-primary-950        | hsla(251, 68%, 15%, 1)      |\n\t\t\t| --sl-focus-ring-color-primary | var(--sl-color-primary-100) |\n\t\t\t| --sl-input-border-color-focus | var(--sl-color-primary-500) |\n\t\t\t| --sl-color-primary-hue        | var(--sl-color-primary-500) |\n\t\tAnd they are applied to the children components\n\t\tBut they are not applied to any components outside of the brand component\n\t\tAnd they are not applied to any vanilla components\n\n\t@minutia\n\tScenario Outline: The brand colour can be hex, HSL or rgb\n\t\tGiven a brand component with \"brand-color\" <colour>\n\t\tAnd it is wrapping several mint components\n\t\tWhen a user views the children components\n\t\tThen the colour is used to create a brand palete\n\t\tAnd it is applied to the children components\n\t\tExamples:\n\t\t\t| colour                 |\n\t\t\t| #4225c4                |\n\t\t\t| rgb(66, 37, 196)       |\n\t\t\t| hsl(251, 68%, 46%)     |\n\t\t\t| hsla(251, 68%, 46%, 1) |\n\n\t@motivating\n\tScenario: The brand component can apply a brand font to children components\n\t\tGiven a brand component with \"brand-font\" \"Nunito Sans\"\n\t\tAnd it is wrapping several mint components\n\t\tWhen a user views the children components\n\t\tThen the following css variables are set\n\t\t\t| variable                 | value                |\n\t\t\t| --sl-font-sans           | \"Nunito Sans\", arial |\n\t\t\t| --sl-input-font-family   | \"Nunito Sans\", arial |\n\t\t\t| --sl-tooltip-font-family | \"Nunito Sans\", arial |\n\t\t\t| font-family              | \"Nunito Sans\", arial |\n\t\tAnd they are applied to the children components\n\t\tAnd the children component's text is \"Nunito Sans\"";
+const scenario$p = "@author:derek\n@owner:logan\nFeature: Brand Configuration\n\n\t@motivating\n\tScenario: The brand components creates a colour pallet from a brand colour and applies it to children\n\t\tGiven a brand component with \"brand-color\" \"#4225c4\"\n\t\tAnd it is wrapping several mint components\n\t\tWhen a user views the children components\n\t\tThen the following css variables are set\n\t\t\t| variable                      | value                       |\n\t\t\t| --sl-color-primary-50         | hsla(251, 68%, 95%, 1)      |\n\t\t\t| --sl-color-primary-100        | hsla(251, 68%, 86%, 1)      |\n\t\t\t| --sl-color-primary-200        | hsla(251, 68%, 76%, 1)      |\n\t\t\t| --sl-color-primary-300        | hsla(251, 68%, 66%, 1)      |\n\t\t\t| --sl-color-primary-400        | hsla(251, 68%, 56%, 1)      |\n\t\t\t| --sl-color-primary-500        | hsla(251, 68%, 46%, 1)      |\n\t\t\t| --sl-color-primary-600        | hsla(251, 68%, 39%, 1)      |\n\t\t\t| --sl-color-primary-700        | hsla(251, 68%, 32%, 1)      |\n\t\t\t| --sl-color-primary-800        | hsla(251, 68%, 25%, 1)      |\n\t\t\t| --sl-color-primary-900        | hsla(251, 68%, 18%, 1)      |\n\t\t\t| --sl-color-primary-950        | hsla(251, 68%, 15%, 1)      |\n\t\t\t| --sl-focus-ring-color-primary | var(--sl-color-primary-100) |\n\t\t\t| --sl-input-border-color-focus | var(--sl-color-primary-500) |\n\t\t\t| --sl-color-primary-hue        | var(--sl-color-primary-500) |\n\t\tAnd they are applied to the children components\n\t\tBut they are not applied to any components outside of the brand component\n\t\tAnd they are not applied to any vanilla components\n\n\t@minutia\n\tScenario Outline: The brand colour can be hex, HSL or rgb\n\t\tGiven a brand component with \"brand-color\" <colour>\n\t\tAnd it is wrapping several mint components\n\t\tWhen a user views the children components\n\t\tThen the colour is used to create a brand palete\n\t\tAnd it is applied to the children components\n\t\tExamples:\n\t\t\t| colour                 |\n\t\t\t| #4225c4                |\n\t\t\t| rgb(66, 37, 196)       |\n\t\t\t| hsl(251, 68%, 46%)     |\n\t\t\t| hsla(251, 68%, 46%, 1) |\n\n\t@motivating\n\tScenario: The brand component can apply a brand font to children components\n\t\tGiven a brand component with \"brand-font\" \"Nunito Sans\"\n\t\tAnd it is wrapping several mint components\n\t\tWhen a user views the children components\n\t\tThen the following css variables are set\n\t\t\t| variable                 | value                |\n\t\t\t| --sl-font-sans           | \"Nunito Sans\", arial |\n\t\t\t| --sl-input-font-family   | \"Nunito Sans\", arial |\n\t\t\t| --sl-tooltip-font-family | \"Nunito Sans\", arial |\n\t\t\t| font-family              | \"Nunito Sans\", arial |\n\t\tAnd they are applied to the children components\n\t\tAnd the children component's text is \"Nunito Sans\"";
 
 const SqmBrand_stories = {
   title: "Components/Brand",
   parameters: {
-    scenario: scenario$o,
+    scenario: scenario$p,
   },
 };
 const SampleComponents = () => (h("div", { style: { padding: "10px", border: "5px solid #EEE" } },
@@ -11337,12 +11476,12 @@ const BrandStories = /*#__PURE__*/Object.freeze({
   Fonts: Fonts
 });
 
-const scenario$p = "@author:kutay\n@owner:kutay\nFeature: Card Feed\n\n\tThe Card Feed component displays Task Card components in a grid layout.\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the Card Feed component\n\n\t@motivating\n\tScenario: The Card Feed component displays Task Cards given as children slots\n\t\tGiven a Card Feed component\n\t\tAnd it is wrapping a number of task cards as children\n\t\tWhen the user views the Card Feed\n\t\tThen the task cards are displayed in a masonry layout\n\t\tWhen the card feed with grows or shrinks in width\n\t\tThen the number of columns adjust to the given width\n\n\t@motivating\n\t@ui\n\tScenario Outline: The Card Feed component can have a maximum width\n\t\tGiven a Card Feed component\n\t\tAnd it is wrapping a number of task cards as children\n\t\tAnd has prop \"width\" has a provided <value>\n\t\tThen the task cards are displayed in a masonry layout\n\t\tWhen the card feed with grows or shrinks in width\n\t\tThen the number of columns adjust to the given width\n\t\tAnd the task cards do not exceed <width>\n\t\tExamples:\n\t\t\t| value | width |\n\t\t\t|       | 347px |\n\t\t\t| 200   | 200px |\n\t\t\t| 400   | 400px |\n\n\t@motivating\n\t@ui\n\tScenario Outline: The Card Feed component gap between task cards can be customized\n\t\tGiven a Card Feed component\n\t\tAnd it is wrapping a number of task cards as children\n\t\tAnd has prop \"gap\" has a provided <value>\n\t\tThen the task cards are displayed in a masonry layout\n\t\tAnd the gap between the columns is the <gap>\n\t\tExamples:\n\t\t\t| value | gap  |\n\t\t\t|       | 24px |\n\t\t\t| 20    | 20px |\n\t\t\t| 50    | 50px |";
+const scenario$q = "@author:kutay\n@owner:kutay\nFeature: Card Feed\n\n\tThe Card Feed component displays Task Card components in a grid layout.\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the Card Feed component\n\n\t@motivating\n\tScenario: The Card Feed component displays Task Cards given as children slots\n\t\tGiven a Card Feed component\n\t\tAnd it is wrapping a number of task cards as children\n\t\tWhen the user views the Card Feed\n\t\tThen the task cards are displayed in a masonry layout\n\t\tWhen the card feed with grows or shrinks in width\n\t\tThen the number of columns adjust to the given width\n\n\t@motivating\n\t@ui\n\tScenario Outline: The Card Feed component can have a maximum width\n\t\tGiven a Card Feed component\n\t\tAnd it is wrapping a number of task cards as children\n\t\tAnd has prop \"width\" has a provided <value>\n\t\tThen the task cards are displayed in a masonry layout\n\t\tWhen the card feed with grows or shrinks in width\n\t\tThen the number of columns adjust to the given width\n\t\tAnd the task cards do not exceed <width>\n\t\tExamples:\n\t\t\t| value | width |\n\t\t\t|       | 347px |\n\t\t\t| 200   | 200px |\n\t\t\t| 400   | 400px |\n\n\t@motivating\n\t@ui\n\tScenario Outline: The Card Feed component gap between task cards can be customized\n\t\tGiven a Card Feed component\n\t\tAnd it is wrapping a number of task cards as children\n\t\tAnd has prop \"gap\" has a provided <value>\n\t\tThen the task cards are displayed in a masonry layout\n\t\tAnd the gap between the columns is the <gap>\n\t\tExamples:\n\t\t\t| value | gap  |\n\t\t\t|       | 24px |\n\t\t\t| 20    | 20px |\n\t\t\t| 50    | 50px |";
 
 const CardFeed_stories = {
   title: "Components/Card Feed",
   parameters: {
-    scenario: scenario$p,
+    scenario: scenario$q,
   },
 };
 const oneAction$1 = {
@@ -11579,12 +11718,12 @@ const CardFeed = /*#__PURE__*/Object.freeze({
   CardFeedGeneric: CardFeedGeneric
 });
 
-const scenario$q = "@author:kutay\n@owner:noah\nFeature: Portal Container\n\n\t@motivating\n\t@ui\n\tScenario: Horizontal content overflows, but does not stretch\n\t\tGiven there are two element in the container\n\t\tAnd the first is small\n\t\tAnd the second would stretch the container wider than it's parent\n\t\tThen the second one is clipped\n\t\tAnd the first one doesn't stretch\n\n\t@landmine\n\t@ui\n\tScenario: `max-width` is required for displaying as a row\n\t\tGiven I have `direction` to \"row\"\n\t\tAnd I have not set a `max-width`\n\t\tThen it displays as a column\n\n\t@motivating\n\t@ui\n\tScenario Outline: Content padding can be customized\n\t\tGiven prop \"padding\" has <value>\n\t\tThen <padding> is applied to content\n\n\t\tExamples:\n\t\t\t| value      | padding    |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |\n\n\n\t@motivating\n\t@ui\n\tScenario Outline: Gap between content elements can be customized\n\t\tGiven prop \"gap\" has <value>\n\t\tThen <gap> is applied to elements between content\n\n\t\tExamples:\n\t\t\t| value      | gap        |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |\n\n\t@minutia\n\t@ui\n\tScenario: Content can be center aligned in horizontal view\n\t\tGiven I have supplied the prop \"center\"\n\t\tThen the content is center aligned\n\n\t@minutia\n\t@ui\n\tScenario: Content in the last row can span full width with display in horizontal view\n\t\tGiven I have `display` to \"flex\"\n\t\tThen the content is full width on the last row\n\n\t@motivating\n\t@ui\n\tScenario Outline: Content can be aligned along the x-axis\n\t\tGiven prop \"justify-content\" has <value>\n\t\tThen content within the container is aligned <alignment>\n\n\t\tExamples:\n\t\t\t| value         | alignment          |\n\t\t\t| none          | no alignment       |\n\t\t\t| start         | to the start       |\n\t\t\t| center        | to the center      |\n\t\t\t| end           | to the end         |\n\t\t\t| space-between | with space between |\n\t\t\t| space-around  | with space around  |\n\t\t\t| space-evenly  | with space evenly  |\n\n\n\t@motivating\n\t@ui\n\tScenario Outline: Component background color can be customized\n\t\tGiven a user is viewing the Portal Container component\n\t\tThen the default value is \"#ffffff00\"\n\t\tWhen the prop \"background-color\" has <value>\n\t\tThen the background has color <backgroundColor>\n\t\tExamples:\n\t\t\t| value                 | backgroundColor                     |\n\t\t\t| empty (default value) | var(--sl-color-neutral-0) (#ffffff) |\n\t\t\t| aquamarine            | #7fffd4                             |\n";
+const scenario$r = "@author:kutay\n@owner:noah\nFeature: Portal Container\n\n\t@motivating\n\t@ui\n\tScenario: Horizontal content overflows, but does not stretch\n\t\tGiven there are two element in the container\n\t\tAnd the first is small\n\t\tAnd the second would stretch the container wider than it's parent\n\t\tThen the second one is clipped\n\t\tAnd the first one doesn't stretch\n\n\t@landmine\n\t@ui\n\tScenario: `max-width` is required for displaying as a row\n\t\tGiven I have `direction` to \"row\"\n\t\tAnd I have not set a `max-width`\n\t\tThen it displays as a column\n\n\t@motivating\n\t@ui\n\tScenario Outline: Content padding can be customized\n\t\tGiven prop \"padding\" has <value>\n\t\tThen <padding> is applied to content\n\n\t\tExamples:\n\t\t\t| value      | padding    |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |\n\n\n\t@motivating\n\t@ui\n\tScenario Outline: Gap between content elements can be customized\n\t\tGiven prop \"gap\" has <value>\n\t\tThen <gap> is applied to elements between content\n\n\t\tExamples:\n\t\t\t| value      | gap        |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |\n\n\t@minutia\n\t@ui\n\tScenario: Content can be center aligned in horizontal view\n\t\tGiven I have supplied the prop \"center\"\n\t\tThen the content is center aligned\n\n\t@minutia\n\t@ui\n\tScenario: Content in the last row can span full width with display in horizontal view\n\t\tGiven I have `display` to \"flex\"\n\t\tThen the content is full width on the last row\n\n\t@motivating\n\t@ui\n\tScenario Outline: Content can be aligned along the x-axis\n\t\tGiven prop \"justify-content\" has <value>\n\t\tThen content within the container is aligned <alignment>\n\n\t\tExamples:\n\t\t\t| value         | alignment          |\n\t\t\t| none          | no alignment       |\n\t\t\t| start         | to the start       |\n\t\t\t| center        | to the center      |\n\t\t\t| end           | to the end         |\n\t\t\t| space-between | with space between |\n\t\t\t| space-around  | with space around  |\n\t\t\t| space-evenly  | with space evenly  |\n\n\n\t@motivating\n\t@ui\n\tScenario Outline: Component background color can be customized\n\t\tGiven a user is viewing the Portal Container component\n\t\tThen the default value is \"#ffffff00\"\n\t\tWhen the prop \"background-color\" has <value>\n\t\tThen the background has color <backgroundColor>\n\t\tExamples:\n\t\t\t| value                 | backgroundColor                     |\n\t\t\t| empty (default value) | var(--sl-color-neutral-0) (#ffffff) |\n\t\t\t| aquamarine            | #7fffd4                             |\n";
 
 const PortalContainer_stories = {
   title: "Components/Microsite Container",
   parameters: {
-    scenario: scenario$q,
+    scenario: scenario$r,
   },
 };
 const TooWideColumn = () => (h("div", { style: { width: "200px", border: "1px dashed grey" } },
@@ -11752,11 +11891,11 @@ const scenario3 = "@author:derek @owner:derek\nFeature: Reward Table Status Colu
 
 const scenario4 = "@author:derek @owner:derek\nFeature: Reward Table Source Column\n    Shows the source of each reward\n\n  @motivating @ui\n  Scenario Outline: The title of the source column is configurable\n    Given the \"column-title\" prop is set to <value>\n    Then the source column is shown with <columnTitle>\n\n    Examples:\n      | value           | columnTitle     |\n      | Source          |                 |\n      | My column title | My column title |\n\n  @motivating @ui\n  Scenario: The source column displays manual if the reward is caused by a manual action\n    Given a user with a \"MANUAL\" reward\n    When they view the rewards table\n    Then the source of their reward is displayed as \"Manual\"\n\n  @motivating @ui\n  Scenario: The source column displays the program name if the reward is caused automatically by a program\n    Given a user with a \"AUTOMATED\" program reward\n    And the program has name \"Loyalty Program\"\n    When they view the rewards table\n    Then the source of their reward is displayed as \"Loyalty Program\"\n\n  @motivating @ui\n  Scenario Outline: The source column displays customizable reward exchange text with amount if the reward is caused by reward exchange\n    Given the \"reward-exchange-text\" prop is <propValue>\n    And a user with a \"MANUAL\" reward\n    But it was created by a reward exchange\n    Then they view the rewards table\n    Then the source displays <exchangeText>\n    And under it displays the following\n      | prettyRedeemedCredit → prettyValue |\n\n    Examples:\n      | propValue | exchangeText    |\n      |           | Reward Exchange |\n      | Exchanged | Exchanged       |\n\n  @motivating @ui\n  Scenario Outline: The source column displays customizable referral information if the reward is from a referral\n    Given the \"reward-source-text\" prop is <propValue>\n    And a user with a referral reward\n    And that reward has <rewardSource>\n    When they view the rewards table\n    Then then source displays <referralText>\n    And under it displays the full name of the <referralUser>\n\n    Examples:\n      | propValue                                                                             | rewardSource  | referralText | referralUser  |\n      |                                                                                       | REFERRED      | Referred by  | referrer user |\n      |                                                                                       | FRIEND_SIGNUP | Referral to  | referred user |\n      | {rewardSource, select, FRIEND_SIGNUP {You Referred} REFERRED {Referred you} other {}} | REFERRED      | Referred you | referrer user |\n      | {rewardSource, select, FRIEND_SIGNUP {You Referred} REFERRED {Referred you} other {}} | FRIEND_SIGNUP | You Referred | referred user |\n\n  @motivating @ui\n  Scenario Outline: The source column displays the existing name for a referral if either the first name or last name does not exist\n    Given a user with a referral reward\n    And referral user exists\n    And referral user has <name>\n    But referral user has no <otherName>\n    When they view the rewards table\n    Then referral user's name is displayed as <name>\n\n    Examples:\n      | name       | otherName  |\n      | first.name | last.name  |\n      | last.name  | first.name |\n\n  @motivating @ui\n  Scenario Outline: The source column displays referral as \"Anonymous User\" if the referral user has no names\n    Given a user with a referral reward\n    And that reward has <rewardSource>\n    And the <referralUser> has no first name\n    And the <referralUser> has no last name\n    When they view the rewards table\n    Then then source displays <sourceText>\n    And under it displays \"Anonymous User\"\n\n    Examples:\n      | rewardSource  | referralUser  | sourceText  |\n      | FRIEND_SIGNUP | referrer      | Referral to |\n      | REFERRED      | referred user | Referred by |\n\n  @motivating @ui\n  Scenario Outline: The source column displays referral as \"Deleted User\" if the referral user is deleted in the system\n    Given a user with a referral reward\n    And that reward has <rewardSource>\n    But <referral> user was deleted\n    When they view the rewards table\n    Then the source displays <sourceText>\n    And under it displays \"Deleted User\"\n\n    Examples:\n      | rewardSource    | referral | sourceText  |\n      | \"FRIEND_SIGNUP\" | referrer | Referral to |\n      | \"REFERRED\"      | referred | Referred by |\n#  AL: TODO DELETED REFERRAL SPEC\n\n  @motivating @ui\n  Scenario Outline: The source column displays referral as \"Deleted referral\" if the referral user is deleted in the system\n    Given a user with a referral reward\n    And that reward has <rewardSource>\n    But <referral> user was deleted\n    When they view the rewards table\n    Then the source displays <sourceText>\n    And under it displays \"Deleted referral\"\n\n    Examples:\n      | rewardSource    | referral | sourceText  |\n      | \"FRIEND_SIGNUP\" | referrer | Referral to |\n      | \"REFERRED\"      | referred | Referred by |\n\n  @minutia @ui\n  Scenario Outline: Name fallbacks for referral users without names are customizable\n    Given <prop> with <value>\n    And a user with a referral reward\n    But the referral user <hadAction>\n    When they view the rewards table\n    Then the source displays <value> as the referral user\n\n    Examples:\n      | prop           | value           | hadAction                       |\n      | deleted-user   | Former Customer | was deleted                     |\n      | anonymous-user | Nameless User   | had first and last name deleted |\n\n  @motivating\n  Scenario Outline: Source text can be customized\n    Given the \"reward-source-text\" prop is \"{rewardSource, select, MANUAL {Support} AUTOMATED {Loyalty Program} other {}}\"\n    And a user with a <rewardSource> reward\n    When they view the rewards table\n    Then the source is <sourceText>\n\n    Examples:\n      | rewardSource | sourceText      |\n      | MANUAL       | Support         |\n      | AUTOMATED    | Loyalty Program |\n";
 
-const scenario$r = scenario1 + scenario2 + scenario3 + scenario4;
+const scenario$s = scenario1 + scenario2 + scenario3 + scenario4;
 const RewardsTableCell_stories = {
   title: "Components/Rewards Table Cell",
   parameters: {
-    scenario: scenario$r,
+    scenario: scenario$s,
   },
 };
 const rewardsData$1 = {
@@ -12205,12 +12344,12 @@ const RewardsTableCell = /*#__PURE__*/Object.freeze({
   EmptyCell: EmptyCell$2
 });
 
-const scenario$s = "@owner:sam\n@author:sam\nFeature: Rewards Table\n\n    Shows a list of rewards as a table\n\n    @motivating\n    @ui\n    Scenario: The empty state is shown if there are no rewards\n        Given a user with rewards\n        When they view the reward table\n        Then no rewards are displayed\n        And they see an image with a user icon\n        And \"View your rewards\" in bold\n        And \"See all the rewards you have earned from referring friends and completing tasks\" below the bolded text\n        And the pagination buttons are disabled\n\n    @minutia\n    @ui\n    Scenario: A custom empty state can be provided\n        Given a user with no rewards\n        And a custom empty state has been supplied in the \"empty\" slot\n        When they view the reward table\n        Then they see the custom empty state\n\n    @minutia\n    @ui\n    Scenario: The loading state is shown while rewards are loading\n        Given the table is loading\n        Then the loading state is shown in the table\n        And a custom loading state can be supplied in the \"loading\" slot\n        And the pagination buttons are disabled\n\n    @motivating\n    @ui\n    Scenario Outline: The table becomes paginated when the number of rewards exceeds the per page limit\n        Given the user has <number of rewards>\n        And the table is configured to show <page limit> rewards per page\n        Then the table will have <number of pages> page(s)\n        And pagination buttons will allow users to navigate between pages\n        And the pagination button to go to the next page is disabled on the last page of rewards\n        And the pagination button to go to the previous page is disabled on the first page of rewards\n        Examples:\n            | number of rewards | page limit | number of pages |\n            | 0                 | 4          | 1               |\n            | 1                 | 4          | 1               |\n            | 3                 | 4          | 1               |\n            | 5                 | 4          | 2               |\n            | 42                | 4          | 11              |\n\n    @motivating\n    @ui\n    Scenario: The table converts to a card view on tablet and mobile window sizes\n        Given a user with rewards\n        When they view the table\n        And their window size is smaller than \"799px\"\n        Then rewards are displayed as cards\n        And they are in two columns\n        When their window size is smaller than \"599px\"\n        Then the rewards are displayed as cards in a singular column\n\n    @motivating\n    @ui\n    Scenario: Table and Mobile beakpoints can be configured\n        Given the reward table has been configured with the following props\n            | prop         | value |\n            | smBreakpoint | 599   |\n            | mdBreakpoint | 799   |\n        And a user with rewards\n        When they view the table\n        And their window size is smaller than \"799px\"\n        Then rewards are displayed as cards\n        And they are in two columns\n        When their window size is smaller than \"599px\"\n        Then the rewards are displayed as cards in a singular column\n\n    @motivating\n    @ui\n    Scenario Outline: By default the first column heading is hidden in mobile\n        Given a reward table with 4 columns\n        And prop \"hidden-columns\" with <hideColumnValue>\n        And a user with rewards\n        When they view the reward table\n        And their window size is below the tablet breakpoint\n        Then reward cards are displayed\n        And the titles of <columnsArehidden> within the card\n        Examples:\n            | hideColumnValue | columnsArehidden                    |\n            |                 | the first column                    |\n            | 0,1,2           | the first, second and third columns |\n            | 3               | the fourth column                   |\n\n    @motivating\n    Scenario: Only rewards which occured in the program specific by \"program-id\" are shown\n        Given the table is configured with \"program-id\"\n        Then only rewards from the program with \"program-id\" are shown\n\n    @landmine\n    Scenario: When a `classic` program Id is set then any reward without a programId is shown\n        There is no easy way for the backend to filter for \"classic\" programs,\n        thus we are filtering for rewards without programId's.\n\n        Given the \"program-id\" of the table is set to \"classic\"\n        Then rewards from classic programs are shown\n        And manual rewards are shown\n\n    @minutia\n    @ui\n    Scenario: Column heading can be hidden\n        Given the table is configured with \"hide-labels\" set to \"true\"\n        Then the table is displayed without column headings";
+const scenario$t = "@owner:sam\n@author:sam\nFeature: Rewards Table\n\n    Shows a list of rewards as a table\n\n    @motivating\n    @ui\n    Scenario: The empty state is shown if there are no rewards\n        Given a user with rewards\n        When they view the reward table\n        Then no rewards are displayed\n        And they see an image with a user icon\n        And \"View your rewards\" in bold\n        And \"See all the rewards you have earned from referring friends and completing tasks\" below the bolded text\n        And the pagination buttons are disabled\n\n    @minutia\n    @ui\n    Scenario: A custom empty state can be provided\n        Given a user with no rewards\n        And a custom empty state has been supplied in the \"empty\" slot\n        When they view the reward table\n        Then they see the custom empty state\n\n    @minutia\n    @ui\n    Scenario: The loading state is shown while rewards are loading\n        Given the table is loading\n        Then the loading state is shown in the table\n        And a custom loading state can be supplied in the \"loading\" slot\n        And the pagination buttons are disabled\n\n    @motivating\n    @ui\n    Scenario Outline: The table becomes paginated when the number of rewards exceeds the per page limit\n        Given the user has <number of rewards>\n        And the table is configured to show <page limit> rewards per page\n        Then the table will have <number of pages> page(s)\n        And pagination buttons will allow users to navigate between pages\n        And the pagination button to go to the next page is disabled on the last page of rewards\n        And the pagination button to go to the previous page is disabled on the first page of rewards\n        Examples:\n            | number of rewards | page limit | number of pages |\n            | 0                 | 4          | 1               |\n            | 1                 | 4          | 1               |\n            | 3                 | 4          | 1               |\n            | 5                 | 4          | 2               |\n            | 42                | 4          | 11              |\n\n    @motivating\n    @ui\n    Scenario: The table converts to a card view on tablet and mobile window sizes\n        Given a user with rewards\n        When they view the table\n        And their window size is smaller than \"799px\"\n        Then rewards are displayed as cards\n        And they are in two columns\n        When their window size is smaller than \"599px\"\n        Then the rewards are displayed as cards in a singular column\n\n    @motivating\n    @ui\n    Scenario: Table and Mobile beakpoints can be configured\n        Given the reward table has been configured with the following props\n            | prop         | value |\n            | smBreakpoint | 599   |\n            | mdBreakpoint | 799   |\n        And a user with rewards\n        When they view the table\n        And their window size is smaller than \"799px\"\n        Then rewards are displayed as cards\n        And they are in two columns\n        When their window size is smaller than \"599px\"\n        Then the rewards are displayed as cards in a singular column\n\n    @motivating\n    @ui\n    Scenario Outline: By default the first column heading is hidden in mobile\n        Given a reward table with 4 columns\n        And prop \"hidden-columns\" with <hideColumnValue>\n        And a user with rewards\n        When they view the reward table\n        And their window size is below the tablet breakpoint\n        Then reward cards are displayed\n        And the titles of <columnsArehidden> within the card\n        Examples:\n            | hideColumnValue | columnsArehidden                    |\n            |                 | the first column                    |\n            | 0,1,2           | the first, second and third columns |\n            | 3               | the fourth column                   |\n\n    @motivating\n    Scenario: Only rewards which occured in the program specific by \"program-id\" are shown\n        Given the table is configured with \"program-id\"\n        Then only rewards from the program with \"program-id\" are shown\n\n    @landmine\n    Scenario: When a `classic` program Id is set then any reward without a programId is shown\n        There is no easy way for the backend to filter for \"classic\" programs,\n        thus we are filtering for rewards without programId's.\n\n        Given the \"program-id\" of the table is set to \"classic\"\n        Then rewards from classic programs are shown\n        And manual rewards are shown\n\n    @minutia\n    @ui\n    Scenario: Column heading can be hidden\n        Given the table is configured with \"hide-labels\" set to \"true\"\n        Then the table is displayed without column headings";
 
 const RewardsTable_stories = {
   title: "Components/Rewards Table",
   parameters: {
-    scenario: scenario$s,
+    scenario: scenario$t,
   },
 };
 const loadingElement$1 = (h("div", { slot: "loading", style: { display: "contents" } },
@@ -12522,12 +12661,12 @@ const UseReferralTable = /*#__PURE__*/Object.freeze({
   ReferralTableFr: ReferralTableFr
 });
 
-const scenario$t = "@author:kutay\n@owner:kutay\nFeature: Hero Image\n\n\tThe Hero Image component displays media images with a header, description and button using an overlay or a double column layout to offer an attrative widget page.\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the Hero Image component\n\n\t@motivating\n\t@ui\n\tScenario: Overlay image displays header, description, and button with brand color\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop        | value                                                              |\n\t\t\t| image-url   | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header      | \"Klip Rewards\"                                                     |\n\t\t\t| description | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text | \"Start earning\"                                                    |\n\t\t\t| layout      | \"overlay\"                                                          |\n\t\tThen they see their image\n\t\tAnd the image has no padding\n\t\tAnd it has a brand colour overlay\n\t\tAnd \"Klip Rewards\" is displayed over top of the image in xxx-large font\n\t\tAnd below \"Refer friends or complete tasks while using Klip to earn rewards\" is displayed over top of the image in x-large font\n\t\tAnd below they see a brand coloured button with text \"Start earning\"\n\t\tAnd the text section has xxx-large padding\n\t\tWhen the component is scaled down to 599px\n\t\tThen the image is scaled to fit content\n\n\t@motivating\n\t@ui\n\tScenario Outline: Overlay image crop can be aligned left, center or right\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop        | value                                                              |\n\t\t\t| image-url   | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header      | \"Klip Rewards\"                                                     |\n\t\t\t| description | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text | \"Start earning\"                                                    |\n\t\t\t| layout      | \"overlay\"                                                          |\n\t\t\t| image-pos   | <value>                                                            |\n\t\tThen the image with overlay is displayed\n\t\tWhen the component is scaled down to 599px\n\t\tThen the image is <alignment> to fit content\n\t\tExamples:\n\t\t\t| value  | alignment     |\n\t\t\t| left   | left aligned  |\n\t\t\t| center | centered      |\n\t\t\t| right  | right aligned |\n\t\t\t| N/A    | centered      |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Overlay padding is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop         | value                                                              |\n\t\t\t| image-url    | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header       | \"Klip Rewards\"                                                     |\n\t\t\t| description  | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text  | \"Start earning\"                                                    |\n\t\t\t| layout       | \"overlay\"                                                          |\n\t\t\t| padding-text | <value>                                                            |\n\t\tThen the image with overlay is displayed\n\t\tAnd <padding> is applied around header, description and button\n\t\tExamples:\n\t\t\t| value      | padding    |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Overlay color and background is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop            | value                                                              |\n\t\t\t| image-url       | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header          | \"Klip Rewards\"                                                     |\n\t\t\t| description     | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text     | \"Start earning\"                                                    |\n\t\t\t| layout          | \"overlay\"                                                          |\n\t\t\t| text-color      | <textColor>                                                        |\n\t\t\t| overlay-color   | <overlayColor>                                                     |\n\t\t\t| overlay-opacity | <overlayOpacity>                                                   |\n\t\tThen the image with overlay is displayed\n\t\tAnd the overlay is <overlayColor>\n\t\tAnd the overlay has <overlayOpacity>\n\t\tAnd the text is <textColor>\n\t\tExamples:\n\t\t\t| textColor | overlayColor | overlayOpacity |\n\t\t\t| #fffc4b   | #ff7f7f      | 0.9            |\n\t\t\t| #1d0314   | #4baa1a      | 0              |\n\t\t\t| #211a27   | #aa481a      | 1              |\n\n\t@motivating\n\t@ui\n\tScenario: Two-column layout displays an image on one side and on the other side a header, description, and button\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop        | value                                                              |\n\t\t\t| image-url   | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header      | \"Klip Rewards\"                                                     |\n\t\t\t| description | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text | \"Start earning\"                                                    |\n\t\t\t| layout      | \"columns\"                                                          |\n\t\tThen the image is displayed on the left\n\t\tAnd the following elements are displayed on the right\n\t\t\t| elements    |\n\t\t\t| header      |\n\t\t\t| description |\n\t\t\t| button      |\n\t\tWhen the component is scaled down to 599px\n\t\tThen the two-column layout switches to a row layout\n\t\tAnd the image is displayed on top\n\t\tAnd the content is displayed below\n\n\t@motivating\n\t@ui\n\tScenario Outline: Image position is configurable for desktop and mobile\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop             | value                                                              |\n\t\t\t| image-url        | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header           | \"Klip Rewards\"                                                     |\n\t\t\t| description      | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text      | \"Start earning\"                                                    |\n\t\t\t| layout           | \"columns\"                                                          |\n\t\t\t| image-pos        | <imagePos>                                                         |\n\t\t\t| image-mobile-pos | <imageMobilePos>                                                   |\n\t\tThen the image is displayed on the <imagePos>\n\t\tWhen the component is scaled down to 599px\n\t\tThen two-column layout switches to a row layout\n\t\tAnd image is displayed on the <imageMobilePos>\n\t\tExamples:\n\t\t\t| imagePos | imageMobilePos |\n\t\t\t| left     | top            |\n\t\t\t| right    | bottom         |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Padding is configurable for the image and text of two column layouts\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop          | value                                                              |\n\t\t\t| image-url     | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header        | \"Klip Rewards\"                                                     |\n\t\t\t| description   | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text   | \"Start earning\"                                                    |\n\t\t\t| layout        | \"columns\"                                                          |\n\t\t\t| padding-text  | <paddingText>                                                      |\n\t\t\t| padding-image | <paddingImage>                                                     |\n\t\tThen the two column layout is displayed\n\t\tAnd the image has padding <paddingImage>\n\t\tAnd the text has padding <paddingText>\n\t\tExamples:\n\t\t\t| paddingText | paddingImage |\n\t\t\t| xxx-small   | xxx-small    |\n\t\t\t| xx-small    | xx-small     |\n\t\t\t| x-small     | x-small      |\n\t\t\t| small       | small        |\n\t\t\t| medium      | medium       |\n\t\t\t| large       | large        |\n\t\t\t| x-large     | x-large      |\n\t\t\t| xx-large    | xx-large     |\n\t\t\t| xxx-large   | xxx-large    |\n\t\t\t| xxxx-large  | xxxx-large   |\n\t\t\t| none        | none         |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Two-column layout image division percentage is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop             | value                                                              |\n\t\t\t| image-url        | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000248/squatch-assets/MVgOJn7.png\"                                 |\n\t\t\t| header           | \"Klip Rewards\"                                                     |\n\t\t\t| description      | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text      | \"Start earning\"                                                    |\n\t\t\t| layout           | \"columns\"                                                          |\n\t\t\t| image-percentage | <percent>                                                          |\n\t\tThen the two column layout is displayed\n\t\tAnd the image takes up <percent> of the two-column layout\n\t\tAnd the text elements take up the remainder of the space\n\t\tExamples:\n\t\t\t| percent |\n\t\t\t| 25%     |\n\t\t\t| 42%     |\n\t\t\t| 66%     |\n\n\t@motivating\n\t@ui\n\tScenario: Two-column layout text and background color is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop             | value                                                              |\n\t\t\t| image-url        | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header           | \"Klip Rewards\"                                                     |\n\t\t\t| description      | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text      | \"Start earning\"                                                    |\n\t\t\t| layout           | \"columns\"                                                          |\n\t\t\t| text-color       | <textColor>                                                        |\n\t\t\t| background-color | <backgroundColor>                                                  |\n\t\tThen the two column layout is displayed\n\t\tAnd the text has color <textColor>\n\t\tAnd the background has color <backgroundColor>\n\t\tExamples:\n\t\t\t| textColor | backgroundColor |\n\t\t\t| #fffc4b   | #ff7f7f         |\n\t\t\t| #1d0314   | #4baa1a         |\n\t\t\t| #211a27   | #aa481a         |";
+const scenario$u = "@author:kutay\n@owner:kutay\nFeature: Hero Image\n\n\tThe Hero Image component displays media images with a header, description and button using an overlay or a double column layout to offer an attrative widget page.\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the Hero Image component\n\n\t@motivating\n\t@ui\n\tScenario: Overlay image displays header, description, and button with brand color\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop        | value                                                              |\n\t\t\t| image-url   | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header      | \"Klip Rewards\"                                                     |\n\t\t\t| description | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text | \"Start earning\"                                                    |\n\t\t\t| layout      | \"overlay\"                                                          |\n\t\tThen they see their image\n\t\tAnd the image has no padding\n\t\tAnd it has a brand colour overlay\n\t\tAnd \"Klip Rewards\" is displayed over top of the image in xxx-large font\n\t\tAnd below \"Refer friends or complete tasks while using Klip to earn rewards\" is displayed over top of the image in x-large font\n\t\tAnd below they see a brand coloured button with text \"Start earning\"\n\t\tAnd the text section has xxx-large padding\n\t\tWhen the component is scaled down to 599px\n\t\tThen the image is scaled to fit content\n\n\t@motivating\n\t@ui\n\tScenario Outline: Overlay image crop can be aligned left, center or right\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop        | value                                                              |\n\t\t\t| image-url   | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header      | \"Klip Rewards\"                                                     |\n\t\t\t| description | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text | \"Start earning\"                                                    |\n\t\t\t| layout      | \"overlay\"                                                          |\n\t\t\t| image-pos   | <value>                                                            |\n\t\tThen the image with overlay is displayed\n\t\tWhen the component is scaled down to 599px\n\t\tThen the image is <alignment> to fit content\n\t\tExamples:\n\t\t\t| value  | alignment     |\n\t\t\t| left   | left aligned  |\n\t\t\t| center | centered      |\n\t\t\t| right  | right aligned |\n\t\t\t| N/A    | centered      |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Overlay padding is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop         | value                                                              |\n\t\t\t| image-url    | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header       | \"Klip Rewards\"                                                     |\n\t\t\t| description  | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text  | \"Start earning\"                                                    |\n\t\t\t| layout       | \"overlay\"                                                          |\n\t\t\t| padding-text | <value>                                                            |\n\t\tThen the image with overlay is displayed\n\t\tAnd <padding> is applied around header, description and button\n\t\tExamples:\n\t\t\t| value      | padding    |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Overlay color and background is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop            | value                                                              |\n\t\t\t| image-url       | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000278/squatch-assets/bTwu1Um.png\"                                 |\n\t\t\t| header          | \"Klip Rewards\"                                                     |\n\t\t\t| description     | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text     | \"Start earning\"                                                    |\n\t\t\t| layout          | \"overlay\"                                                          |\n\t\t\t| text-color      | <textColor>                                                        |\n\t\t\t| overlay-color   | <overlayColor>                                                     |\n\t\t\t| overlay-opacity | <overlayOpacity>                                                   |\n\t\tThen the image with overlay is displayed\n\t\tAnd the overlay is <overlayColor>\n\t\tAnd the overlay has <overlayOpacity>\n\t\tAnd the text is <textColor>\n\t\tExamples:\n\t\t\t| textColor | overlayColor | overlayOpacity |\n\t\t\t| #fffc4b   | #ff7f7f      | 0.9            |\n\t\t\t| #1d0314   | #4baa1a      | 0              |\n\t\t\t| #211a27   | #aa481a      | 1              |\n\n\t@motivating\n\t@ui\n\tScenario: Two-column layout displays an image on one side and on the other side a header, description, and button\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop        | value                                                              |\n\t\t\t| image-url   | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header      | \"Klip Rewards\"                                                     |\n\t\t\t| description | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text | \"Start earning\"                                                    |\n\t\t\t| layout      | \"columns\"                                                          |\n\t\tThen the image is displayed on the left\n\t\tAnd the following elements are displayed on the right\n\t\t\t| elements    |\n\t\t\t| header      |\n\t\t\t| description |\n\t\t\t| button      |\n\t\tWhen the component is scaled down to 599px\n\t\tThen the two-column layout switches to a row layout\n\t\tAnd the image is displayed on top\n\t\tAnd the content is displayed below\n\n\t@motivating\n\t@ui\n\tScenario Outline: Image position is configurable for desktop and mobile\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop             | value                                                              |\n\t\t\t| image-url        | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header           | \"Klip Rewards\"                                                     |\n\t\t\t| description      | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text      | \"Start earning\"                                                    |\n\t\t\t| layout           | \"columns\"                                                          |\n\t\t\t| image-pos        | <imagePos>                                                         |\n\t\t\t| image-mobile-pos | <imageMobilePos>                                                   |\n\t\tThen the image is displayed on the <imagePos>\n\t\tWhen the component is scaled down to 599px\n\t\tThen two-column layout switches to a row layout\n\t\tAnd image is displayed on the <imageMobilePos>\n\t\tExamples:\n\t\t\t| imagePos | imageMobilePos |\n\t\t\t| left     | top            |\n\t\t\t| right    | bottom         |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Padding is configurable for the image and text of two column layouts\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop          | value                                                              |\n\t\t\t| image-url     | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header        | \"Klip Rewards\"                                                     |\n\t\t\t| description   | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text   | \"Start earning\"                                                    |\n\t\t\t| layout        | \"columns\"                                                          |\n\t\t\t| padding-text  | <paddingText>                                                      |\n\t\t\t| padding-image | <paddingImage>                                                     |\n\t\tThen the two column layout is displayed\n\t\tAnd the image has padding <paddingImage>\n\t\tAnd the text has padding <paddingText>\n\t\tExamples:\n\t\t\t| paddingText | paddingImage |\n\t\t\t| xxx-small   | xxx-small    |\n\t\t\t| xx-small    | xx-small     |\n\t\t\t| x-small     | x-small      |\n\t\t\t| small       | small        |\n\t\t\t| medium      | medium       |\n\t\t\t| large       | large        |\n\t\t\t| x-large     | x-large      |\n\t\t\t| xx-large    | xx-large     |\n\t\t\t| xxx-large   | xxx-large    |\n\t\t\t| xxxx-large  | xxxx-large   |\n\t\t\t| none        | none         |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Two-column layout image division percentage is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop             | value                                                              |\n\t\t\t| image-url        | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000248/squatch-assets/MVgOJn7.png\"                                 |\n\t\t\t| header           | \"Klip Rewards\"                                                     |\n\t\t\t| description      | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text      | \"Start earning\"                                                    |\n\t\t\t| layout           | \"columns\"                                                          |\n\t\t\t| image-percentage | <percent>                                                          |\n\t\tThen the two column layout is displayed\n\t\tAnd the image takes up <percent> of the two-column layout\n\t\tAnd the text elements take up the remainder of the space\n\t\tExamples:\n\t\t\t| percent |\n\t\t\t| 25%     |\n\t\t\t| 42%     |\n\t\t\t| 66%     |\n\n\t@motivating\n\t@ui\n\tScenario: Two-column layout text and background color is configurable\n\t\tGiven a Hero Image component configured with the following props\n\t\t\t| prop             | value                                                              |\n\t\t\t| image-url        | \"https://res.cloudinary.com/saasquatch/image/upload/v1644000275/squatch-assets/yr6ER3R.png\"                                 |\n\t\t\t| header           | \"Klip Rewards\"                                                     |\n\t\t\t| description      | \"Refer friends or complete tasks while using Klip to earn rewards\" |\n\t\t\t| button-text      | \"Start earning\"                                                    |\n\t\t\t| layout           | \"columns\"                                                          |\n\t\t\t| text-color       | <textColor>                                                        |\n\t\t\t| background-color | <backgroundColor>                                                  |\n\t\tThen the two column layout is displayed\n\t\tAnd the text has color <textColor>\n\t\tAnd the background has color <backgroundColor>\n\t\tExamples:\n\t\t\t| textColor | backgroundColor |\n\t\t\t| #fffc4b   | #ff7f7f         |\n\t\t\t| #1d0314   | #4baa1a         |\n\t\t\t| #211a27   | #aa481a         |";
 
 const HeroImage_stories = {
   title: "Components/Hero Image",
   parameters: {
-    scenario: scenario$t,
+    scenario: scenario$u,
   },
 };
 const OverlayHeader = () => {
@@ -12600,12 +12739,12 @@ const HeroImage = /*#__PURE__*/Object.freeze({
   ColumnsCustomColors: ColumnsCustomColors
 });
 
-const scenario$u = "@author:kutay\n@owner:kutay\nFeature: Referral Card\n\n\tThe Referral Card component takes in two slots and displays them side by side.\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the Referral Card component\n\n\t@motivating\n\t@ui\n\tScenario: Referral Card component displays provided content in left and right slots side by side\n\t\tGiven a Referral Card component\n\t\tAnd a slot with the name \"left\"\n\t\tAnd a slot with the name \"right\"\n\t\tWhen the user views the referral card\n\t\tThen the slot contents are displayed the card with equal width\n\t\tWhen the component is scaled down to 499px\n\t\tThen the column layout switches to row layout\n\t\tAnd the \"left\" slot content is displayed above the \"right\" slot content\n\n\t@minutia\n\t@ui\n\tScenario: Left or right column content spans the whole card if there is no content in the other column\n\t\tGiven a Referral Card component\n\t\tAnd there content in one column\n\t\tAnd there is no content in the other column\n\t\tThen the column with content spans 100% of the card width\n\t\tAnd the column with content respects the container's padding\n\t\tAnd the column without content has zero width\n\n\t@motivating\n\t@ui\n\tScenario Outline: Referral Card component content can be vertically aligned start, center, end\n\t\tGiven a Referral Card component\n\t\tAnd a slot with the name \"left\"\n\t\tAnd a slot with the name \"right\"\n\t\tAnd the prop \"vertical-alignment\" has <value>\n\t\tThen slots contents are displayed inside the card\n\t\tAnd slots are vertically aligned to <alignment> of the card\n\t\tExamples:\n\t\t\t| value  | alignment  |\n\t\t\t| start  | the top    |\n\t\t\t| center | the center |\n\t\t\t| end    | the bottom |\n\t\t\t| N/A    | the top    |\n\n\t@ui\n\tScenario Outline: Container border can be toggled\n\t\tGiven a user is viewing the referral card component\n\t\tThen the default value for the prop \"include-border\" is \"true\"\n\t\tWhen \"include-border\" has <value>\n\t\tThen the referral card component's border <maybe> included\n\t\tExamples:\n\t\t\t| value            | maybe |\n\t\t\t| true             | is    |\n\t\t\t| false            | isn't |\n\t\t\t| empty (no value) | is    |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Component background color can be customized\n\t\tGiven a user is viewing the Referral Card component\n\t\tThen the default value is \"#ffffff\"\n\t\tWhen the prop \"background-color\" has <value>\n\t\tThen the background has color <backgroundColor>\n\t\tExamples:\n\t\t\t| value                 | backgroundColor                     |\n\t\t\t| empty (default value) | var(--sl-color-neutral-0) (#ffffff) |\n\t\t\t| aquamarine            | #7fffd4                             |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Container padding can be customized\n\t\tGiven a user is looking at the component\n\t\tThen the default values for \"padding-top\", \"padding-bottom\", \"padding-left\", \"padding-right\" is \"large\"\n\t\tWhen prop \"padding-top\" has <value>\n\t\tThen <padding> is applied to content\n\t\tAnd the same applies to \"padding-bottom\", \"padding-left\", \"padding-right\"\n\n\t\tExamples:\n\t\t\t| value      | padding    |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |";
+const scenario$v = "@author:kutay\n@owner:kutay\nFeature: Referral Card\n\n\tThe Referral Card component takes in two slots and displays them side by side.\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the Referral Card component\n\n\t@motivating\n\t@ui\n\tScenario: Referral Card component displays provided content in left and right slots side by side\n\t\tGiven a Referral Card component\n\t\tAnd a slot with the name \"left\"\n\t\tAnd a slot with the name \"right\"\n\t\tWhen the user views the referral card\n\t\tThen the slot contents are displayed the card with equal width\n\t\tWhen the component is scaled down to 499px\n\t\tThen the column layout switches to row layout\n\t\tAnd the \"left\" slot content is displayed above the \"right\" slot content\n\n\t@minutia\n\t@ui\n\tScenario: Left or right column content spans the whole card if there is no content in the other column\n\t\tGiven a Referral Card component\n\t\tAnd there content in one column\n\t\tAnd there is no content in the other column\n\t\tThen the column with content spans 100% of the card width\n\t\tAnd the column with content respects the container's padding\n\t\tAnd the column without content has zero width\n\n\t@motivating\n\t@ui\n\tScenario Outline: Referral Card component content can be vertically aligned start, center, end\n\t\tGiven a Referral Card component\n\t\tAnd a slot with the name \"left\"\n\t\tAnd a slot with the name \"right\"\n\t\tAnd the prop \"vertical-alignment\" has <value>\n\t\tThen slots contents are displayed inside the card\n\t\tAnd slots are vertically aligned to <alignment> of the card\n\t\tExamples:\n\t\t\t| value  | alignment  |\n\t\t\t| start  | the top    |\n\t\t\t| center | the center |\n\t\t\t| end    | the bottom |\n\t\t\t| N/A    | the top    |\n\n\t@ui\n\tScenario Outline: Container border can be toggled\n\t\tGiven a user is viewing the referral card component\n\t\tThen the default value for the prop \"include-border\" is \"true\"\n\t\tWhen \"include-border\" has <value>\n\t\tThen the referral card component's border <maybe> included\n\t\tExamples:\n\t\t\t| value            | maybe |\n\t\t\t| true             | is    |\n\t\t\t| false            | isn't |\n\t\t\t| empty (no value) | is    |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Component background color can be customized\n\t\tGiven a user is viewing the Referral Card component\n\t\tThen the default value is \"#ffffff\"\n\t\tWhen the prop \"background-color\" has <value>\n\t\tThen the background has color <backgroundColor>\n\t\tExamples:\n\t\t\t| value                 | backgroundColor                     |\n\t\t\t| empty (default value) | var(--sl-color-neutral-0) (#ffffff) |\n\t\t\t| aquamarine            | #7fffd4                             |\n\n\t@motivating\n\t@ui\n\tScenario Outline: Container padding can be customized\n\t\tGiven a user is looking at the component\n\t\tThen the default values for \"padding-top\", \"padding-bottom\", \"padding-left\", \"padding-right\" is \"large\"\n\t\tWhen prop \"padding-top\" has <value>\n\t\tThen <padding> is applied to content\n\t\tAnd the same applies to \"padding-bottom\", \"padding-left\", \"padding-right\"\n\n\t\tExamples:\n\t\t\t| value      | padding    |\n\t\t\t| none       | no padding |\n\t\t\t| xxx-small  | xxx-small  |\n\t\t\t| xx-small   | xx-small   |\n\t\t\t| x-small    | x-small    |\n\t\t\t| small      | small      |\n\t\t\t| medium     | medium     |\n\t\t\t| large      | large      |\n\t\t\t| x-large    | x-large    |\n\t\t\t| xx-large   | xx-large   |\n\t\t\t| xxx-large  | xxx-large  |\n\t\t\t| xxxx-large | xxxx-large |\n\t\t\t| N/A        | no padding |";
 
 const ReferralCard_stories = {
   title: "Components/Referral Card",
   parameters: {
-    scenario: scenario$u,
+    scenario: scenario$v,
   },
 };
 const media = (slot) => {
@@ -12738,11 +12877,11 @@ const scenarioTimeline = "@author:derek\n@owner:kutay\nFeature: Timeline\n\n
 
 const scenarioTimelineEntry = "@author:derek\n@owner:kutay\nFeature: Timeline Entry\n\n    @motivating\n    @ui\n    Scenario: Timeline entries have an icon, a reward and an entry desciption\n        Given an timeline entry with the following props\n            | prop   | value                                               |\n            | unit   | Visa Giftcard                                       |\n            | reward | 50$                                                 |\n            | desc   | Earn a 50$ Visa Giftcard for each referral you make |\n        When a user views the entry\n        Then they see a gift icon\n        And see \"$50 VISA GIFTCARRD\" to the right\n        And \"$50\" is bolded with x-large font size\n        And below they see \"Earn a 50$ Visa Giftcard for each referral you make\"\n\n    @motivating\n    @ui\n    Scenario Outline: Icon can either be a gift or a brand colour cirle\n        Given a timeline entry with \"icon\" <iconPropValue>\n        When a user views the entry\n        Then they see an <icon>\n        Examples:\n            | iconPropValue 1 | icon                |\n            | gift            | gift                |\n            | circle          | brand colour circle |\n            |                 | gift                |\n\n    @motivating\n    @ui\n    Scenario: A timeline entry can display a line to connect it to another entry\n        Given a timeline entry with \"line\" \"true\"\n        When a user views the entry\n        Then they see the entry\n        But it has a brand colour line connecting it to the next timeline entry\n";
 
-const scenario$v = scenarioTimeline + scenarioTimelineEntry;
+const scenario$w = scenarioTimeline + scenarioTimelineEntry;
 const Timeline_stories = {
   title: "Components/Timeline",
   parameters: {
-    scenario: scenario$v,
+    scenario: scenario$w,
   },
 };
 const TimelineWith1Reward = () => {
@@ -12815,12 +12954,12 @@ const Timeline = /*#__PURE__*/Object.freeze({
   TimelineWith4Rewards: TimelineWith4Rewards
 });
 
-const scenario$w = "@author:kutay\n@owner:kutay\nFeature: Image\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the image component\n\n\t@motivating\n\t@ui\n\tScenario: Image is displayed from URL\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided with a valid image url\n\t\tThen the image is displayed\n\t\tAnd it is centered\n\n\t@motivating\n\t@ui\n\tScenario Outline: Images can be aligned left, center or right\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided with a valid image url\n\t\tAnd prop \"align\" has <value>\n\t\tThen the image is displayed\n\t\tAnd it is aligned to the <value>\n\t\tExamples:\n\t\t\t| value  |\n\t\t\t| left   |\n\t\t\t| center |\n\t\t\t| right  |\n\n\t@motivating\n\t@ui\n\tScenario: Image background can be assigned a color\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided with a valid image url\n\t\tAnd prop \"background-color\" is provided a color\n\t\tThen the image is displayed\n\t\tAnd the background is the provided color\n\n\t@motivating\n\t@ui\n\tScenario: Image minimum height can be constrained\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided\n\t\tAnd prop \"min-height\" is given a minimum value\n\t\tThen the image is displayed\n\t\tAnd the container size changes\n\t\tThen the image does not shrink below its minimum height";
+const scenario$x = "@author:kutay\n@owner:kutay\nFeature: Image\n\n\tBackground: A user on the portal is viewing the widget\n\t\tGiven a user viewing the image component\n\n\t@motivating\n\t@ui\n\tScenario: Image is displayed from URL\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided with a valid image url\n\t\tThen the image is displayed\n\t\tAnd it is centered\n\n\t@motivating\n\t@ui\n\tScenario Outline: Images can be aligned left, center or right\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided with a valid image url\n\t\tAnd prop \"align\" has <value>\n\t\tThen the image is displayed\n\t\tAnd it is aligned to the <value>\n\t\tExamples:\n\t\t\t| value  |\n\t\t\t| left   |\n\t\t\t| center |\n\t\t\t| right  |\n\n\t@motivating\n\t@ui\n\tScenario: Image background can be assigned a color\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided with a valid image url\n\t\tAnd prop \"background-color\" is provided a color\n\t\tThen the image is displayed\n\t\tAnd the background is the provided color\n\n\t@motivating\n\t@ui\n\tScenario: Image minimum height can be constrained\n\t\tGiven an Image component\n\t\tAnd prop \"image-url\" is provided\n\t\tAnd prop \"min-height\" is given a minimum value\n\t\tThen the image is displayed\n\t\tAnd the container size changes\n\t\tThen the image does not shrink below its minimum height";
 
 const Image_stories = {
   title: "Components/Image",
   parameters: {
-    scenario: scenario$w,
+    scenario: scenario$x,
   },
 };
 const Image = () => {
@@ -12853,12 +12992,12 @@ const Image$1 = /*#__PURE__*/Object.freeze({
   MinimumHeight: MinimumHeight
 });
 
-const scenario$x = "@author:derek\n@owner:noah\nFeature: Titled Section\n\n    Background: The titled section has a label and content\n        Given a titled section\n        And it has a label\n        And it has content in the content slot\n\n    @motivating\n    @ui\n    Scenario: Text alignment defaults to left align but can be configured\n        Given the titled section has \"text-align\" <textAlignPropValue>\n        When a user views the titled section\n        Then the text in the label is <aligned>\n        And the text in the content is <aligned>\n        Examples:\n            | textAlignPropValue | aligned |\n            | center             | center  |\n            | left               | left    |\n            | right              | right   |\n            |                    | left    |\n\n    @minutia\n    @ui\n    Scenario: Label margin is configurable\n        Given the titled section has \"label-margin\" <marginPropValue>\n        When a user views the titled section\n        Then <marginPropValue> margin is between the label and content\n        Examples:\n            | marginPropValue | margin     |\n            | none            | no         |\n            | xxx-small       | xxx-small  |\n            | xx-small        | xx-small   |\n            | x-small         | x-small    |\n            | small           | small      |\n            | medium          | medium     |\n            | large           | large      |\n            | x-large         | x-large    |\n            | xx-large        | xx-large   |\n            | xxx-large       | xxx-large  |\n            | xxxx-large      | xxxx-large |\n            |                 | no         |\n\n    @minutia\n    @ui\n    Scenario Outline: Titled section padding is configurable\n        Given the titled section has \"padding\" <paddingPropValue>\n        When a user views the titled section\n        Then <paddingPropValue> padding is applied around the titled section\n        Examples:\n            | paddingPropValue | padding    |\n            | none             | no         |\n            | xxx-small        | xxx-small  |\n            | xx-small         | xx-small   |\n            | x-small          | x-small    |\n            | small            | small      |\n            | medium           | medium     |\n            | large            | large      |\n            | x-large          | x-large    |\n            | xx-large         | xx-large   |\n            | xxx-large        | xxx-large  |\n            | xxxx-large       | xxxx-large |\n            |                  | no         |";
+const scenario$y = "@author:derek\n@owner:noah\nFeature: Titled Section\n\n    Background: The titled section has a label and content\n        Given a titled section\n        And it has a label\n        And it has content in the content slot\n\n    @motivating\n    @ui\n    Scenario: Text alignment defaults to left align but can be configured\n        Given the titled section has \"text-align\" <textAlignPropValue>\n        When a user views the titled section\n        Then the text in the label is <aligned>\n        And the text in the content is <aligned>\n        Examples:\n            | textAlignPropValue | aligned |\n            | center             | center  |\n            | left               | left    |\n            | right              | right   |\n            |                    | left    |\n\n    @minutia\n    @ui\n    Scenario: Label margin is configurable\n        Given the titled section has \"label-margin\" <marginPropValue>\n        When a user views the titled section\n        Then <marginPropValue> margin is between the label and content\n        Examples:\n            | marginPropValue | margin     |\n            | none            | no         |\n            | xxx-small       | xxx-small  |\n            | xx-small        | xx-small   |\n            | x-small         | x-small    |\n            | small           | small      |\n            | medium          | medium     |\n            | large           | large      |\n            | x-large         | x-large    |\n            | xx-large        | xx-large   |\n            | xxx-large       | xxx-large  |\n            | xxxx-large      | xxxx-large |\n            |                 | no         |\n\n    @minutia\n    @ui\n    Scenario Outline: Titled section padding is configurable\n        Given the titled section has \"padding\" <paddingPropValue>\n        When a user views the titled section\n        Then <paddingPropValue> padding is applied around the titled section\n        Examples:\n            | paddingPropValue | padding    |\n            | none             | no         |\n            | xxx-small        | xxx-small  |\n            | xx-small         | xx-small   |\n            | x-small          | x-small    |\n            | small            | small      |\n            | medium           | medium     |\n            | large            | large      |\n            | x-large          | x-large    |\n            | xx-large         | xx-large   |\n            | xxx-large        | xxx-large  |\n            | xxxx-large       | xxxx-large |\n            |                  | no         |";
 
 const TitledSection_stories = {
   title: "Components/Titled Section",
   parameters: {
-    scenario: scenario$x,
+    scenario: scenario$y,
   },
 };
 const AlignLeft = () => {
@@ -13254,12 +13393,12 @@ const Scroll = /*#__PURE__*/Object.freeze({
   ShoelaceProps: ShoelaceProps
 });
 
-const scenario$y = "@author:Zach\n@owner:Zach\nFeature: Tabs\n\n  The Tabs takes in the Tab component as children and maps through to display their header and content.\n\n  Background: A user on the portal is viewing the widget\n    Given a user viewing the Tabs component\n\n  @motivating\n  Scenario: Content inside the active tab is shown\n    Given the header is set to <tabHeader>\n    And the content inside is <tabContent>\n    And the user has clicked <tabHeader>\n    Then the <tabContent> is shown\n    Examples:\n      | tabHeader | tabContent               |\n      | Settings  | This is the settings tab |\n      | General   | This is the general tab  |\n      | History   | This is the history tab  |\n\n  @motivating\n  @ui\n  Scenario: The placement of the tabs is configurable\n    Given The placement prop has been passed a valid <placement>\n    Then tabs are placed on the <placementResult>\n    Examples:\n      | placement | placementResult                |\n      |           | top of the content             |\n      | left      | left hand side of the content  |\n      | right     | right hand side of the content |\n      | bottom    | bottom of the content          |\n\n\n  @minutia\n  @ui\n  Scenario Outline: Tabs are setup to use the brand color\n    Given the brand color is set to darkblue\n    Then the text inside the active tab is darkblue\n    And the underline of the active tab is darkblue\n\n  @ui\n  Scenario: Tabs are responsive\n    Given the user is on a mobile device\n    When there are more tabs than the horizontal space allows for\n    Then clickable arrows appear on the left and right of the tabs\n    And the tabs are scrollable\n\n  @landmine\n  Scenario: Program section cannot be used inside of tabs\n    Given a tabs component\n    And tab containing a program section with program-id \"test123\"\n    And the program section wraps a component using program context\n    When the tabs component is rendered\n    Then the \"sq:program-id\" event listener for the program section is removed\n    And the component does not use program-id \"test123\" to source its data\n    And falls back to the global program id";
+const scenario$z = "@author:Zach\n@owner:Zach\nFeature: Tabs\n\n  The Tabs takes in the Tab component as children and maps through to display their header and content.\n\n  Background: A user on the portal is viewing the widget\n    Given a user viewing the Tabs component\n\n  @motivating\n  Scenario: Content inside the active tab is shown\n    Given the header is set to <tabHeader>\n    And the content inside is <tabContent>\n    And the user has clicked <tabHeader>\n    Then the <tabContent> is shown\n    Examples:\n      | tabHeader | tabContent               |\n      | Settings  | This is the settings tab |\n      | General   | This is the general tab  |\n      | History   | This is the history tab  |\n\n  @motivating\n  @ui\n  Scenario: The placement of the tabs is configurable\n    Given The placement prop has been passed a valid <placement>\n    Then tabs are placed on the <placementResult>\n    Examples:\n      | placement | placementResult                |\n      |           | top of the content             |\n      | left      | left hand side of the content  |\n      | right     | right hand side of the content |\n      | bottom    | bottom of the content          |\n\n\n  @minutia\n  @ui\n  Scenario Outline: Tabs are setup to use the brand color\n    Given the brand color is set to darkblue\n    Then the text inside the active tab is darkblue\n    And the underline of the active tab is darkblue\n\n  @ui\n  Scenario: Tabs are responsive\n    Given the user is on a mobile device\n    When there are more tabs than the horizontal space allows for\n    Then clickable arrows appear on the left and right of the tabs\n    And the tabs are scrollable\n\n  @landmine\n  Scenario: Program section cannot be used inside of tabs\n    Given a tabs component\n    And tab containing a program section with program-id \"test123\"\n    And the program section wraps a component using program context\n    When the tabs component is rendered\n    Then the \"sq:program-id\" event listener for the program section is removed\n    And the component does not use program-id \"test123\" to source its data\n    And falls back to the global program id";
 
 const Tabs_stories = {
   title: "Components/Tabs",
   parameters: {
-    scenario: scenario$y,
+    scenario: scenario$z,
   },
 };
 const SimpleTabs = () => (h("div", { style: { maxWidth: "700px", margin: "auto" }, innerHTML: `
@@ -13759,12 +13898,12 @@ const Tabs = /*#__PURE__*/Object.freeze({
   RightTabs: RightTabs
 });
 
-const scenario$z = "@author:johan\n@owner:johan\nFeature: Share Code\n\n  The share code component is a box that allows users to see and copy their referral code for a given program\n\n  Background: Environment\n    Given there is a valid program ID in the environment\n    And there is a valid user ID and account ID in the environment\n\n  @motivating\n  Scenario: A Users referral code can be copied to their clipboard\n    Given tooltiptext is \"hello tooltip\"\n    When the component renders\n    Then there is a textbox with the user's share code\n    When the clipboard icon is clicked\n    Then the code is copied to clipboard\n    And a tooltip will appear for ~1 second\n\n  @minutia\n  Scenario: Tooltip lifespan defaults to 2000\n    Given the tooltip's lifespan is set to 2000\n    And there is tooltip text\n    When the component renders\n    And the clipboard icon is clicked\n    Then a tooltip will appear for ~2 seconds\n\n  @minutia\n  Scenario: Demo\n    Given isDemo() returns true\n    Then the share code is \"SHARECODE001\"\n    And the component won't be interactive\n    And the tooltip is hidden\n\n  @minutia\n  Scenario: Program ID can be sourced from prop\n    Given the programId prop is set to \"program-a\"\n    And window.widgetIdent.programId is set to \"program-b\"\n    When the component renders\n    Then the share code is for \"program-a\"\n\n  @minutia\n  Scenario: Program ID can be sourced from window\n    Given the programId prop is unset\n    And window.widgetIdent.programId is set to \"program-b\"\n    When the component renders\n    Then the share code is for \"program-b\"\n\n  @minutia\n  Scenario: An analytic event is fired when a user copies their code\n    Given a user viewing the share code component\n    And the component is rendered for \"program-a\"\n    When they click to copy their code\n    Then an \"USER_REFERRAL_PROGRAM_ENGAGEMENT_EVENT\" analytic event is fired\n    And it is for \"program-a\"\n    And it has share medium \"DIRECT\"\n\n\n  @ui\n  Scenario Outline: user can edit the alignment of the share code text\n    Given a user is editing the share code component\n    Then they see \"Align text\" props\n    And the default value is \"left\"\n    When they change the option to <option>\n    Then they see the text in <position>\n    Examples:\n      | option | position |\n      | left   | left     |\n      | center | center   |\n      | right  | right    |\n\n  @ui\n  Scenario Outline: The position of the copy button can be changed\n    Given a user is editing the share code component\n    Then they see \"Style\" props\n    And the default value is \"icon\"\n    When they change the option to <option>\n    Then they see the copy button in <position>\n    Examples:\n      | option         | position                        |\n      | button outside | outside the input, on the right |\n      | button below   | outside the input, below        |\n      | icon           | inside the input as an icon     |\n";
+const scenario$A = "@author:johan\n@owner:johan\nFeature: Share Code\n\n  The share code component is a box that allows users to see and copy their referral code for a given program\n\n  Background: Environment\n    Given there is a valid program ID in the environment\n    And there is a valid user ID and account ID in the environment\n\n  @motivating\n  Scenario: A Users referral code can be copied to their clipboard\n    Given tooltiptext is \"hello tooltip\"\n    When the component renders\n    Then there is a textbox with the user's share code\n    When the clipboard icon is clicked\n    Then the code is copied to clipboard\n    And a tooltip will appear for ~1 second\n\n  @minutia\n  Scenario: Tooltip lifespan defaults to 2000\n    Given the tooltip's lifespan is set to 2000\n    And there is tooltip text\n    When the component renders\n    And the clipboard icon is clicked\n    Then a tooltip will appear for ~2 seconds\n\n  @minutia\n  Scenario: Demo\n    Given isDemo() returns true\n    Then the share code is \"SHARECODE001\"\n    And the component won't be interactive\n    And the tooltip is hidden\n\n  @minutia\n  Scenario: Program ID can be sourced from prop\n    Given the programId prop is set to \"program-a\"\n    And window.widgetIdent.programId is set to \"program-b\"\n    When the component renders\n    Then the share code is for \"program-a\"\n\n  @minutia\n  Scenario: Program ID can be sourced from window\n    Given the programId prop is unset\n    And window.widgetIdent.programId is set to \"program-b\"\n    When the component renders\n    Then the share code is for \"program-b\"\n\n  @minutia\n  Scenario: An analytic event is fired when a user copies their code\n    Given a user viewing the share code component\n    And the component is rendered for \"program-a\"\n    When they click to copy their code\n    Then an \"USER_REFERRAL_PROGRAM_ENGAGEMENT_EVENT\" analytic event is fired\n    And it is for \"program-a\"\n    And it has share medium \"DIRECT\"\n\n\n  @ui\n  Scenario Outline: user can edit the alignment of the share code text\n    Given a user is editing the share code component\n    Then they see \"Align text\" props\n    And the default value is \"left\"\n    When they change the option to <option>\n    Then they see the text in <position>\n    Examples:\n      | option | position |\n      | left   | left     |\n      | center | center   |\n      | right  | right    |\n\n  @ui\n  Scenario Outline: The position of the copy button can be changed\n    Given a user is editing the share code component\n    Then they see \"Style\" props\n    And the default value is \"icon\"\n    When they change the option to <option>\n    Then they see the copy button in <position>\n    Examples:\n      | option         | position                        |\n      | button outside | outside the input, on the right |\n      | button below   | outside the input, below        |\n      | icon           | inside the input as an icon     |\n";
 
 const ShareCode_stories = {
   title: "Components/Share Code",
   parameters: {
-    scenario: scenario$z,
+    scenario: scenario$A,
   },
 };
 const ShareCode = () => {
@@ -13829,7 +13968,7 @@ const EmailRegistration_stories = {
   // scenario,
   },
 };
-const defaultProps$d = {
+const defaultProps$e = {
   states: {
     error: "",
     loading: false,
@@ -13848,59 +13987,59 @@ const defaultProps$d = {
     fraudErrorMessageTitle: "Looks like you tried referring yourself",
   },
 };
-const Default$e = () => h(EmailRegistrationView, Object.assign({}, defaultProps$d));
+const Default$g = () => h(EmailRegistrationView, Object.assign({}, defaultProps$e));
 const HasFirstNameLastName = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   content: {
-    ...defaultProps$d.content,
+    ...defaultProps$e.content,
     includeName: true,
   },
 })));
 const WithSlots = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   content: {
-    ...defaultProps$d.content,
+    ...defaultProps$e.content,
     topSlot: h("div", null, "Hello this is the top slot"),
     bottomSlot: h("div", null, "Hello this is the bottom slot"),
   },
 })));
 const NoBorder$1 = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   content: {
-    ...defaultProps$d.content,
+    ...defaultProps$e.content,
     hideBorder: true,
   },
 })));
 const BackgroundColor$2 = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   content: {
-    ...defaultProps$d.content,
+    ...defaultProps$e.content,
     backgroundColor: "aquamarine",
   },
 })));
 const Loading$4 = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   states: {
     error: "",
     loading: true,
   },
 })));
 const Error$8 = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   states: {
     error: "Something went wrong. Please try again.",
     loading: false,
   },
 })));
 const FraudError = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   states: {
     error: "FRAUD",
     loading: false,
   },
 })));
 const EmptyEmailError = () => (h(EmailRegistrationView, Object.assign({}, {
-  ...defaultProps$d,
+  ...defaultProps$e,
   states: {
     error: "Something went wrong. Please try again.",
     loading: false,
@@ -13913,7 +14052,7 @@ const EmptyEmailError = () => (h(EmailRegistrationView, Object.assign({}, {
 const EmailRegistration = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': EmailRegistration_stories,
-  Default: Default$e,
+  Default: Default$g,
   HasFirstNameLastName: HasFirstNameLastName,
   WithSlots: WithSlots,
   NoBorder: NoBorder$1,
@@ -13924,15 +14063,15 @@ const EmailRegistration = /*#__PURE__*/Object.freeze({
   EmptyEmailError: EmptyEmailError
 });
 
-const scenario$A = "@author:truman\n@owner:truman\nFeature: Coupon Code\n\n  The coupon code component is a box that allows users to see and copy their coupon code for a given program\n\n  @motivating\n  Scenario: Component only fetches codes from current program\n    Given a user has multiple rewards from various programs\n    When the component is loaded\n    Then it fetches the user's rewards from only the program associated with the widget\n\n  @motivating\n  Scenario: Component only looks at fueltank rewards\n    Given a user has multiple rewards of different types\n    When the component is loaded\n    Then it filters the user's reward to only return FUELTANK rewards\n\n\n  @motivating\n  Scenario: The first (i.e. most recently received) reward is the reward that is displayed\n    Given a user has at least one fueltank reward\n    And the fueltank reward is available\n    Then the coupon code component shows the first reward returned\n    And this reward is the most recently received reward by the user\n\n  @motivating\n  Scenario Outline: Coupon code has multiple states depending on reward status\n    Given a user has at least one fueltank reward\n    And the reward has most recent status <status>\n    And the dateScheduledFor field is <dateScheduledFor>\n    Then the component's status is set to <componentStatus>\n    And the <errorMessageTextProp> is displayed under the input field\n\n    Examples:\n      | status    | dateScheduledFor | componentStatus | errorMessageTextProp     |\n      | AVAILABLE | null             | AVAILABLE       | N/A                      |\n      | EXPIRED   | null             | EXPIRED         | expiredErrorMessage      |\n      | REDEEMED  | null             | REDEEMED        | redeemedMessage          |\n      | CANCELLED | null             | CANCELLED       | cancelledErrorMessage    |\n      | PENDING   | null             | EMPTY_TANK      | fullfillmentErrorMessage |\n      | PENDING   | 123412341234     | PENDING         | pendingErrorMessage      |\n      | null      | null             | ERROR           | genericErrorMessage      |\n\n  Scenario Outline: Coupon code's error message text props are grouped\n    Given an end user is viewing the coupon code component in the widget editor\n    And they are looking at the component's properties\n    Then they see <prop>\n    And <prop> is grouped under \"Coupon code error\"\n    Examples:\n      | prop                     |\n      | N/A                      |\n      | expiredErrorMessage      |\n      | redeemedMessage          |\n      | cancelledErrorMessage    |\n      | fullfillmentErrorMessage |\n      | pendingErrorMessage      |\n      | genericErrorMessage      |\n\n  @minutia\n  Scenario: Tooltip lifespan defaults to 2000\n    Given the tooltip's lifespan is set to 2000\n    And there is tooltip text\n    When the component renders\n    And the clipboard icon is clicked\n    Then a tooltip appears for ~2 seconds\n\n  @ui\n  Scenario: Component shows an error state when there is an error\n    Given a user is viewing the coupon code component\n    When there is an error in the coupon code\n    Then in place of the coupon code is an alert banner\n    And the alert banner gives information about the error to the user\n\n  @ui\n  Scenario: Component shows an loading state\n    Given a user is viewing the coupon code component\n    When the coupon code is loading in\n    Then the text inside the input is \"Loading...\"\n    And the coupon code input box has a gray background\n    And the cursor is set to \"default\"\n    And the user cannot copy the text\n\n  @ui\n  Scenario Outline: User can edit the alignment of the coupon code text\n    Given a user is editing the coupon code component\n    Then they see \"Align text\" props\n    And the default value is \"left\"\n    When they change the option to <option>\n    Then they see the text in <position>\n    Examples:\n      | option | position |\n      | left   | left     |\n      | center | center   |\n      | right  | right    |\n\n  @ui\n  Scenario Outline: The position of the copy button can be changed\n    Given a user is editing the coupon code component\n    Then they see \"Style\" props\n    And the default value is \"icon\"\n    When they change the option to <option>\n    Then they see the copy button in <position>\n    Examples:\n      | option         | position                        |\n      | button outside | outside the input, on the right |\n      | button below   | outside the input, below        |\n      | icon           | inside the input as an icon     |\n\n  @minutia\n  Scenario: ICU string converts to a date\n    Given a user is viewing a live coupon code code component\n    And the \"pendingErrorText\" has the \"{unpendDate}\" ICU string\n    And the program is configured for rewards to be pending\n    Then the user will see an info alert banner\n    And the ICU string is converted to the unpend date\n";
+const scenario$B = "@author:truman\n@owner:truman\nFeature: Coupon Code\n\n  The coupon code component is a box that allows users to see and copy their coupon code for a given program\n\n  @motivating\n  Scenario: Component only fetches codes from current program\n    Given a user has multiple rewards from various programs\n    When the component is loaded\n    Then it fetches the user's rewards from only the program associated with the widget\n\n  @motivating\n  Scenario: Component only looks at fueltank rewards\n    Given a user has multiple rewards of different types\n    When the component is loaded\n    Then it filters the user's reward to only return FUELTANK rewards\n\n\n  @motivating\n  Scenario: The first (i.e. most recently received) reward is the reward that is displayed\n    Given a user has at least one fueltank reward\n    And the fueltank reward is available\n    Then the coupon code component shows the first reward returned\n    And this reward is the most recently received reward by the user\n\n  @motivating\n  Scenario Outline: Coupon code has multiple states depending on reward status\n    Given a user has at least one fueltank reward\n    And the reward has most recent status <status>\n    And the dateScheduledFor field is <dateScheduledFor>\n    Then the component's status is set to <componentStatus>\n    And the <errorMessageTextProp> is displayed under the input field\n\n    Examples:\n      | status    | dateScheduledFor | componentStatus | errorMessageTextProp     |\n      | AVAILABLE | null             | AVAILABLE       | N/A                      |\n      | EXPIRED   | null             | EXPIRED         | expiredErrorMessage      |\n      | REDEEMED  | null             | REDEEMED        | redeemedMessage          |\n      | CANCELLED | null             | CANCELLED       | cancelledErrorMessage    |\n      | PENDING   | null             | EMPTY_TANK      | fullfillmentErrorMessage |\n      | PENDING   | 123412341234     | PENDING         | pendingErrorMessage      |\n      | null      | null             | ERROR           | genericErrorMessage      |\n\n  Scenario Outline: Coupon code's error message text props are grouped\n    Given an end user is viewing the coupon code component in the widget editor\n    And they are looking at the component's properties\n    Then they see <prop>\n    And <prop> is grouped under \"Coupon code error\"\n    Examples:\n      | prop                     |\n      | N/A                      |\n      | expiredErrorMessage      |\n      | redeemedMessage          |\n      | cancelledErrorMessage    |\n      | fullfillmentErrorMessage |\n      | pendingErrorMessage      |\n      | genericErrorMessage      |\n\n  @minutia\n  Scenario: Tooltip lifespan defaults to 2000\n    Given the tooltip's lifespan is set to 2000\n    And there is tooltip text\n    When the component renders\n    And the clipboard icon is clicked\n    Then a tooltip appears for ~2 seconds\n\n  @ui\n  Scenario: Component shows an error state when there is an error\n    Given a user is viewing the coupon code component\n    When there is an error in the coupon code\n    Then in place of the coupon code is an alert banner\n    And the alert banner gives information about the error to the user\n\n  @ui\n  Scenario: Component shows an loading state\n    Given a user is viewing the coupon code component\n    When the coupon code is loading in\n    Then the text inside the input is \"Loading...\"\n    And the coupon code input box has a gray background\n    And the cursor is set to \"default\"\n    And the user cannot copy the text\n\n  @ui\n  Scenario Outline: User can edit the alignment of the coupon code text\n    Given a user is editing the coupon code component\n    Then they see \"Align text\" props\n    And the default value is \"left\"\n    When they change the option to <option>\n    Then they see the text in <position>\n    Examples:\n      | option | position |\n      | left   | left     |\n      | center | center   |\n      | right  | right    |\n\n  @ui\n  Scenario Outline: The position of the copy button can be changed\n    Given a user is editing the coupon code component\n    Then they see \"Style\" props\n    And the default value is \"icon\"\n    When they change the option to <option>\n    Then they see the copy button in <position>\n    Examples:\n      | option         | position                        |\n      | button outside | outside the input, on the right |\n      | button below   | outside the input, below        |\n      | icon           | inside the input as an icon     |\n\n  @minutia\n  Scenario: ICU string converts to a date\n    Given a user is viewing a live coupon code code component\n    And the \"pendingErrorText\" has the \"{unpendDate}\" ICU string\n    And the program is configured for rewards to be pending\n    Then the user will see an info alert banner\n    And the ICU string is converted to the unpend date\n";
 
 const CouponCode_stories = {
   title: "Components/Coupon Code",
   parameters: {
-    scenario: scenario$A,
+    scenario: scenario$B,
   },
 };
-const defaultProps$e = {
+const defaultProps$f = {
   tooltiptext: "Copied to Clipboard",
   copyString: "THANKSJANE125uv125",
   open: false,
@@ -13957,43 +14096,43 @@ const TextAlignRight$2 = () => {
   return h("sqm-coupon-code", { textAlign: "right" });
 };
 const CopyButton$2 = () => {
-  return (h("sqm-coupon-code", Object.assign({}, defaultProps$e, { buttonStyle: "button-outside" })));
+  return (h("sqm-coupon-code", Object.assign({}, defaultProps$f, { buttonStyle: "button-outside" })));
 };
 const CopyButtonCustomLabel = () => {
-  return (h("sqm-coupon-code", Object.assign({}, defaultProps$e, { buttonStyle: "button-outside", "copy-button-label": "test long custom label" })));
+  return (h("sqm-coupon-code", Object.assign({}, defaultProps$f, { buttonStyle: "button-outside", "copy-button-label": "test long custom label" })));
 };
 const CopyButtonBelow$2 = () => {
-  return (h("sqm-coupon-code", Object.assign({}, defaultProps$e, { buttonStyle: "button-below" })));
+  return (h("sqm-coupon-code", Object.assign({}, defaultProps$f, { buttonStyle: "button-below" })));
 };
 const CopyButtonBelowCustomLabel = () => {
-  return (h("sqm-coupon-code", Object.assign({}, defaultProps$e, { buttonStyle: "button-below", "copy-button-label": "test long custom label" })));
+  return (h("sqm-coupon-code", Object.assign({}, defaultProps$f, { buttonStyle: "button-below", "copy-button-label": "test long custom label" })));
 };
 const Loading$5 = () => {
-  return h(CouponCodeView, Object.assign({}, defaultProps$e, { loading: true }));
+  return h(CouponCodeView, Object.assign({}, defaultProps$f, { loading: true }));
 };
 const CopyButtonLoading = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { buttonStyle: "button-outside", loading: true })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { buttonStyle: "button-outside", loading: true })));
 };
 const CopyButtonBelowLoading = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { buttonStyle: "button-below", loading: true })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { buttonStyle: "button-below", loading: true })));
 };
 const ErrorGeneric = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { errorType: "warning", error: true, errorText: "We couldn't fetch your code. Please try again later or reach out to the Support team for help resolving this issue." })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { errorType: "warning", error: true, errorText: "We couldn't fetch your code. Please try again later or reach out to the Support team for help resolving this issue." })));
 };
 const ErrorPending = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { errorType: "info", error: true, errorText: "Your code will be available on April 24, 2023. Mark your calendar and come back then to redeem your reward!" })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { errorType: "info", error: true, errorText: "Your code will be available on April 24, 2023. Mark your calendar and come back then to redeem your reward!" })));
 };
 const ErrorFullfillment = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { errorType: "warning", error: true, errorText: "We couldn't fetch your code. Please try again later or reach out to the Support team for help resolving this issue." })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { errorType: "warning", error: true, errorText: "We couldn't fetch your code. Please try again later or reach out to the Support team for help resolving this issue." })));
 };
 const ErrorCancelled = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { errorType: "warning", error: true, errorText: "This code has been cancelled. Please reach out to the Support team for help resolving this issue." })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { errorType: "warning", error: true, errorText: "This code has been cancelled. Please reach out to the Support team for help resolving this issue." })));
 };
 const ErrorExpired = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { errorType: "warning", error: true, errorText: "Looks like this code has expired. Please reach out to the Support team for help resolving this issue." })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { errorType: "warning", error: true, errorText: "Looks like this code has expired. Please reach out to the Support team for help resolving this issue." })));
 };
 const ErrorRedeemed = () => {
-  return (h(CouponCodeView, Object.assign({}, defaultProps$e, { errorType: "success", error: true, errorText: "Looks like you\u2019ve already redeemed this code." })));
+  return (h(CouponCodeView, Object.assign({}, defaultProps$f, { errorType: "success", error: true, errorText: "Looks like you\u2019ve already redeemed this code." })));
 };
 
 const CouponCode$1 = /*#__PURE__*/Object.freeze({
@@ -14019,55 +14158,55 @@ const CouponCode$1 = /*#__PURE__*/Object.freeze({
   ErrorRedeemed: ErrorRedeemed
 });
 
-const scenario$B = "@author:noah\n@owner:noah\n\nFeature: Logout Current User\n\n  Background:\n    Given a user viewing an instant access widget\n\n  @motivating\n  @ui\n  Scenario: A user on an instant access widget\n    Given the user is identified\n    And the user is logged in\n    Then the component identifies the user by displaying their email in an ICU string\n    And the users email displayed in the ICU string using hte \"{email}\" variable\n\n  @motivating\n  @ui\n  Scenario: Users can switch who they are identified as through a link\n    Given the user is identified\n    And the user is logged in\n    When the user clicks the link in the component\n    Then the saved user identity is emptied\n    And they are sent back to the registration form to re-identify themselves\n\n  @minutia\n  Scenario: Logout link empties the saved User Identity\n    Given a valid user identity\n    And the user is viewing the \"logged-in\" template\n    When they click the logout link\n    Then the user identity is set to \"undefined\"\n    And the user is returned to the \"logged-out\" template";
+const scenario$C = "@author:noah\n@owner:noah\n\nFeature: Logout Current User\n\n  Background:\n    Given a user viewing an instant access widget\n\n  @motivating\n  @ui\n  Scenario: A user on an instant access widget\n    Given the user is identified\n    And the user is logged in\n    Then the component identifies the user by displaying their email in an ICU string\n    And the users email displayed in the ICU string using hte \"{email}\" variable\n\n  @motivating\n  @ui\n  Scenario: Users can switch who they are identified as through a link\n    Given the user is identified\n    And the user is logged in\n    When the user clicks the link in the component\n    Then the saved user identity is emptied\n    And they are sent back to the registration form to re-identify themselves\n\n  @minutia\n  Scenario: Logout link empties the saved User Identity\n    Given a valid user identity\n    And the user is viewing the \"logged-in\" template\n    When they click the logout link\n    Then the user identity is set to \"undefined\"\n    And the user is returned to the \"logged-out\" template";
 
 const LogoutCurrentUser_stories = {
   title: "Components/Logout Current User",
   parameters: {
-    scenario: scenario$B,
+    scenario: scenario$C,
   },
 };
-const defaultProps$f = {
+const defaultProps$g = {
   filledInEmailText: "Currently showing referral data for noah.clarke@saasquatch.com",
   onSwitchClick: () => console.log("clicked"),
   switchUserText: "not you?",
   loading: false,
   emailErrorText: "Error fetching email",
 };
-const Default$f = () => {
-  return h(LogoutCurrentUserView, Object.assign({}, defaultProps$f));
+const Default$h = () => {
+  return h(LogoutCurrentUserView, Object.assign({}, defaultProps$g));
 };
 
 const LogoutCurrentUser = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': LogoutCurrentUser_stories,
-  Default: Default$f
+  Default: Default$h
 });
 
-const scenario$C = "@author:noah\n@owner:noah\n\nFeature: Link Button\n\n\t@ui\n\tScenario: Links can be opened in the same tab\n\t\tWhen a user clicks the button\n\t\tThen a link opens in the same tab\n\t\tAnd if the component is in an iFrame then the link is opened in the parent window not the iFrame\n\n\t@ui\n\tScenario: Links can be opened in a new tab\n\t\tWhen a user clicks the button\n\t\tThen a link opens in a new tab\n\t\tAnd if the component is in an iFrame then the link is still opened in a new tab\n\n\n\t@ui\n\tScenario: Props control the link and button text\n\t\tGiven the \"link\" prop is set to \"https://www.example.com\"\n\t\tAnd the \"buttonText\" prop is set to \"Click me!\"\n\t\tThen a button is shown with the text \"Click me!\"\n\t\tAnd when clicked the button opens https://www.example.com\n\n\t@ui\n\tScenario Outline: The button type can be set\n\t\tGiven the button type is set to <value>\n\t\tThen a <buttonType> is shown\n\t\tExamples:\n\t\t\t| value   | buttonType |\n\t\t\t| <null>  | primary    |\n\t\t\t| default | default    |\n\t\t\t| primary | primary    |\n\t\t\t| success | success    |\n\t\t\t| neutral | neutral    |\n\t\t\t| warning | warning    |\n\t\t\t| danger  | danger     |";
+const scenario$D = "@author:noah\n@owner:noah\n\nFeature: Link Button\n\n\t@ui\n\tScenario: Links can be opened in the same tab\n\t\tWhen a user clicks the button\n\t\tThen a link opens in the same tab\n\t\tAnd if the component is in an iFrame then the link is opened in the parent window not the iFrame\n\n\t@ui\n\tScenario: Links can be opened in a new tab\n\t\tWhen a user clicks the button\n\t\tThen a link opens in a new tab\n\t\tAnd if the component is in an iFrame then the link is still opened in a new tab\n\n\n\t@ui\n\tScenario: Props control the link and button text\n\t\tGiven the \"link\" prop is set to \"https://www.example.com\"\n\t\tAnd the \"buttonText\" prop is set to \"Click me!\"\n\t\tThen a button is shown with the text \"Click me!\"\n\t\tAnd when clicked the button opens https://www.example.com\n\n\t@ui\n\tScenario Outline: The button type can be set\n\t\tGiven the button type is set to <value>\n\t\tThen a <buttonType> is shown\n\t\tExamples:\n\t\t\t| value   | buttonType |\n\t\t\t| <null>  | primary    |\n\t\t\t| default | default    |\n\t\t\t| primary | primary    |\n\t\t\t| success | success    |\n\t\t\t| neutral | neutral    |\n\t\t\t| warning | warning    |\n\t\t\t| danger  | danger     |";
 
 const LinkButton_stories = {
   title: "Components/Link Button",
   parameters: {
-    scenario: scenario$C,
+    scenario: scenario$D,
   },
 };
-const defaultProps$g = {
+const defaultProps$h = {
   link: "https://example.com",
   openInNewTab: false,
   buttonText: "Button Text",
 };
-const Default$g = () => {
-  return h("sqm-link-button", Object.assign({}, defaultProps$g));
+const Default$i = () => {
+  return h("sqm-link-button", Object.assign({}, defaultProps$h));
 };
 const OpenInNewTab = () => {
-  return (h("sqm-link-button", Object.assign({}, { ...defaultProps$g, openInNewTab: true })));
+  return (h("sqm-link-button", Object.assign({}, { ...defaultProps$h, openInNewTab: true })));
 };
 
 const LinkButton = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': LinkButton_stories,
-  Default: Default$g,
+  Default: Default$i,
   OpenInNewTab: OpenInNewTab
 });
 
@@ -14077,7 +14216,7 @@ const CloseButton_stories = {
   // scenario,
   },
 };
-const defaultProps$h = {};
+const defaultProps$i = {};
 const containerStyles = {
   position: "relative",
   width: "500px",
@@ -14085,22 +14224,22 @@ const containerStyles = {
   border: "1px solid black",
   padding: "25px",
 };
-const Default$h = () => {
-  return h(CloseButtonView, Object.assign({}, defaultProps$h));
+const Default$j = () => {
+  return h(CloseButtonView, Object.assign({}, defaultProps$i));
 };
 const InAContainer = () => {
   return (h("div", { style: containerStyles },
-    h(CloseButtonView, Object.assign({}, defaultProps$h))));
+    h(CloseButtonView, Object.assign({}, defaultProps$i))));
 };
 const CustomColor$1 = () => {
   return (h("div", { style: containerStyles },
-    h(CloseButtonView, Object.assign({}, { ...defaultProps$h, color: "blue" }))));
+    h(CloseButtonView, Object.assign({}, { ...defaultProps$i, color: "blue" }))));
 };
 
 const CloseButton = /*#__PURE__*/Object.freeze({
   __proto__: null,
   'default': CloseButton_stories,
-  Default: Default$h,
+  Default: Default$j,
   InAContainer: InAContainer,
   CustomColor: CustomColor$1
 });
@@ -14290,17 +14429,17 @@ const RadioCardView = ({ title, icon, description, selected, }) => {
 const RadioCard_stories = {
   title: "Components/Radio Card",
 };
-const defaultProps$i = {
+const defaultProps$j = {
   selected: false,
   title: "Card Title",
   description: "Description text goes here",
   icon: "apple",
 };
 const DefaultView$1 = () => {
-  return h(RadioCardView, Object.assign({}, defaultProps$i));
+  return h(RadioCardView, Object.assign({}, defaultProps$j));
 };
 const Selected = () => {
-  return h(RadioCardView, Object.assign({}, defaultProps$i, { selected: true }));
+  return h(RadioCardView, Object.assign({}, defaultProps$j, { selected: true }));
 };
 
 const RadioCard = /*#__PURE__*/Object.freeze({
@@ -14313,13 +14452,13 @@ const RadioCard = /*#__PURE__*/Object.freeze({
 const ProgressBar_stories = {
   title: "Components/Progress Bar",
 };
-const defaultProps$j = {
+const defaultProps$k = {
   progress: 2,
   goal: 4,
   steps: true,
 };
 const TaxAndPayoutsProgressBar = () => {
-  return h(ProgressBar$2, Object.assign({}, defaultProps$j, { stageCount: 4, currentStage: 2 }));
+  return h(ProgressBar$2, Object.assign({}, defaultProps$k, { stageCount: 4, currentStage: 2 }));
 };
 
 const ProgressBar$1 = /*#__PURE__*/Object.freeze({
@@ -14391,7 +14530,6 @@ const BankingForm_stories = {
 };
 const bankingFormProps = {
   states: {
-    showVerification: false,
     hideSteps: false,
     disabled: false,
     loading: false,
@@ -14408,7 +14546,6 @@ const bankingFormProps = {
     loadingError: false,
   },
   callbacks: {
-    onVerification: () => { },
     onSubmit: async () => console.log("Submit"),
     setPaymentMethodChecked: () => { },
     setPaymentScheduleChecked: () => { },
@@ -14991,152 +15128,6 @@ const UseInvoiceTableCells = /*#__PURE__*/Object.freeze({
   InvoiceTableDemoHook: InvoiceTableDemoHook
 });
 
-const WidgetEmailVerification_stories = {
-  title: "Components/Widget Email Verification",
-};
-const defaultProps$k = {
-  email: "",
-  error: false,
-  loading: false,
-  initialLoading: false,
-  sendCodeError: false,
-};
-const Default$i = () => (h("sqm-email-verification", { demoData: {} }));
-const EmailIsPrefilled = () => (h("sqm-email-verification", { demoData: {
-    states: {
-      ...defaultProps$k,
-      email: "test@example.com",
-    },
-  } }));
-const Loading$7 = () => (h("sqm-email-verification", { demoData: {
-    states: {
-      ...defaultProps$k,
-      initialLoading: true,
-    },
-  } }));
-const SaveLoading = () => (h("sqm-email-verification", { demoData: {
-    states: {
-      ...defaultProps$k,
-      loading: true,
-    },
-  } }));
-const InvalidEmail = () => (h("sqm-email-verification", { demoData: {
-    states: {
-      ...defaultProps$k,
-      error: true,
-    },
-  } }));
-const SendCodeError = () => (h("sqm-email-verification", { demoData: {
-    states: {
-      ...defaultProps$k,
-      sendCodeError: true,
-    },
-  } }));
-
-const WidgetEmailVerification = /*#__PURE__*/Object.freeze({
-  __proto__: null,
-  'default': WidgetEmailVerification_stories,
-  Default: Default$i,
-  EmailIsPrefilled: EmailIsPrefilled,
-  Loading: Loading$7,
-  SaveLoading: SaveLoading,
-  InvalidEmail: InvalidEmail,
-  SendCodeError: SendCodeError
-});
-
-const WidgetCodeVerification_stories = {
-  title: "Components/Widget Code Verification",
-};
-const defaultProps$l = {
-  initialiseLoading: false,
-  email: "testemail@example.com",
-  loading: false,
-  verifyFailed: false,
-  emailResent: false,
-};
-const Default$j = () => (h("sqm-code-verification", { demoData: { states: defaultProps$l } }));
-const InitialLoading = () => (h("sqm-code-verification", { demoData: {
-    states: {
-      ...defaultProps$l,
-      initialiseLoading: true,
-    },
-  } }));
-const Loading$8 = () => (h("sqm-code-verification", { demoData: {
-    states: {
-      ...defaultProps$l,
-      loading: true,
-    },
-  } }));
-const CodeResent = () => (h("sqm-code-verification", { demoData: {
-    states: {
-      ...defaultProps$l,
-      emailResent: true,
-    },
-  } }));
-const VerificationFailed = () => (h("sqm-code-verification", { demoData: {
-    states: {
-      ...defaultProps$l,
-      verifyFailed: true,
-    },
-  } }));
-
-const WidgetCodeVerification = /*#__PURE__*/Object.freeze({
-  __proto__: null,
-  'default': WidgetCodeVerification_stories,
-  Default: Default$j,
-  InitialLoading: InitialLoading,
-  Loading: Loading$8,
-  CodeResent: CodeResent,
-  VerificationFailed: VerificationFailed
-});
-
-const PayoutButtonScroll_stories = {
-  title: "Components/Payout Scroll Button",
-};
-const defaultProps$m = {
-  payoutSettingsComplete: true,
-};
-const CompletedTaxForm = () => (h("sqm-payout-button-scroll", { demoData: { states: { ...defaultProps$m, payoutSettingsComplete: true } } }));
-
-const PayoutButtonScroll = /*#__PURE__*/Object.freeze({
-  __proto__: null,
-  'default': PayoutButtonScroll_stories,
-  CompletedTaxForm: CompletedTaxForm
-});
-
-const PayoutStatusAlert_stories = {
-  title: "Components/Payout Status Alert",
-};
-const defaultProps$n = {
-  error: false,
-  status: "INFORMATION_REQUIRED",
-  loading: false,
-  showVerifyIdentity: false,
-};
-const InformationRequired = () => (h("sqm-payout-status-alert", { demoData: { states: defaultProps$n } }));
-const VerifyIdentity = () => (h("sqm-payout-status-alert", { demoData: { states: { ...defaultProps$n, status: "VERIFICATION_NEEDED" } } }));
-const VerifyIdentityOpen = () => (h("sqm-payout-status-alert", { demoData: {
-    states: {
-      ...defaultProps$n,
-      status: "VERIFICATION_NEEDED",
-      showVerifyIdentity: true,
-    },
-  } }));
-const Hold = () => (h("sqm-payout-status-alert", { demoData: { states: { ...defaultProps$n, status: "HOLD" } } }));
-const Loading$9 = () => (h("sqm-payout-status-alert", { demoData: { states: { ...defaultProps$n, loading: true } } }));
-const Error$a = () => (h("sqm-payout-status-alert", { demoData: { states: { ...defaultProps$n, error: true } } }));
-
-const PayoutStatusAlert = /*#__PURE__*/Object.freeze({
-  __proto__: null,
-  'default': PayoutStatusAlert_stories,
-  InformationRequired: InformationRequired,
-  VerifyIdentity: VerifyIdentity,
-  VerifyIdentityOpen: VerifyIdentityOpen,
-  Hold: Hold,
-  Loading: Loading$9,
-  Error: Error$a
-});
-
 /**
  *
  * Themes
@@ -17827,6 +17818,7 @@ const stories = [
   ReferralIframe$1,
   NameFields$1,
   CheckboxField,
+  MarketingEmailsCheckbox,
   DropdownField,
   InputField,
   RewardExchangeList,
@@ -17860,10 +17852,7 @@ const stories = [
   TaxFormSlots,
   PayoutDetailsCard,
   BankingInfoForm,
-  WidgetEmailVerification,
-  WidgetCodeVerification,
-  PayoutButtonScroll,
-  PayoutStatusAlert,
+  NewPortalRegistrationForm,
 ];
 const StencilStorybook = class {
   constructor(hostRef) {