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

fix: de-emphasize copy to clipboard button #6246

Merged
merged 3 commits into from
Jan 20, 2024
Merged

Conversation

bmuenzenmeyer
Copy link
Collaborator

@bmuenzenmeyer bmuenzenmeyer commented Jan 14, 2024

Description

De-emphasizes the copy to clipboard button. also removed the homepage customization. yes, this is a deviation of the figma- but now met with real content, especially repeated examples are distracting. this is a tertiary act for the site, it should not have primary/action color

Validation

same homepage

image

less busy examples within content

Old New
image image

Related Issues

closes #6244

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npx turbo lint to ensure the code follows the style guide. And run npx turbo lint:fix to fix the style errors if necessary.
  • I have run npx turbo format to ensure the code follows the style guide.
  • I have run npx turbo test to check if all tests are passing.
  • I've covered new added functionality with unit tests if necessary.

@bmuenzenmeyer bmuenzenmeyer requested a review from a team as a code owner January 14, 2024 21:12
Copy link

vercel bot commented Jan 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 20, 2024 2:55am

Copy link
Contributor

github-actions bot commented Jan 14, 2024

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 100 🟢 100 🟢 92 🟢 92 🔗
/en/about 🟢 100 🟢 97 🟢 92 🟢 92 🔗
/en/about/previous-releases 🟢 98 🟢 96 🟢 92 🟢 92 🔗
/en/download 🟢 100 🟢 97 🟢 92 🟢 92 🔗
/en/blog 🟢 100 🟢 97 🟢 92 🟢 92 🔗

Copy link
Contributor

github-actions bot commented Jan 14, 2024

Unit Test Coverage Report

Lines Statements Branches Functions
Coverage: 91%
86.84% (396/456) 77.33% (116/150) 78.65% (70/89)

Unit Test Report

Tests Skipped Failures Errors Time
72 0 💤 0 ❌ 0 🔥 4.566s ⏱️

@ovflowd
Copy link
Member

ovflowd commented Jan 14, 2024

@bmuenzenmeyer does it make sense to keep the green colour on light theme? Like keeping the gray on dark theme and green on light theme? I have the feeling that within the light theme the gray button is more emphasized than the green one.

@bmuenzenmeyer
Copy link
Collaborator Author

I thought about that but the codebox is always dark, so this still seems appropriate to me.

Open to more thoughts, or iterating on this for a bit.

Copy link
Member

@AugustinMauroy AugustinMauroy left a comment

Choose a reason for hiding this comment

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

LGTM

I think that on en/learn/getting-started/introduction-to-nodejs the code snippet that displays functions should be inline code.

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.

LGTM!

Copy link
Collaborator Author

@bmuenzenmeyer bmuenzenmeyer left a comment

Choose a reason for hiding this comment

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

added a neutral button kind - alphabetically first across all diffs

components/Common/CodeBox/index.module.css Show resolved Hide resolved
@bmuenzenmeyer bmuenzenmeyer added this pull request to the merge queue Jan 17, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 17, 2024
@bmuenzenmeyer bmuenzenmeyer added this pull request to the merge queue Jan 17, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 17, 2024
@ovflowd
Copy link
Member

ovflowd commented Jan 17, 2024

@bmuenzenmeyer apparently the merge queue is failing. You might want to check why 👀

@ovflowd

This comment was marked as resolved.

@bmuenzenmeyer

This comment was marked as outdated.

@bmuenzenmeyer
Copy link
Collaborator Author

@ovflowd this lint error above is directly conflicting with 31a50a6 - as if we have dueling format output

image

i re-generated my dependencies atop the lockfile - can you confirm you are using the latest too?

@ovflowd
Copy link
Member

ovflowd commented Jan 18, 2024

I mean yea, we updated the tailwind prettier plugin, so main branch has new rules 👀

@bmuenzenmeyer bmuenzenmeyer force-pushed the 6244-copy-to-clipboard branch from cd866c2 to 1830871 Compare January 20, 2024 02:53
@bmuenzenmeyer bmuenzenmeyer added the github_actions:pull-request Trigger Pull Request Checks label Jan 20, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jan 20, 2024
@bmuenzenmeyer bmuenzenmeyer added this pull request to the merge queue Jan 20, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 20, 2024
@bmuenzenmeyer
Copy link
Collaborator Author

cursed pr

@bmuenzenmeyer bmuenzenmeyer added this pull request to the merge queue Jan 20, 2024
Merged via the queue into main with commit 21ee6cf Jan 20, 2024
16 checks passed
@bmuenzenmeyer bmuenzenmeyer deleted the 6244-copy-to-clipboard branch January 20, 2024 03:07
@canerakdas canerakdas mentioned this pull request Jan 22, 2024
4 tasks
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.

Copy to Clipboard button is too prominent
6 participants