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

Migrate new go-ethereum website built with Next.js #26374

Merged
merged 547 commits into from
Dec 20, 2022

Conversation

wackerow
Copy link
Member

Target branch: website

Description

The go-ethereum website front end has been getting a revamp and is ready for launch! 🎉

See Epic Tracker: ethereum/geth-website#1

This PR is a migration of the codebase at ethereum/geth-website master branch, which has been acting as the dev repo while establishing an initial release of the new site. Similar to the current gh-pages branch of this repo, a dedicated website branch has been created to act as the home for the go-ethereum website front end codebase.

This site is a React site built using Next.js, written in TypeScript, using Chakra-UI for design components, and Algolia for search functionality. The site intends to reach parity with the existing site while implementing several near features and enhancements, including but not limited to:

  • Significantly improving loading time of downloads page
  • Redesigned documentation
  • Dark mode
  • Search functionality indexed by Algolia

image

cc: @fjl @jmcook1186

wackerow and others added 30 commits November 28, 2022 11:08
% not supported for letterSpacing, 'auto' not supported for lineHeight
using DocSearch component via @docsearch/react library
* chore: update textStyles

* markdown text color styles

Co-authored-by: Corwin Smith <[email protected]>
* chore: update constants

* feat: add releases data utils

* chore: add fast-xml-parser

* chore: update types

* feat: fetch & parse all releases data

* chore: update utils

* wip: use real data on DataTable

* chore: update yarn.lock

* fix: getReleaseCommitHash

* feat: filter data per downloads tab

* chore: update DownloadsTable

* chore: update DownloadsTable Props

* fix: getReleaseArch.ts

* feat: add fetchXMLData util

* feat: add fetchLatestReleaseCommit util

* feat: add getSortedReleases util

* chore: comment wip primary release feature

* fix: fetchXMLData

* chore: add netlify.toml

* fix: total number of releases count

* fix: center showing latest releases text and use smaller font

* chore: prettier

* chore: update textStyles

* fix: merge conflicts
…age (#64)

* chore: update SpecificVersionsSection component layout to match homepage

* chore: remove non-required repeat function
Co-authored-by: Paul Wackerow <[email protected]>
@gitguardian
Copy link

gitguardian bot commented Dec 20, 2022

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
5133149 Generic High Entropy Secret 5646bc1 src/components/UI/Search.tsx View secret
5133149 Generic High Entropy Secret 7913090 src/components/UI/Search.tsx View secret
5133149 Generic High Entropy Secret 7913090 src/components/UI/Search.tsx View secret
5133149 Generic High Entropy Secret 5646bc1 src/components/UI/Search.tsx View secret
5133149 Generic High Entropy Secret 7913090 src/components/UI/Search.tsx View secret
5133149 Generic High Entropy Secret 7913090 src/components/UI/Search.tsx View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

If this detection is a false positive, please contact Oleh Vasylenko (@Aldekein) to fix it in the GitGuardian dashboard.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@wackerow
Copy link
Member Author

wackerow commented Dec 20, 2022

image

Note the security alert related to API keys is a false positive, as the keys used in these commits were publicly available keys provided by Algolia for testing

Copy link
Member

@MariusVanDerWijden MariusVanDerWijden left a comment

Choose a reason for hiding this comment

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

sgtm

@holiman
Copy link
Contributor

holiman commented Dec 20, 2022

If this detection is a false positive, please contact Oleh Vasylenko (@Aldekein) to fix it in the GitGuardian dashboard.

Ping @Aldekein

@Aldekein
Copy link
Member

It's very weird. I marked this finding as Ignored and can confirm it in GitGuardian dashboard, but for some reason it still blocks the Github checks 🤯 I emailed GitGuardian support. PR is safe to be merged.

@Aldekein Aldekein self-requested a review December 20, 2022 15:59
@MariusVanDerWijden MariusVanDerWijden merged this pull request into ethereum:website Dec 20, 2022
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.