Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: new styles implemented #534

Merged
merged 39 commits into from
Mar 7, 2022
Merged

Conversation

mcturco
Copy link
Member

@mcturco mcturco commented Jan 5, 2022

Currently working on a new version of the website with the new branding applied across all elements. Styles to match new brand have been added in tailwind config. In the process of making sure all typography and colors match new brand. Some small edits to spacing are being made here as well.

Also - wanted to make it known that there are going to be little changes in several files. If it makes more sense to separate these into several PRs, let me know! Just wanted to post the progress so far.

cc: @magicmatatjahu


UPDATE:
New styles have been implemented based on the current Design System styles 🎉

Here is a screenshot preview, but you may also view the changes via the deploy preview link below:

Screen Shot 2022-02-07 at 5 36 36 PM

Some things that were edited:

  • tailwind css config file settings
  • New AsyncAPI logo added
  • New color palette
  • New font
  • Heading component (applies tailwind classes based on typeStyle prop, with ability to change the heading level)
  • Paragraph component (applies tailwind classes based on typeStyle prop)
  • TextLink component (applies tailwind classes by default for inline links)
  • The above 3 components have been applied throughout the website so that the typography remains consistent with the Design System

Do leave your feedback in this PR if you have it! 😄

Styles to match new brand have been added in tailwind config. In the process of making sure all typography and colors match new brand.
@netlify
Copy link

netlify bot commented Jan 5, 2022

✔️ Deploy Preview for asyncapi-website ready!

🔨 Explore the source changes: b3dc206

🔍 Inspect the deploy log: https://app.netlify.com/sites/asyncapi-website/deploys/6225f5c6f344b60007a77d9f

😎 Browse the preview: https://deploy-preview-534--asyncapi-website.netlify.app

Copy link
Member

@magicmatatjahu magicmatatjahu left a comment

Choose a reason for hiding this comment

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

I know that it's a draft PR but I see some problems.

I checked live preview and it's amazing 🚀 I am not sure but everything looks almost finished 😅 In the meantime, are you also working on a page for style guides (I ask because of the PR description)?

components/DemoAnimation.js Outdated Show resolved Hide resolved
components/typography/Heading.js Outdated Show resolved Hide resolved
tailwind.config.js Outdated Show resolved Hide resolved
tailwind.config.js Show resolved Hide resolved
@mcturco
Copy link
Member Author

mcturco commented Jan 7, 2022

In the meantime, are you also working on a page for style guides (I ask because of the PR description)?

@magicmatatjahu I have raised an issue for this so someone can help me set up the template. I tried doing it myself but I couldn't get it to work right. Here is the issue: #532

I think @yashsehgal is wanting to help out with it!

@magicmatatjahu
Copy link
Member

magicmatatjahu commented Jan 10, 2022

@mcturco

@magicmatatjahu I have raised an issue for this so someone can help me set up the template. I tried doing it myself but I couldn't get it to work right. Here is the issue: #532

I think @yashsehgal is wanting to help out with it!

If you need help I can show you how to setup new page on video call :) When do you have time? Of course if @yashsehgal don't have problem with second guy with help 😅

@mcturco
Copy link
Member Author

mcturco commented Jan 10, 2022

If you need help I can show you how to setup new page on video call :)

@magicmatatjahu yes! I would love that. I think @yashsehgal mentioned he was having issues with it on the issue I raised?

Perhaps you can help us both 😄

Copy link
Member

@magicmatatjahu magicmatatjahu left a comment

Choose a reason for hiding this comment

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

Three more comments :)

components/typography/Heading.js Outdated Show resolved Hide resolved
let classNames
const Tag = `${level}`;

if (typeStyle === 'heading-xl') {
Copy link
Member

Choose a reason for hiding this comment

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

Can I have question? What is a difference between heading and body? I mean e.g. heading-lg and body-lg?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure, heading is for heading type treatments and in most cases have a heavier weight and darker color than the paragraphs, which are called body to represent body copy. Here is a visual breakdown of these styles and the class names assigned to each.

WebsiteTypography

The names in the bubble are the identifiers which will be passed into typeStyle within each component and the classnames below that identifier are the tailwind classnames that are assigned to each identifier.

Copy link
Member

Choose a reason for hiding this comment

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

Ok, thanks! :) However, can we use here switch cases syntax not if else?

components/typography/Paragraph.js Outdated Show resolved Hide resolved
@mcturco mcturco marked this pull request as ready for review February 7, 2022 22:24
@mcturco
Copy link
Member Author

mcturco commented Feb 7, 2022

Hi @magicmatatjahu 👋

I think this is about ready for review. There might be some small things that I might have missed but IMO I don't think we should wait much longer to merge these changes, for things like that we can just open separate PRs.

Initially, I thought it would be a good idea to merge this PR at the same time as #539 (brand guidelines pages), but honestly after thinking about it I don't see why the making of the brand guidelines pages have to hold up the release of this PR, but wondering what others think.

