Skip to content

Feat/landing#1018

Merged
vidvidvid merged 60 commits intodevelopfrom
feat/landing
Jan 15, 2022
Merged

Feat/landing#1018
vidvidvid merged 60 commits intodevelopfrom
feat/landing

Conversation

@tommymaher15
Copy link
Contributor

Overview

What features/fixes does this PR include?

Added each component as per the mockup for the initial design.

Mockups are only for Desktop that I could see so not responsive yet but a starting point.

Will be tidying up and making things cleaner now that things are finished.

Please provide the GitHub issue number

Closes #

Follow up Improvement Ideas

  • please list any improvement/ideas

Implementation

Describe technical (nontrivial / non-obvious) parts of your code

Side effects

Assets

[Include screenshots/videos if it makes reviewing easier.]

@vercel
Copy link

vercel bot commented Jan 5, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/metafam/the-game/8vxtf99WvuNUV8dXRgAqkrTHeBZQ
✅ Preview: https://the-game-git-feat-landing-metafam.vercel.app

@vidvidvid
Copy link
Collaborator

Thanks. The build is failing on this latest update for some reason.

same thing happened here: #1014 and i retriggered the deploy which was then successful. idk what's the deal with vercel, but this is getting pretty annoying :'D

@Gnomeski
Copy link

Gnomeski commented Jan 14, 2022

"For those who want to: Help finding tools, frameworks & funds accessible. Help getting value-aligned contributors & adopters. Become a part of the "new world" puzzle."

Is this meant to be those who want (no 'to' here?) - help finding tools, frameworks and accessible funds (reverse words). Also it can just be "become part of" no need for the a.

