vtex-apps / store-footer Goto Github PK

Footer menu headers are in the same format as sub menu items, so we can make header menu item's text bold and capitalized.

Expected Behavior

Headers in footer menu should be bold and capitalized

Current Behavior

headers in footer menu is same look and feel as sub menu items

Possible Solution

Add new configurable parameter to make text bold and capitalized

Expected Behavior

An Extension Point to be able to set third party dynamic scripts like E-bit, Trustvox, protected sites...

Current Behavior

We do not have access to any extension point that allow us to add third party scripts in our stores

Context

We need to set the E-bit seal for our clients. If the scripts could be added to the stores, that would solve upcoming problems.

Expected Behavior

Nowadays Footer render Badges as images only, we suggest to wrap image tag inside Link tag from render, being available a prop for setting up logo url redirect.

Current Behavior

The current behavior do not allow us to set a url redirect to our agency website.

Context

As Agencies that implements Vtex e-commerces at least we want to be able to provide a redirect url to our website in our logo on stores footer.

When using storeInformations prop, filing information in doesn't have any visible results in the store.

{
  "footer": {
    "props": {
      "storeInformations": [
        "Store.",
        "All Rights Reserved."
      ]
    }
    "blocks": [
      
    ]
  }

Expected Behavior

I'd expect the strings in storeInformations to appear in the footer.

Is it possible for the link to have an option if it will be opened in the same browser tab or in a new tab?

We create other footer project and extend from your footer for can add in the store. but you're added one schema by default in the footer component. we need remove this schema. how ?

Expected Behavior

Be able to display most used payment methods that the store gateway accepts

Current Behavior

Nowadays the only methods that we have is MasterCard, Visa and DinersClub though there's a lot of any others that is mostly used that we don't have.

Context

We need to display the following payment methods:

• American Express
• Elo
• PayPal
• Boleto
• Hipercard

Expected Behavior

A structure that allow us to have more control over the ordering and disposal of the elements in Footer.

Current Behavior

The current structure of footer do not allows us to reordering the elements including Payment Methods based on the first container row of items.

Possible Solution

Analyze the possibility of restructure the Footer to achieve a better precision and control over elements, like ordering and disposal of then, both by props or css.

Context

Nowadays the Footer render Payment Methods as a single container, not being able to reordering it according to other elements like Social Networks and footer links. We need to achieve this level of customization, to display Payment Methods before Social Network or even a more complex and different disposal of items.

Error resolving block "footer":
Unable to find an extension point declared for block 'sandbox#testing' on block 'footer'. Check 'allowed' blocks on interface '[email protected]:footer'.

I need to use the sandbox component to insert scripts from trusted company and other kind of stamps.

Today, in the footer, we have 4 links to social networks: facebook, twitter, youtube, instagram and pinterest.

It will be very useful to have 2 more options: Blog and Custom.