First iteration on TS migration.

Description

Core files has been migrated.

Some extra things:

• Package scripts were refactored a bit. The prebuild script processes has been moved into onPreBootstrap hook in gatsby-node.
• Migrated data/translations.json into data/languages.ts.
• Removed unused LegacyPageHome.js page.
• Decoupled a but the logic that lives inside the translations.ts file. I moved them into the languages.ts.

More reference: https://www.gatsbyjs.com/docs/how-to/custom-configuration/typescript/#migrating-to-typescript

TODO

• migrate and see how to test the docsearchConfigScript.js file
• fix GC build issue

First iteration on TS migration.

Description

Core files has been migrated.

Some extra things:

• Package scripts were refactored a bit. The prebuild script processes has been moved into onPreBootstrap hook in gatsby-node.
• Migrated data/translations.json into data/languages.ts.
• Removed unused LegacyPageHome.js page.
• Decoupled a but the logic that lives inside the translations.ts file. I moved them into the languages.ts.

More reference: https://www.gatsbyjs.com/docs/how-to/custom-configuration/typescript/#migrating-to-typescript

TODO

• migrate and see how to test the docsearchConfigScript.js file
• fix GC build issue

:zap: Changes

• Add ETH SD to list of meetups (#6378) @chadlohrli
• Staking translation refactor (#6264) @wackerow
• Bounty copy clarifier (#6377) @wackerow
• fix: remove /*/grants/ redirect to avoid loop (#6371) @nhsz
• Fix ButtonLink arrow logic (#6273) @corwintines
• Close Academic Grants round (#6353) @nhsz
• Typo correction (#6364) @SuperDelphi
• Feedback widget [Fixes #6252] (#6293) @wackerow
• Fix RTL styling on codeblocks (#6203) @minimalsm
• Update proof of stake section (wiki migration) (#6157) @jmcook1186

:globe_with_meridians: Translations

• Typo correction (#6361) @moretimeL

:house: Internal

• Avoid loading matomo in preview deploys (#6366) @pettinarip

:unicorn: Contributors

Thank you @SuperDelphi, @chadlohrli, @corwintines, @jmcook1186, @minimalsm, @moretimeL, @nhsz, @pettinarip, @samajammin and @wackerow for the contributions! :trophy:

Description

Adjusts copy on bug bounty page to clarify the list of EL vs CL clients, as Nimbus also has EL infrastructure that is not currently in scope for rewards.

Description

Refactors recent staking changes to support intl translations.

https://www.notion.so/efdn/Set-up-translation-support-for-staking-pages-a306b5d4348f41ea872d6f0833f4075f

Description

Refactors recent staking changes to support intl translations.

https://www.notion.so/efdn/Set-up-translation-support-for-staking-pages-a306b5d4348f41ea872d6f0833f4075f

This PR fixes the redirect loop from /en/community/grants/

Problem

After the collapse of UST, the general sentiment I'm seeing in the wild is that algorithmic stablecoins are fundamentally flawed from a design perspective (E.g.: 1, 2, 3). This issue aims to open up the discussion publicly about whether ethereum.org should list algorithmic stablecoins on our stablecoins page or not.

Currently, we list the top eight stablecoins based on market capitalisation. In the top eight, there are presently two algorithmic stablecoins being listed (Magic Internet Money and Frax).

Potential options

I see a few paths forward, but we're entirely open to all suggestions on this.

Note: see reference images below for what the 'stablecoins list' and 'types of stablecoins' section describe.

1. Do nothing.
2. Remove algorithmic stablecoins from the 'stablecoins list' (AND remove the explanation from 'types of stablecoins'.)
3. Remove algorithmic stablecoins from the 'stablecoins list' (but keep the explanation of 'types of stablecoins'.)
4. Keep algorithmic stablecoins in the 'stablecoins list' but add a disclaimer to 'types of stablecoins' explaining that algorithmic stablecoins are experimental and not well battle-tested.

Reference images