Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Table of Contents

Currently, white label homepage footer displays a link to "Livro de reclamações" webpage for BK-PT market.

However, the logo is not “clickable” and only the text below redirects the user.

Today, Sanity has the footer content configured in Marketing Content → Features → Feature Footer, where managers can include different rows and columns with the information they need. For BK-PT, this includes the image and link for “livro de reclamações”.

Changing all widget images with link to be clickable. The ImageWidget object in GraphQL has the fields Image, ImageDescription, Caption and attributionLink, providing all the necessary information. The attributionLink is optional, therefore, only the ones which have a registered link will be clickcable. The code will be hidden behind a feature toggle untill properly tested.

After the change is implemented and the feature toggle is activated, PT market can update sanity “Livro de Reclamações“ image with the appropriate link (and remove the extra text link that exists today, if desired) to solve the issue.

Pros:

Cons:

  • If a bussiness case where an Footer Image Widget has to have a link but cannot be clickable exists, this solution won’t work.

Create a new Option object for ImageLinks or add a new field to imageWidget. The first requires adding a new case in the footer column switch, and implementing a new component for images with link. The second is very similar to Option 1, except that the condition for the link would be the new field instead of attributionLink. Both cases will require changes in the sanity schema, that in turn, might impact any automatic synchronization between sanity and other systems.

Pros:

  • Doesn’t impact the existing Footer ImageWidgets, since either a new field is added, or an entire new object is created.

Cons:

  • If the footer is automatically synchronized by other systems (eg. MDM), the synchronization process will also have to be updated (more investigation is needed).

  • Changes span more than one repository.

  • No labels