witnet / website Goto Github PK

Prepare a mockup of the new design of the website with the outputs collected from prior discussion.

The goal of this task is to draft how the website will look like (i.e. the content layout).

Based on the outputs of #32, create the copies for each part of the content layout.

The font families currently being used are not the same than in the design. We need to pay attention to the usage of the two different fonts (Avenir Next Pro for titles and Almarai for paragraphs) and also negative letter spacing.

The select component can´t be position next to the responsive menu. It breaks when the menu modal opens.

This is to limit bots from scraping the website and joining / spamming the telegram group

@kengork is in da house!

@jrmoreau is in da house!!!

Social icons in the following order:

• Twitter
• Telegram
• Discord
• GitHub
• Medium
• Reddit

The current stylesheet could use some polishing. Namely:

• Give padding to "What Is Witnet" headers, so they look nicer when you navigate through anchors.
• Review usage of typographies.
• Improve logo — currently it doesn't match the one we are using pretty much everywhere else.

@Tommytrg is in da house!!!

To reproduce run yarn install on any m1 machine.

@mariocao commented on Mon Mar 01 2021

Website is horizontally scrollable using triple-tap or middle click gestures.

This normally happens because the size of the document or a top level element is set to 100vw instead of 100%, so even if the viewport looks right at first, elements are actually overflowing behind the scrollbar.

Update the team section:

• Add new team members
• Update open positions

Alongside "What is Witnet?" and "How to Participate"

Otherwise it's difficult to find because you have to scroll down or press "How to Participate", but someone looking for documentation may not click there.

This is a checklist of known issues / needed or wished improvements:

• Wrong button alignment:
  

• Wrong alignment:
  
  

• Wrong alignment
  

We should be able to replace the PNGs for SVGs once these are minified (some of them are quite complex and contain heavyweight metadata that makes them unusable on a web or mobile context because of bandwidth and rendering times)

• Mario → VP Engineering
• Jose
• James
• Tomás → Front-end Lead Developer