Feat(brand): add brand resource (#3147)Co-authored-by: Shanmughapriyan S <priyanshan03@gmail.com> Co-authored-by: Claudio Wunder <cwunder@gnome.org>#3147
Feat(brand): add brand resource (#3147)Co-authored-by: Shanmughapriyan S <priyanshan03@gmail.com> Co-authored-by: Claudio Wunder <cwunder@gnome.org>#3147ovflowd merged 19 commits intonodejs:mainfrom AugustinMauroy:ressources
Conversation
|
CC @nodejs/nodejs-dev |
|
Oh boii, this is a big one 👀 going to review once I get a few minutes. |
|
Please find a preview at: https://staging.nodejs.dev/3147/ |
This is normal; it's just because it doesn't add the staging prefixes on the link. Don't worry about that. |
Codecov ReportPatch coverage has no change and project coverage change:
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. |
|
I still haven't had time to review this @shanpriyan would you mind giving an 👁️ here? |
Sure, will look into it. |
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. |
|
I will test this PR locally once I get time |
view that all the contents to change. It is not added. I will make a pr that will be reviewed by the French team. |
Full colors can be kept to have a summary but the others are not necessary. |
There was a problem hiding this comment.
- Missing icon

- 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?
- Change
Nodejs-->Node.jsin all occurrences in this PR - Unable to find the difference between these two logos


Also I think the hover state shouldn't appear for logos.
Ref: https://nodejs.dev/en/about/resources/#logo-downloads - Do we need a
without background logothat changes according to the theme? - Can we align this in a single row 🤔 ? WDYT

this too

I took this choice because we say what it is and then we show it. |
Yes, but writing html or a react component. What do you think about doing component react? |
Hmm. IMO the existing one is better. I wonder what others might think about this approach 🤔 cc: @ovflowd |
I think we don't need a react component here |
|
@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 👀 |
|
Please find a preview at: https://staging.nodejs.dev/3147/ |
ovflowd
left a comment
There was a problem hiding this comment.
I believe this should be inside a HTML table.
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:
- The name of the asset and the link to it
- Preview of the asset
All asset previews should have a fixed with so that bigger images do not "break the page"
|
You mean an html table like this :
|
|
Yes! Something like that! I apologise for the late reply 😅 |
|
@AugustinMauroy can you update this PR please? |
What is it about? |
|
I'm waiting for you to finish updating this PR with the table I asked for. |
It's done |
|
Please find a preview at: https://staging.nodejs.dev/3147/ |
ovflowd
left a comment
There was a problem hiding this comment.
Good! Let's get this merged 🎉 ![]()






Description
The idea is that the brand/resource fit with the new design.
Adding brand resources.
Related Issues
No related Issues
Check List
npm run lint:js -- --fixand/ornpm run lint:md -- --fixfor my JavaScript and/or Markdown changes.npm run testto check if all tests are passing, and/ornpm run test -- -uto update snapshots if I created and/or updated React Components.npm run buildwork fine.