🛠️ Potential Solutions

The solution is to add a field in sanity so that franchisse can add the texts related to the policy cover and thus communicate with the frontend on the support page.

✅ Proposed Solution

The solution involves adding a new field to the Sanity support document, allowing policy cover texts to be included. In addition, a policy cover field will be inserted on the support page, just below the form, which will display the information provided in Sanity. We will also have a temporary feature flag that will be used to validate the feature in production and that can be removed afterwards.

On the support page we will have a field where the user can read the information about the policy cover before finalizing the submission of the form.

Within the sanity support document there will be a field where the franchisee can add a document with the texts related to the policy cover.

By clicking on the policy cover document, the user will be able to change the policy cover texts to various languages that will be used for the frontend as shown in the screens above.

To implement this solution, it will be necessary to make some changes to two repositories: intl-whitelabel-cms and intl-whitelabel-app. An example of changes required for each is described below.

Intl-whitelabel-cms

fields: [
  ...,
  {
    title: 'Support Policy Cover',
    name: 'supportPolicyCover',
    type: 'array',
    of: [
      {
        title: 'Privacy Policy Disclaimers Cell',
        name: 'privacyPolicyDisclaimersCell',
        type: 'privacyPolicyDisclaimersCell',
      },
    ],
  },
  ...,
]

Intl-whitelabel-app

supportPolicyCover {
  privacyPolicyDisclaimersCells {
    disclaimerTitle
    disclaimerDescription
    disclaimerContent {
      locale: enRaw
    }
    border
    fontSize
    paddingTop
    paddingRight
    paddingBottom
    paddingLeft
    radius
  }
}

{
...
const {
    ...,
    supportPolicyCover,
  } = data?.SupportData ?? {};
  const isSupportDataLoading = featureIdsLoading || loading;
  
  ...
  
  return {
    ...,
    supportPolicyCover,
  };
};

const { supportPolicyCover } = useSupportData();
const privacyPolicyDisclaimersCells =
    supportPolicyCover?.privacyPolicyDisclaimersCells;
    
<PoliciesContainer>
      {privacyPolicyDisclaimersCells?.map(item => {
        return (
          item?.disclaimerContent?.locale && (
            <PrivacyPolicyDisclaimerBox radius={item?.radius} border={item?.border}>
              <PrivacyPolicyDisclaimer
                fontSize={item?.fontSize}
                paddingTop={item?.paddingTop}
                paddingRight={item?.paddingRight}
                paddingBottom={item?.paddingBottom}
                paddingLeft={item?.paddingLeft}
              >
                <SanityBlockRenderer content={item?.disclaimerContent?.locale} />
              </PrivacyPolicyDisclaimer>
            </PrivacyPolicyDisclaimerBox>
          )
        );
      })}
</PoliciesContainer>

Potential Challenges

N/A

💰 Cost

N/A

🎛️ Configuration

Sanity

The first step in this solution involves adding the texts in Sanity. To do this, you will need to navigate to the support document and add a new item in the “Support Policy Cover” field via the following path:

CTG Configs -> Support -> Support Data

Once the item has been created, clicking on it, it will open a modal, allowing you to include the messages that will be displayed in the “Disclaimer Content” field. In addition, all translations must be entered in the corresponding fields for each language.

Launch Darkly

The second stage is simpler and will only be carried out in the initial stages of validating the feature in production, and will be removed after this phase.

If the feature flag is still present, you will need to access the “support-policy-cover-to-contact” flag and enable it in the desired environment. Otherwise, the feature will already be working and you'll just need to add the content to Sanity.

📈 Metrics

N/A

🗓️ Delivery Plan

🧑‍🚒 QA Plan

⚠️ Call-outs

N/A