Jest Website v2

[slorber]

Summary

@SimenB I thought it was a good idea to have a PR merging the jest-website-v2 to master.

This way we can check if there are conflicts to resolve

Test plan

preview

[slorber]

Note, the current Configuration.md conflicts should be resolved after you merge #11148

[netlify]

Deploy preview for jestjs ready!

Built with commit 104fafd

https://deploy-preview-11149--jestjs.netlify.app

[ElianCordoba]

Smol detail, the nytimes logo is not very visible in dark mode, I can create an issues if you want me to

[codecov-io]

Codecov Report

Merging #11149 (104fafd) into master (b1764ef) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11149      +/-   ##
==========================================
+ Coverage   64.14%   64.15%   +0.01%     
==========================================
  Files         307      307              
  Lines       13373    13373              
  Branches     3259     3259              
==========================================
+ Hits         8578     8580       +2     
+ Misses       4089     4088       -1     
+ Partials      706      705       -1     

Impacted Files	Coverage Δ
packages/expect/src/utils.ts	96.12% <0.00%> (+1.29%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b1764ef...104fafd. Read the comment docs.

[SimenB]

seems like #11148 just made conflicts worse 😅 at least the squash merge I did. maybe just rebase this branch?

If it does not create conflicts I can probably do that before merging

[SimenB]

Smol detail, the nytimes logo is not very visible in dark mode, I can create an issues if you want me to

Could you open up a separate issue, please? 🙂 I'll be merging this later today and it would be great to not forget to fix.

EDIT: never mind: #11183

[SimenB]

let's go 👍

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.