Small corrections to Beamer Website V2

[olympe-silve]

Those are the website design fix to do implement after the Mainnet Launch (or sooner if there is the capacity)

• [ ] all items in the CTA section to be smaller with narrower columns (tbd on figma)
• [ ] Bigger logos in the Hero Background
• [x] dApp > App (copy)
• [x] FAQs > FAQ (copy)
• [ ] Exporting the background hero image in 3 different sizes to optimise load times
• [ ] Use cases section : smaller copy, slightly larger spacing between columns (consistent with CTA section, tbd on Figma)

[GabrielBuragev]

Updated description as some of the corrections are already implemented and a part of the prepared mainnet bundle.

[DBecane]

The copy is, in general still too big - beyond the use case section IMO. I'm sure there are best practices in terms of website font sizes we can refer to.

[andfletcher]

@olympe-silve, in the issue description, you write "bigger" and three different sizes. Is there a more precise size we can put into the issue, or do we not know the exact size(s) we need?

Also, e.g., how is the process to get clarification on the sices for the items in the CTA section? Will you provide the size and write it down here, or how does e.g., Gabriel know what to do / what size it will be?

[olympe-silve]

@olympe-silve, in the issue description, you write "bigger" and three different sizes. Is there a more precise size we can put into the issue, or do we not know the exact size(s) we need?

Also, e.g., how is the process to get clarification on the sices for the items in the CTA section? Will you provide the size and write it down here, or how does e.g., Gabriel know what to do / what size it will be?

For the bigger logos, it's a matter of visibility and preference from Dina's perspective. In my head I estimate this to be twice as big as they are currently, and we will see right away if that's too present in comparison with the rest of the content, or not enough, as I check with Dina in real time for those sorts of things.

For your second question, Gabriel works using the Figma file, which I will reshape using the new responsive tools on figma (which makes the design relative to other elements,not dimension based). This hopefully should fix the scaling and proportion issues that have been persisting. I don't write technical specs here on github as I only provide guidelines on how to implement a visual via Figma, as the CTA are affected by responsivity.