Problem
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.
Current Status
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”.
...
Solutions Proposed
Option 1
Changing all widget images that have a link into clickable. The ImageWidget object in graphql has the fields Image, ImageDescription, Caption and attributionLink, so it has 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:
Low effort, the required changes are minimal, and happen in a single github repository (https://github.com/rbilabs/intl-whitelabel-app )
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.
Option 2
Create a new Option object for ImageLinks, or add a new field to imageWidget. The first requires including a new case in the footer column switch, and implementing a new component for the image with link. The second is very similar to Option 1, but 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), this synchronization process will have to be updated with the new schema (more investigation is needed).
Changes span more than one repository.