cc: @fmvilas @derberg

@akshatnema
Copy link
Member

Hey @mcturco sorry for intervening in the PR 😅, as I am not much related to the PR and issue. Here are some of the changes I think you should need to consider:

  1. Hovering the links in the Footer makes the text invisible - Maybe it's because, on hover, you have provided purple color to the text and on the black background, it's not visible. Here is my preview:
    Screenshot from 2022-02-08 10-57-42

About Link got disappeared (because of color) when I put my cursor on it. The same happened with the link at the footer, specifying the trademark policies.

  1. Responsive issue in Navbar in a window size of 14 inches - If you open the dropdown menu of Community in Navbar and make your screen size of 1330px * 698px, you will see that the dropdown menu is not perfectly visible in the whole screen. You probably can assign the height in percentage or just decrease some padding/margin between the options so that it gets corrected. Here's the preview:
    Screenshot from 2022-02-08 11-01-34

@mcturco
Copy link
Member Author

mcturco commented Feb 23, 2022

@magicmatatjahu Thank you for the tips!

Check now and see if that's better 😄

Copy link
Member

@magicmatatjahu magicmatatjahu left a comment

Choose a reason for hiding this comment

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

Two comments about switch case :)

components/typography/Heading.js Outdated Show resolved Hide resolved
components/typography/Paragraph.js Outdated Show resolved Hide resolved
@magicmatatjahu
Copy link
Member

@mcturco 👌🏼 Lets see what other people will think :) Could you write about that PR on Slack as we discussed?

@akshatnema
Copy link
Member

Hey @mcturco, I saw the preview right now. Really, great work done by you in typography, styling, and design. You nailed it ✨. Overall, PR looks top-notch and fully complete. Just look like a few finishing touches are needed and then, this PR will boom the website 💥. Here are some suggestions from my side:

  • URL Text Link not visible on hover

Screenshot (25)_LI

Yep, I completely understand that you have made a default styling for all the links on the website, but I think we have to make the hover effect of this link the same as that of About, Blog, etc. in the footer.

  • A Very Fine Line Gap on top of Navbar

Screenshot 2022-02-25 150015

This error is still on the website right now as well. Looks like there is a very fine gap between the top and navbar of the website. I don't know why it is there and how to resolve it. I will just suggest, if you find this error, kindly resolve it 😄.

  • Extra indentation for title in docs

Screenshot 2022-02-25 151126

I'm not sure why you put extra spacing on the left of the title. Is it made intentionally? From my point of view, it should be left-aligned as it is right now on the website.

@mcturco
Copy link
Member Author

mcturco commented Feb 25, 2022

Hey @akshatnema, thank you so much for your kind words and your review ❤️

Yep, I completely understand that you have made a default styling for all the links on the website, but I think we have to make the hover effect of this link the same as that of About, Blog, etc. in the footer.

Good find! I have updated the code with your suggestion 😄

This error is still on the website right now as well. Looks like there is a very fine gap between the top and navbar of the website. I don't know why it is there and how to resolve it. I will just suggest, if you find this error, kindly resolve it 😄.

I don't see this on my end, even when checking in other browsers (chrome, firefox, safari). Either way, because this is a current problem on the website, we should probably raise a separate issue and debug it there.

I'm not sure why you put extra spacing on the left of the title. Is it made intentionally? From my point of view, it should be left-aligned as it is right now on the website.

Thank you for finding this bug! That definitely wasn't intentional... not sure how that happened, must have been while merging changes. Just fixed that as well!

@magicmatatjahu
Copy link
Member

Seriously, Missy needs more feedback. it's a big change and we don't want to merge with two reviews.

cc @derberg @boyney123 @fmvilas @alequetzalli

@fmvilas
Copy link
Member

fmvilas commented Feb 28, 2022

The roadmap page isn't still visible? Any idea why?

@magicmatatjahu
Copy link
Member

magicmatatjahu commented Feb 28, 2022

The roadmap page isn't still visible? Any idea why?

It is never visible because someone could make a console log of our credentials (I guess, I haven't configured repo config myself).

@fmvilas
Copy link
Member

fmvilas commented Feb 28, 2022

Oh yeah, you're right. Cool, then I'll blindly say "LGTM 👍" 😄

@boyney123
Copy link
Contributor

Scanned through the 45 files of changes, couldn't see any obvious problems, also spent time looking at the preview (which looks amazing btw), can't find any problems either... so from what I can tell it's looking good!

Copy link
Member

@magicmatatjahu magicmatatjahu left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Member

@quetzalliwrites quetzalliwrites left a comment

Choose a reason for hiding this comment

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

🚢 🚢 🚢

@mcturco
Copy link
Member Author

mcturco commented Mar 7, 2022

/rtm

@asyncapi-bot asyncapi-bot merged commit 4ee787b into asyncapi:master Mar 7, 2022
@mcturco mcturco deleted the missy-new-styles branch March 7, 2022 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

7 participants