flexDirection="column"
justifyContent="center"
maxWidth="100%"
pl={{ base: '0', md: '137px' }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there's still places where px is used, which can be replaced with rem equivalents, like this one.

bgClip="text"
maxWidth="75rem"
display="inline"
pb="35px"
Copy link
Member

@dan13ram dan13ram Jan 15, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here too, and also paddings in the Text components inside this Box

color="white"
maxWidth="75rem"
>
<Text pt="130px" pb="35px" textAlign="center">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here also padding

>
<Box
fontSize={{ base: '1.5rem', md: '3rem' }}
lineHeight={{ base: '2.25rem', md: '4rem' }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

paddings and maxWidth here

Copy link
Member

@dan13ram dan13ram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly looks good. We can merge now but we should work on moving these px measurements to rem equivalents so that everything remains responsive :)

display="flex"
alignItems="center"
flexDirection="column"
pl="76px"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on this page there are many paddings, widths, and particularly fontSize is in pxs. We want to replace them with rem equivalents and the fontSize to sm, md, lg or xl as necessary

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect I've fixed all of these to rem. Apologies I missed out on those others.

@peth-yursick
Copy link
Member

I am a tiiiny bit cringed out by the "Join NAO" in the very beginning to be totally honest.
I get a sense of dissonance between this "lolcats"-type of writing in the beginning and the rest of the text and aesthetic which seem to be quite serious afterwards.
This might be an aesthetic choice but I think it may probably drive other people off too, especially if we now want to appeal to more academically inclined audiences such as Game B folks.

This kind of "we're doing serious things but we also joke" vibe has kind of been the brand voice since the first articles. Personally, I find things more believable with this "we don't take ourselves too seriously" vibe vs. being super serious, especially if talking about something utopian.
To me, making it serious is what makes it cringe..

In this case, the right way to go may simply be to remove the "join nao". Its kind of a standard practice to have the call to action right away but in our case I think it might be better to force everyone to actually read the page before trying to join 🤷‍♂️

But this may be just me & it really is time to solidify brand voice..
Thank you for the feedback 🙏

vidvidvid added a commit that referenced this pull request Jan 16, 2022
@vidvidvid vidvidvid mentioned this pull request Jan 16, 2022
vidvidvid added a commit that referenced this pull request Jan 16, 2022
tenfinney pushed a commit that referenced this pull request Mar 1, 2022
* Create landing.tsx

testing

* feat:Intro section (initial)

* feat:Intro section (cleanup)

* feat:Intro section (initial)

* Landing: Added second section and necessary assets

* Landing: Added second section and necessary assets

* Landing: cleanup intro

* Landing: Build section done

* Landing: added revolution section. Apologies on naming 🚀

* Big commit: added multiple sections & some minor fixes

* small ui fixed

* Final push on last components next commit

* ui fix

* large commit: added most final sections, one more to go

* added all sections as per mockup.Up next: refactoring and cleanup

* testing

* Create landing.tsx

testing

* feat:Intro section (initial)

* feat:Intro section (cleanup)

* feat:Intro section (initial)

* Landing: Added second section and necessary assets

* Landing: Added second section and necessary assets

* Landing: cleanup intro

* Landing: Build section done

* Landing: added revolution section. Apologies on naming 🚀

* Big commit: added multiple sections & some minor fixes

* small ui fixed

* Final push on last components next commit

* ui fix

* large commit: added most final sections, one more to go

* added all sections as per mockup.Up next: refactoring and cleanup

* testing

* cleanup file structure

* feat: landing ( Improved file structure for landing page and tidied improrts

* fixed imports: importing from design system instead from chakra

* fixed ordered list

* cleanup

* fixed ordered list

* Update packages/web/pages/landing.tsx

Co-authored-by: vidvidvid <35112939+vidvidvid@users.noreply.github.com>

* prettier and cleanup folders

* testing type declaration

* big commit: fixed missing type errors and linting errors

* removed px values + rem (used colors as per design system )

* updated node modules

* updated imports

* mobile work: WIP

* more mobile work

* responsiveness changes for last components

* fix

* Trigger Build

* updated intro to fix overlap

* fixed height on sections to full height

* quickfix

* Trigger Build

* content change

* content changes

* fixed exports on components and imports as per linting guidelines )

* fixed px values to rem for responsiveness

Co-authored-by: vidvidvid <35112939+vidvidvid@users.noreply.github.com>
tenfinney pushed a commit that referenced this pull request Mar 1, 2022
alalonde pushed a commit that referenced this pull request Mar 12, 2022
* Create landing.tsx

testing

* feat:Intro section (initial)

* feat:Intro section (cleanup)

* feat:Intro section (initial)

* Landing: Added second section and necessary assets

* Landing: Added second section and necessary assets

* Landing: cleanup intro

* Landing: Build section done

* Landing: added revolution section. Apologies on naming 🚀

* Big commit: added multiple sections & some minor fixes

* small ui fixed

* Final push on last components next commit

* ui fix

* large commit: added most final sections, one more to go

* added all sections as per mockup.Up next: refactoring and cleanup

* testing

* Create landing.tsx

testing

* feat:Intro section (initial)

* feat:Intro section (cleanup)

* feat:Intro section (initial)

* Landing: Added second section and necessary assets

* Landing: Added second section and necessary assets

* Landing: cleanup intro

* Landing: Build section done

* Landing: added revolution section. Apologies on naming 🚀

* Big commit: added multiple sections & some minor fixes

* small ui fixed

* Final push on last components next commit

* ui fix

* large commit: added most final sections, one more to go

* added all sections as per mockup.Up next: refactoring and cleanup

* testing

* cleanup file structure

* feat: landing ( Improved file structure for landing page and tidied improrts

* fixed imports: importing from design system instead from chakra

* fixed ordered list

* cleanup

* fixed ordered list

* Update packages/web/pages/landing.tsx

Co-authored-by: vidvidvid <35112939+vidvidvid@users.noreply.github.com>

* prettier and cleanup folders

* testing type declaration

* big commit: fixed missing type errors and linting errors

* removed px values + rem (used colors as per design system )

* updated node modules

* updated imports

* mobile work: WIP

* more mobile work

* responsiveness changes for last components

* fix

* Trigger Build

* updated intro to fix overlap

* fixed height on sections to full height

* quickfix

* Trigger Build

* content change

* content changes

* fixed exports on components and imports as per linting guidelines )

* fixed px values to rem for responsiveness

Co-authored-by: vidvidvid <35112939+vidvidvid@users.noreply.github.com>
alalonde pushed a commit that referenced this pull request Mar 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.