Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Comments

Feat(brand): add brand resource (#3147)Co-authored-by: Shanmughapriyan S <priyanshan03@gmail.com> Co-authored-by: Claudio Wunder <cwunder@gnome.org>#3147

Merged
ovflowd merged 19 commits intonodejs:mainfrom
AugustinMauroy:ressources
Mar 20, 2023
Merged

Feat(brand): add brand resource (#3147)Co-authored-by: Shanmughapriyan S <priyanshan03@gmail.com> Co-authored-by: Claudio Wunder <cwunder@gnome.org>#3147
ovflowd merged 19 commits intonodejs:mainfrom
AugustinMauroy:ressources

Conversation

@AugustinMauroy
Copy link
Member

@AugustinMauroy AugustinMauroy commented Jan 8, 2023

Description

The idea is that the brand/resource fit with the new design.

Adding brand resources.

  • The colors
  • The font
  • The nodejs logos
  • Other asset

Related Issues

No related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
    • This is important as most of the cases your code changes might not be correctly linted
  • I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
  • I have checked that the build works locally and that npm run build work fine.
  • I've covered new added functionality with unit tests if necessary.

@AugustinMauroy
Copy link
Member Author

CC @nodejs/nodejs-dev

@AugustinMauroy AugustinMauroy added the create-preview Generate preview on staging.nodejs.dev label Jan 8, 2023
@AugustinMauroy AugustinMauroy temporarily deployed to firebase-staging January 8, 2023 16:29 — with GitHub Actions Inactive
@github-actions github-actions bot removed the create-preview Generate preview on staging.nodejs.dev label Jan 8, 2023
@ovflowd
Copy link
Member

ovflowd commented Jan 8, 2023

Oh boii, this is a big one 👀 going to review once I get a few minutes.

@github-actions
Copy link

github-actions bot commented Jan 8, 2023

Please find a preview at: https://staging.nodejs.dev/3147/

@AugustinMauroy
Copy link
Member Author

In local:

Capture d’écran 2023-01-08 à 17 40 27

In GitHub Staging:

Capture d’écran 2023-01-08 à 17 41 30

It's 404 error

Have you an idea ?

@ovflowd
Copy link
Member

ovflowd commented Jan 8, 2023

Have you an idea ?

This is normal; it's just because it doesn't add the staging prefixes on the link. Don't worry about that.

@codecov-commenter
Copy link

codecov-commenter commented Jan 8, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.47 ⚠️

Comparison is base (fd57b87) 66.02% compared to head (b7fd195) 65.55%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3147      +/-   ##
==========================================
- Coverage   66.02%   65.55%   -0.47%     
==========================================
  Files         118      145      +27     
  Lines        1351     1742     +391     
  Branches      342      407      +65     
==========================================
+ Hits          892     1142     +250     
- Misses        422      555     +133     
- Partials       37       45       +8     

see 197 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@ovflowd
Copy link
Member

ovflowd commented Jan 18, 2023

I still haven't had time to review this @shanpriyan would you mind giving an 👁️ here?

@shanpriyan
Copy link
Contributor

I still haven't had time to review this @shanpriyan would you mind giving an eye here?

Sure, will look into it.

@AugustinMauroy
Copy link
Member Author

I still haven't had time to review this shanpriyan would you mind giving an 👁️ here?

Anyway before merge this pr I wait for an opinion of one or two member of the TSC because we define anyway the logo that the world can use.

Copy link
Contributor

@shanpriyan shanpriyan left a comment

Choose a reason for hiding this comment

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

  • Remove unused .svg files in static/images/ (noticed that accent-colors.svg and full-color.svg are not being used anywhere)
  • Missing branding.fr.md file
    image

@shanpriyan
Copy link
Contributor

shanpriyan commented Jan 18, 2023

I will test this PR locally once I get time

@AugustinMauroy
Copy link
Member Author

Missing branding.fr.md file

view that all the contents to change. It is not added. I will make a pr that will be reviewed by the French team.

@AugustinMauroy
Copy link
Member Author

Remove unused .svg files in static/images/ (noticed that accent-colors.svg and full-color.svg are not being used anywhere)

Full colors can be kept to have a summary but the others are not necessary.

Copy link
Contributor

@shanpriyan shanpriyan left a comment

Choose a reason for hiding this comment

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

  1. Missing icon
    image
  2. The respective logo text should appear below the logo, also the background and border-radius seem a bit weird, Are you sure that's expected?

This PR
image

  1. Change Nodejs --> Node.js in all occurrences in this PR
  2. Unable to find the difference between these two logos
    image
    image
    Also I think the hover state shouldn't appear for logos.
    Ref: https://nodejs.dev/en/about/resources/#logo-downloads
  3. Do we need a without background logo that changes according to the theme?
  4. Can we align this in a single row 🤔 ? WDYT
    image
    this too
    image

@AugustinMauroy
Copy link
Member Author

The respective logo text should appear below the logo

I took this choice because we say what it is and then we show it.

@AugustinMauroy
Copy link
Member Author

Can we align this in a single row 🤔 ? WDYT

Yes, but writing html or a react component.

What do you think about doing component react?

@shanpriyan
Copy link
Contributor

The respective logo text should appear below the logo

I took this choice because we say what it is and then we show it.

Hmm. IMO the existing one is better.

I wonder what others might think about this approach 🤔

cc: @ovflowd

@shanpriyan
Copy link
Contributor

Can we align this in a single row 🤔 ? WDYT

Yes, but writing html or a react component.

What do you think about doing component react?

I think we don't need a react component here

@shanpriyan shanpriyan added the create-preview Generate preview on staging.nodejs.dev label Jan 21, 2023
@github-actions github-actions bot removed the create-preview Generate preview on staging.nodejs.dev label Jan 21, 2023
@ovflowd
Copy link
Member

ovflowd commented Feb 8, 2023

@AugustinMauroy could you rebase this branch so I could deploy a preview? I want to see how it looks and give my 2cents (opinion) on this PR 👀

@github-actions
Copy link

github-actions bot commented Feb 9, 2023

Please find a preview at: https://staging.nodejs.dev/3147/

Copy link
Member

@ovflowd ovflowd left a comment

Choose a reason for hiding this comment

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

image

I believe this should be inside a HTML table.

image

This is also a little bit confusing, mostly because of the sizes of the image. I also believe it should be in a table.

Pretty much you can create a HTML table that has two columns:

  1. The name of the asset and the link to it
  2. Preview of the asset

All asset previews should have a fixed with so that bigger images do not "break the page"

@AugustinMauroy
Copy link
Member Author

You mean an html table like this :

name <img 'same rise'>

@AugustinMauroy AugustinMauroy requested review from ovflowd and shanpriyan and removed request for ovflowd and shanpriyan February 15, 2023 21:01
@ovflowd
Copy link
Member

ovflowd commented Feb 27, 2023

Yes! Something like that! I apologise for the late reply 😅

@ovflowd
Copy link
Member

ovflowd commented Mar 10, 2023

@AugustinMauroy can you update this PR please?

@AugustinMauroy
Copy link
Member Author

AugustinMauroy commented Mar 10, 2023

@AugustinMauroy can you update this PR please?

What is it about?

@ovflowd
Copy link
Member

ovflowd commented Mar 15, 2023

I'm waiting for you to finish updating this PR with the table I asked for.

@AugustinMauroy
Copy link
Member Author

I'm waiting for you to finish updating this PR with the table I asked for.

It's done

@shanpriyan shanpriyan added the create-preview Generate preview on staging.nodejs.dev label Mar 15, 2023
@github-actions github-actions bot removed the create-preview Generate preview on staging.nodejs.dev label Mar 15, 2023
@github-actions
Copy link

Please find a preview at: https://staging.nodejs.dev/3147/

Copy link
Member

@ovflowd ovflowd left a comment

Choose a reason for hiding this comment

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

Good! Let's get this merged 🎉 :shipit:

@ovflowd ovflowd changed the title Feat(brand): add brand resource Feat(brand): add brand resource (#3147)Co-authored-by: Shanmughapriyan S <priyanshan03@gmail.com> Co-authored-by: Claudio Wunder <cwunder@gnome.org> Mar 20, 2023
@ovflowd ovflowd merged commit 82b7353 into nodejs:main Mar 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants